Cameron

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?

Right side menu. Open the TQ Window. Make sure everything is aligned.

It's not as much as you might think, sorry to say. No, but what @sundog has told you is sound information. Logical deduction brought about that conclusion.

I also encourage you to use the search feature in the forums. It's been discussed many times.

And you're receiving the error still?

You guys will need to re-download and re-install the product.

@Tim013 Look for changes like that in v2. After 8 years of free updates on this version, we are sunsetting any new visual changes. At this point it's purely a bug fixing and closing the door situation for this iteration of the Saab.

That looks as intended. The lenses are also there on the lights. You can see them at various angles.

But it's already been almost 6 years.

Known issue, being worked on.

Windows 7 as well? You guys really need to think about getting out of ancient OS's! If not just for future driver stability and enhancements for things like Vulkan. Sheesh, guys.

I do not agree. Win 7 to Win 10 was the most painless transition of any MS OS I had ever done. Your mileage may vary, but trying to run a very outdated operating system that is not even supported by MS is not wise either. You should really upgrade before it becomes too late to actually safely migrate your data. There is likely NOT going to be a path from Win7 to Win11 (or whatever it will be called). THAT would be foolish and a hassle.

That's the issue, unfortunately. The above poster also went through this. You can see the resolution here:

What version of Windows are you on?