Cameron

Use the X-Aviation contact form.

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.

Glad you're enjoying it, and nice shots!

If you are using Windows 7 (11 years old) this is the cause. You will need to upgrade to Windows 10.

It's not released. Still in development. There will be a discount offered to current DC-3 owners when it is released.

Right...that's the old version of the DC-3, NOT the one being previewed in this article.

Confirmed broken. A fix for this is in the works.

This was addressed in the release notes both in the forum and in the update e-mail.

Sorry, I missed that part. @JGregory will need to answer this one.

In the Gizmo menu on the right side of the screen, find the Saab preferences. There is a setting for tiller use there.

Captains, This will serve as a formal forum announcement that we have released the version 1.2 update for the BN-2 Islander. All customers who have purchased the BN-2 Islander 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 BN-2 Islander from today forward, your purchased download will already be updated to version 1.2 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 BN-2 Islander download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: Improvements / New Features: New exterior textures. Improved rivets and joins and dirt. Better normal maps. Updated default liveries to match new texture spec. User made liveries will work with no changes required! New liveries can make use of the improved blank textures and normal maps! Updated interior with new panel, new seats, new fixtures, interior trim, and window frames. Updated flight model with better airfoils, fuel consumption, and cruise speeds. Adjusted trim ranges and effectiveness. Several FMOD improvements and bug fixes. New engines, new props, tuned flyby and so many other adjustments. The same night lighting technology implemented in the 2T has been brought to the 2B which greatly improves the panel visibility in low light conditions. Added Linux support Improved autopilot engagement logic Added multithreaded texture uploading to GPU Improved Ammeter Updated libacfutils version As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy this latest update, and stay tuned to the forum as we continually announce the latest happenings.

Hello All, This will serve as a formal forum announcement that we have released the version 1.6.2 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.2 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: Standby VOR From/To Indicator (wrong dataref assignment) GPS, NAV, ILS, VOR, Runway EADI/EHSI Symbology (inadvertently missing in last update) Decision Height Knob (Added HOLD option for faster adjustment) Taxi Light (adjusted length) Flap Joystick Binding (fixed wrong parameter assignment on handle write function) Flap Joystick (increased tolerance on detents) Flap Deflections (flaps were not extending to proper angles) Brakes (fixed logic for all sim brake commands) Commands (created/verified overrides of sim commands for IAS, A/P Altitude, and DH) Nav1 Data (corrected wrong use of nav2 variable reference causing hard error) Autopilot (added logic for alarm kill on re-engage) Engine Temp (All new logic and ITT values) Flap Indicator Gauge (changed animation to match new deflections) Trim on Autopilot (fixed erroneous arming of NAV mode on trim adjust when A/P engaged) Trim (added back manipulators and adjusted logic for all pedestal trim switches) Gust Lock Lever (added new commands to engage/disengage gust lock lever) Power Lever/Flight Idle Latches (verified auto-latch logic to insure PL can't be moved to Flight Idle in flight) 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. Stick Pusher (premature engagement will be revisited in v2.0) Autopilot Stability (will revisit in v2.0) Reported as bugs. These are NOT bugs!... VR config (verified commands from user log.txt warning are in fact in the VR_config file) Radio Audio Ident (verified audio working on navaids) Cabin Pressure (verified cabin pressure working correctly above 20k ft) Reverse Pushback: From one of our Saab Pilots ... "You can barely power back a saab when its loaded. Tiniest up slope and you can giver her full beans and it'll just sit there." IAS Bug Out of Sync (the default dataref may have been written to and it caused the bug to get out of sync with the Saab logic. DO NOT write to the IAS speed dataref!!) ADF Radios in Test Mode (Cannot recreate. The ADF radios default to "ADF" mode on load of the aircraft. This is new behavior in 1.6 per our real world Saab pilot beta testers. Perhaps you are using some hardware or scripts that are interfering with this or altering the behavior? 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.

Honestly don't know. We're not on any such timeline and that hasn't ever crossed my or likely @sundog's mind. You can always wait till after the discount is over if this is most important to you.

Hi, the problem is you are using too old a version of Mac OS X. The version you are using is four releases old and needs to be upgraded.

Server test just now ran at near 1 gig per sec, which is my ISP speed. So, nope. Not an issue with X-Aviation.

Because you obviously needed a nudge/reminder to start using the search feature too. The first few topics in the forum were about the same issue. That's just lazy posting, and not just by you. Did you even bother to read the post you linked? It literally explains why it was posted. "Please do not post various issues in the update announcement thread." If a topic you have issue with exists, you definitely shouldn't be posting a new topic for it.

It honestly is starting to amaze me how many people do not search or even look through recent topics to see if what they're going to post about has been covered. This isn't meant as a personal knock on you, Dave, but people really need to get in the habit of it.

Hello All, This will serve as a formal forum announcement that we have released the version 1.6.1 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.1 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: First Officer RMI Needles (wrong variable assignment) Autopilot Climb Mode Speeds (not updating XP Dataref properly) Autopilot IAS Mode Speeds (not updating XP Dataref properly) Vertical Sync Fixed bug causing crash when Vertical Sync Button was pushed Adjusted logic to set XP Dataref in Vert Sync Mode CRS1 Knob (corrected OBS command for CRS1 knob when NAV2 is HSI Source) Door OH Annunciators not functioning (wrong variable assignment) Charts (Fixed overlapping Mesh) EHSI From/To Flags (Fixed incorrect logic Note: Per the AOM the from/to flag is never displayed on "second course" of the EHSI. Altimeter Needle Animation (wrong Dataref assignment) System Temps (Verified all for accuracy Deg F vs. Deg C) EHSI Nav Mode Annunciator(s) (LOC vs. VOR) CTOT (Left Engine not responding properly on CTOT knob decrement) Right Engine Condition Lever Fixed right CL logic for engine start. Fixed Electrical System Relay and Bus logic for engine start (Motoring/Direct) Changed Engine Start Switch Logic (Motoring/Direct) Starter Motor (fixed sound logic) Cargo Door Handle (changed animation init value Cargo Door (changed animation speed) Main Door (changed logic to prevent closing if stairs are deployed) Changed default prop disc texture(s) to .png (xEnviro bug) Standby VOR (fixed logic to write per frame) NOTE: From/To Flag is reversed and will be fixed next release IAS Mode EADI Annunciator (flashing continuously) Engine Heat Visuals (added back in) Additions: Brake (hold) Commands Gear Uo/Down Commands Logic to allow binding flaps control to joystick (lever) ITT Temps (changed logic to include ambient) Reported as bugs. These are NOT bugs!... Use of Experimental Flight Model NOTE: The experimental flight model is NOT required for the Saab. As of 11.52 you can use the EFM if you choose. HGD/SLAVE BUTTON Previous versions of the Saab modeled this incorrectly because we didn't have accurate Flux Detector errors. The HDG/Slave button(s) in v1.6.0 now provide slaving to the flux detector for error correcrtion. Nosewheel Tiller There seems to be some confusion on how this is implemented. We have provided two (2) options (selectable in user preferences): Use Tiller Checked (ON) - This allows you to use the in-cockpit tiller (manipulator) to steer. Use Tiller Unchecked (OFF) - This allows for mouse/hardware steering. In addition... steering is only available when the following criteria are met On the ground (WOW) Hydraulic PSI >= 1500 Aircraft is moving Tiller is engaged (depressed) DME not indicating distance on ILS The specific ILS being referred to did not have DME. C/L not syncing with hardware when moving the hardware levers fast You must keep your hardware in sync with the manipulators (use the TQ viewer) GPU available with chocks/no brakes We will consider this feature for v2.0 INSTRUCTIONS: The engine start procedure has changed slightly and now exactly matches the AOM. After you have established how you are going to provide power for the start, the two sequence options are as follows: MOTORING START: Ignition Switch to "OFF" Condition Lever to "FUEL OFF" Move and Hold Start Switch to appropriate aide Check Engine Stabilized (approximately 20% Ng and ITT Below 175˚C) Move Condition Lever to "START" After 1 second (but within 2 seconds) set Ignition Switch to "NORM" After Light-Up release Start Switch (If you want to see detailed example of a motoring start just use the Auto-Start Feature and follow the steps) DIRECT START: Move Condition lever to "START" Move Start Switch to appropriate side and hold for approximately 2 seconds Monitor Power Plant parameters accordingly. That's it! Once the engines are started you can proceed with the rest of the necessary steps to go flying. 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.

It's ready when it's ready.

It wasn't because of your input, so no need to be sarcastic. This stuff was already well covered in the forums.

Not everything is Apples to Apples in hardware and how it's applicable to someone's use, @Cam. Not sure why you're trying to stir a pot. As I recall, that individual with the 3090 was also a VR user, which does change things quite a bit too. Neither here nor there though. Everyone has different monitor resolutions and pixels to drive. You don't know what rendering settings people choose, and that's a factor in all of this. At the end of the day, I think @dlrk has fine expectations of settings if he's already flying through 3 hours of a flight. Doesn't seem unreasonable. If such is the case, it sounds like he stands to benefit from such an upgrade.

VRAM more than anything.

Windows 7?