JGregory

My thoughts... 1. Your condition levers were probably set all the way forward and not at the MAX detent as required. 2. As stated by others above, this will be fixed in 1.4.2. 3. Apologies for the documentation being outdated. You no longer need to assign your condition levers as in the past. You can simply use the standard X-Plane axis bindings and assign "prop1" for the left and "prop2" for the right condition levers.

Please post your GizmoLog.txt and Log.txt files. And, if you are running Saab v1.4.1 in XPv11, there is not much we can do except to note the issue for a future update.

The RMI (gauge) will track either an ADF or VOR, as selected by using the switches on the RMI gauge itself. And, the NAV1 or NAV2 radio must be tuned to a valid source and receiving a signal for the needle to display the bearing. The RMI gauge needle WILL NOT point to the waypoints in a flight plan from the G530.

The fix will be available in V1.4.2.

This is a known bug that has been fixed. See here.

Yes, you can uninstall and re-install. I suggest you e-mail support@x-aviation.com for guidance.

The log files only show that XP crashed but do not indicate why. The first thing to try is to remove all your third party plugins (except Gizmo) and then test the aircraft. If you have no crashes, then you can start putting the plugins back one-by-one and and test after each one to see if you can narrow down the problem. You have a lot of custom scenery as well and you might be exceeding VRAM. So, you could also try removing all custom scenery and then testing. Then place them back one-by-one and see if that reveals anything.

Using the Saab v1.4 in XP11 is at your own risk and we will not be addressing any erratic behavior you are experiencing for that version. We will take these things into consideration for v1.5 and v2.0. When reporting these types of issues it would be very helpful if you provide exact steps to recreate the problem (if possible). It is also important to include your Log.txt and GizmoLog.txt files.

You should contact X-Aviation directly.

Both of these bugs were fixed for v1.4.1. In addition, with this version we added code to write a log debug entry indicating that the v1.4.1 scripts had loaded, which does not appear anywhere in your logs. So it appears that you actually have not updated to 1.4.1 or the update was corrupted.

Yes, that's the correct command. However, you need to "HOLD" the command for a second or two in order to engage the Autopilot.

That DataRef (and others with "LES/saab/hide/" as a pefix) are not live. They are/were used for performance testing and debugging. We do not recommend that you use any of these DataRefs as you will see unexpected and improper behavior.

Kent, Thanks for the report. This bug was already fixed and will be available in the next update (1.4.2)

That screenshot is only part of the console window. We need to see any lines that are shaded in red (scroll down to find)... OR.. send us the log.txt file and the GizmoLog.txt file.

Carl, If you want to diagnose the problem correctly, remove ALL of your plugins and then start testing. If you have no crashes you can start adding each plugin back one at a time to determine which one is causing the problem.

Glad you got it worked out.

Are you saying you can't control the zoom regardless of your user preferences setting?

The calibration (assignment) of the condition levers is no longer required as of Saab v1.4. If you need to calibrate your joystick you can do that within X-Plane itself.

There is nothing in the logs to indicate the Saab is causing a problem. You are running (3) AI aircraft as well as (2) plugins (X-Enviro and XPUIPC). My only suggestion at this point is that you remove the plugins and decrease the AI aircraft to zero, then see what happens.

The hydraulic system will cycle periodically as the pressure drops and the pumps kicks in to recharge the accumulator. It's perfectly normal behavior. The cycle will happen more frequently when using hydraulically operated systems like steering, flaps, etc.

No, the Saab does not need FlyWithLua to function properly.

Dscho, I just tested this using Saab v1.4.1 in XP10.52r2 and could not recreate the problem. And, I waited much longer than 20 seconds. If you can give us some more details on exactly what you did when tuning the frequency, using the transfer/mem switch, etc. that would be helpful.

I created the command, but it is not available yet. Will be in 1.4.2.

Marshall, I know what the issue is with the commands, and this will be fixed in v2.0. Thanks for the feedback. In the meantime, if you hover your mouse over those "empty" spaces in the buttons list, the actual command name will be revealed.