Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/19/2021 in all areas

  1. Hello All, This will serve as a formal forum announcement that we have released the version 1.6.3 update for the Take Command! Saab 340A. All customers who have purchased the Saab 340A up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the Saab 340A from today forward, your purchased download will already be updated to version 1.6.3 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original Saab 340A download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: Pilot DH Dial (reworked the DH Dial Logic to fix decrement error) F/O DH Dial (added DH Dial logic to F/O Side) ITT Digital LED (corrected wrong Dataref assignment for Cargo and AEW ITT Digital LEDs) Cockpit Dome Light(s) (adjusted light intensity) GPWS (fixed bad Dataref handle in logic causing a crash) Gust Lock (fixed a bug in the logic for engaging gust lock with commands) CTOT (reinstated torque value calc function casing CTOT to not engage) Engine Start (rewrote the "start relay" logic incorrectly causing open and closing of the relay on motoring start) Engine Temps (tweaked the ITT values) Cargo Glass (fixed incorrect positioning) Stairs (fixed Cargo and AEW animations) Cockpit Document Holder (fixed texture reflectivity) Pending: From v1.6.0 - Sim freezes/hangs on Saab load at certain airports This bug appears to be related to airports that are at or near the Prime Meridian and possibly the equator. The map logic for converting lat/lon to x/y coordinates was getting hung in a loop due to coincident points or convergence error. This can be fixed but will take some revamping of the map coordinate logic, which is somewhat complex math and may take a little time. We are going to clean up most of the other bugs first and then get to this one. The good news is that for now the aircraft is working fine in all other areas of the world. Gust Lock (Locking flaps incorrectly - will revisit in v2.0) Reported as a bug. This is NOT a bug!... Hydraulic Pump (tested for continuous running (unable to recreate, may be related to GPWS bug) As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.
    2 points
  2. I average 40 FPS in Xplane 11. If i enable Skymaxx my frames never go past 20 FPS and get as low as 6 FPS in cloud. Not happy with the product its not usable without ruining the whole flight experiace. I run it in a RTX 2080 TI
    1 point
  3. For throttles my solution is to bind one button to remove flt idle lock and second one to put engines in reverse. Also i edited throttle curve so that my hotas throttle at 0 is ground idle. On touchdown first i push one to remove lock and then use other one to put engines in reverse. Works very well, at least for me.
    1 point
  4. I put in a ticket very late last night. Woke up hours later to find that the ticket has been created. That's FAST and to their credit. I'm not fixed yet, but I truly believe that with the number of folks who have written with a similar problem, that it will be resolved fairly quickly. Submit a ticket, describe the problem to the best of your ability so that X-Aviation can perhaps spot a trend and then patiently wait and hope for a quick fix. I found the problem involved my BN-2 Islander, my BN-2T, the TBM900 and the LES Saab 340 (maybe my favorite).
    1 point
  5. @andrey458You said you’re quite new to this, so one of the things that is often very confusing is the misleading concept of a “stall speed”. In short, there really is no such thing without a lot of other parameters also being considered. I reported the stick pusher issue after spending a good few days flight testing the Saab model, and while it does kick in too soon, it should not affect you at all when flying normally. Make sure you do not have the experimental flight model select (this makes the situation worse). It’s worth having a look at this video, you can start at about 9 minutes if you want to skip the theory and see the flight demo. It shows another aircraft, but the concept is the same for all aircraft.
    1 point
  6. Honestly? What if we're already using Windows 10 and still have the problems? I'd take a look at the forum posts here....many are already reporting problems associated with the latest update and they all seem to point to Gizmo. In the meantime, we can't fly.
    1 point
  7. I just saw this in the 1.62 update post: -Stick Pusher (premature engagement will be revisited in v2.0) So i guess this is a known issue and will not be resolved until the next major version.
    1 point
  8. The same for me. I've update to SMP 5.0 after purchase RWC (so 20$ + 20$), and it was better with SMP 4.0. When I desactive SMP 5.0 I've 50/55 FPS, and It drops to 15/20 FPS, just with broken clouds, without volumetric beta. I'm very disapointing and hope a future update will improve that.
    1 point
×
×
  • Create New...