JGregory

I assume you mean to sync the baro setting? And, no, we won't be doing that.

It's a known issue and will be fixed in the next update.

Yes.

The Emergency Bus is powered by the normal system or the Emergency Battery when a battery relay is closed (via battery switch). The annunciator "lights up" when there is no power to the bus or, if being powered by the Emergency Battery, if the voltage is low. There is not status indicator in the cockpit.

I think you mean 50 right?, not .50 ? There is really no way that can be happening without outside influence (ie. plugin or script). Are you absolutely positive that it is incrementing (not displaying) in 50ft steps? can you provide a video showing this? If you want to start some debugging I suggest you download the X-Plane demo, install the Saab, and then see if the same thing happens.

Wait, I thought you originally said it was incrementing by 100???

please send me a copy of your log.txt file immediately after loading the Saab

it should be 4000.0000, or 4100.0000

OK, thanks for the help.

So you were using the manipulator knob to set the altitude, correct ?

I just tested this and I could not get it to set an "intermediate" value, it is always set to an even hundred as it should be. Are you using any hardware, plugins, or scripts to set the autopilot altitude ?

Did either (or both) of you use the ALT button on the MSP to select Altitude Hold ??

We have "automated" the process of the flight idle latches. Instead of requiring you to use the command to lift the latches after touchdown, we automatically do that for you. The issue of being out of sync with the manipulators would exist whether or not we automated the latches or not because you would still need to wait for "all wheels on ground" before you would be able to lift the latches manually (with a command) and then move your levers into beta/reverse. The reason we "require" you to make sure your hardware is in sync with the manipulators is to prevent "snapping" of the power levers, which could result in sudden and unwanted throttle changes. We have plans to possibly provide audio feedback when you are at flight idle, but this will not happen until v2.0.

Yes

The issue has been diagnosed. Please see the release notes fro v1.6.2.

I can't tell you how much to spend, that's up to you. I was just pointing out that there are some differences between the two models.

Yes, you are right! However, the fix for this is out of the scope of the v1.6 update. We will revisit this in v2.0. Thanks for your input.

An AOM is different than a AFM. The "affordable" one you linked to is for a 340B, not a 340A, beware... there are differences.

your log.txt file indicates this.... 0:21:28.873 G64: error: Run(xp): Saab_Main: [string "JGX.1.Saab.00.lua.ra1"]:44378: dref.getFloat: NULL pointer error, invalid dref handle. 0:21:28.974 G64: core: Run: [OnError] 0:25:49.124 I/SIM: Exiting the sim without confirmation You didn't indicate that the Gizmo console opened or that you had any errors indicated in the console, but the first line of that log.txt excerpt should have automatically opened the console and indicated that error in red lettering. The good news is that I was able to find the bug and fix it. Since the log indicates that the sim was exited after this error occurred, there is nothing else I can research at this time. When you get the next update you will need to re-test your flight to verify that this bug was the reason for your problems.

Just tested this and it is working as expected. The gust lock only affects the Ailerons, Elevator, and Rudder... NOT the flaps Note: Flaps require Left Battery Bus power AND Main Hydraulic Accumuoator pressure > 1650.0 in order to actuate.

Prime Meridian seems to be the problem.

Please post some screenshots and the log.txt file.

The head shake plugin is still being loaded.... from your log.txt ... "Loaded: C:\Users/Bruce/Desktop/X-Plane 11/Resources/plugins/HeadShake/64/win.xpl (com.simcoders.headshake)." We do not have any other reports of this problem. Suggest you remove all your plugins (don't just turn them off) and then test and see if the problem is gone. If it is gone then put the plugins back one at a time and test again until you find the problem plugin.

what happened to ..."I'll not debate the point any further ..." ?

Maybe/probably ?