JGregory

contact X-Aviation for support

Based on some other reports, it looks like 11.30 may be causing this issue. I will be discussing this with Laminar. Please post your Log.txt and GizmoLog.txt files.

I would suggest you re-download and re-install the aircraft. My version of 1.5.1 has not changed from 1.5 Did you make any changes to the aircraft in Plane Maker ??

Huh? Where did I state that you said the 737 didn't work for you? What I said was you stated "All other planes work fine." But, when I asked if you had the 737 you said no. And then you stated " The ATC works fine in every other plane, both freeware and payware." I was simply pointing out that when you stated "all other planes" and "every other plane" (note you said All and every) it was not quite accurate because you don't own the 737.

I asked about the 737 because you stated "All other planes work fine." Apparently, that statement wasn't quite accurate eh ? The other reason I asked is because the 737 and the Saab share the same sound engine. If the same problem exists in the 737 that would be a possible indicator of where the problem lies. If any one else is reading this, and you have the Saab and 737, please let us know if you are experiencing this ATC problem as described above. @Dr.Strangelove Please post your Log.txt and GizmoLog.txt files.

Do you have the IXEG 737 ? If so, does the ATC work in that aircraft ?

We don't have any logic in the Saab that would affect ATC. In addition, the differences between the passenger and cargo versions are purely visual, there is absolutely NO difference in the systems, so there is no logical reason why one would work and not the other.

Not a bug. The sound engine used in the current version of the Saab does not function in replay mode.

click and drag the ON/OFF dial.

The mini GPS was a removed after we installed the Garmin, which you can use to enter fixes on your flight plan. You no longer need to configure or assign the condition levers, so that feature is not necessary anymore. The documentation has not yet been updated to reflect these changes.

What version of X-Plane are you using?

There is nothing obvious in the log files that indicate why you are having a problem. However, you do have a lot of plugins installed. I would follow the usual test procedures of removing all your plugins (except Gizmo) and then test the Saab and see if the problem persists. If the problem resolves, add back the plugins one at a time and hopefully you can determine which one is causing this issue. Note that just "disabling" plugins is not the same as removing them.

When you are reporting issues you also need to post your Log.txt and GizmoLog.txt files.

You should let the engines settle down before going from "unfeather" to "MIN". Much of the engine model in X-Plane has changed in v11. The Saab code for the engines is very complex and quite a few lines of code. It would not be prudent to "tear this all down and rebuild it" for the current version of the Saab. We also need to see what v11.30 will do as it brings even further changes. Once 11.30 is final we will decide what, if anything, needs to be changed. However, these kinds of nuanced issues are something that we will more likely be addressing in v2.0. We've already fixed the bank angle issue but I am not sure exactly when that will be available.

Tim, The bank angle issue has been fixed. Not sure when it will be released.

You have asked your question in the right forums. You didn't describe what your mapping your levers to. However, I don't think you can accomplish what you want to do. Maybe one of the Saab users has some ideas on this.

Contact X-Aviation support via e-mail.

See this.

Is this crash repeatable? You might try removing all your plugins (except Gizmo) and then test again. If the problem is resolved add each plugin back in one at a time and then test again to see if you can find the problem plugin.

Firmware versions are different than the Gizmo version. In the plugins menu you can select Gizmo64 -> About Gizmo64 to get the Gizmo version #. The Saab requires Version 1802270200 or above. I believe the IXEG 737 is at version 1.21, you may want to upgrade. Since the aircraft is working for you now I will consider this resolved.

Don't be so sure. There have been a LOT of changes in 11.30. We usually do not provide support while X-Plane is in beta, but we do appreciate the feedback. What is "diff.brakes" ?? Making a statement that begins ... "It looks like" ... is not something we can use to do diagnostics or debugging. How did you determine that there was any braking happening? Did you observe the braking DataRefs? Did you disconnect your hardware to see if the problem persists? The systems in the Saab do not do any "autobraking". We have previously stated that any new features will only be considered for v2.0 of the Saab Note: Any time you are reporting a problem you should also post your Log.txt and GizmoLog.txt files.

Specifics matter. Gizmo will get installed each time you update an X-Aviation product that uses it (ie. the IXEG 737 and the Saab 340A). Updating to the most current version of Gizmo should not interfere with the operation of either aircraft. And again, thousands of users have both these aircraft installed and are NOT experiencing this problem. Please provide the version number(s) of both aircraft as well as the version number(s) for Gizmo in both installations.

I have no solution for you at this time. No one else is reporting this problem.

Your Log files do not indicate any issue that would relate to the scroll wheel options. There must be something about your setup that is different because we have not had complaints of the scroll options not working. The only thing I can suggest you try is to unplug any hardware you are using and see if that changes anything. With regard to "views"... the "native" X-Plane view system utlizing your numeric keypad should work fine in the Saab and would be the best way to assign a close-up view of a particular panel.

Just did a test flight. Temps and torque are a little sensitive, but I don't think it is any different than it was in 11.26. When we get to V2 these issues will be looked at, but based on our project list and schedule it's going to be some time before V2 is available.