JGregory

Whenever you have problems and post them here you should also post your Log.txt and GizmoLog.txt files.

@Captain_Crow It looks like you had the DCP "SELECT" dial set to GPS (LRN) when you were setting the course. The DCP "SELECT" dial should be set to NAV (VOR1) in order to set a course to a VOR. My guess is that you had not turned on the G530 prior to this error occurring. That being said, this is a design flaw (initialization timing) that I will need to correct. The system should not produce an error if you try to adjust a GPS course when you are in NAV Mode. For now, in order to prevent this error from occurring, make sure you have the G530 turned on PRIOR to using the CRS1 Dial. This should prevent a hard error regardless of which mode the "SELECT" dial is set to. Please report back if this workaround resolves the issue. I will advise as to if, when, and how we will address this bug.

Thanks for the input. We will take all of your suggestions into consideration for v2.0.

This is exactly how the real aircraft behaves. The power is removed from the those busses to protect the avionics instruments from electrical spikes during engine start.

You can't do that. Use the standard X-Plane keystrokes to raise and lower the flaps.

Whenever you report a crash you should also post your Log.txt and GizmoLog.txt files.

John, There are some differences between the current version of the Saab (1.5.1) and the manuals, but nothing that is critical to overall operations.

No. Please verify that file "Custom_LightsCabin.obj" is in the objects folder. That should not be required, no. Just a reminder: The cabin lights will not work without power. This will be something we will look at for v2.0.

The real instrument actually allows for setting in 100's or 1000's !! This will be incorporated in v2.0 Not true. You can control the flaps via the standard X-Plane keystrokes. Note that power is required to actuate the flaps. I tested this when you reported it and could not re-create the issue. The switch behaved as expected and the DataRef value did not change randomly at any time.

This feature will be available in v1.5.1.

My mistake, this is a feature that we added for the v1.5.1 update, not for 1.5.

At 3:47 in your video it shows that you you have the Tool Tray "disabled" in the Gizmo Preferences.

Free?, no. A discount, yes.

ummm, you previously posted (just yesterday !!!!) that you had tried this and it didn't work, see this link... What are you assigning your joystick to ???? The Saab v1.5.1 update will allow you to assign both condition levers to one axis. See the link I referenced (above).

Please do NOT make double posts regarding the same subject. Your question was answered in this post.

in Saab v1.5 you should assign your joystick to "prop" if you wish to have it control both Condition Levers.

Wait... if you disconnected the hardware (as I suggested in step 1, and you confirmed stating "Did all those steps"), how can you be using your joystick ??? Also, what do you have your joystick(s) mapped to?

Is this happening on EVERY flight? We have had a couple of reports of the aircraft shuttling down (randomly), usually right after landing. There are some other forum posts here where this is discussed. My best guess at this point is that it was due to overly aggressive movement of the power levers. You stated " ... and I pull full power..". You should not be pushing the power levers to their maximum at takeoff. This will overheat the engine and "could" cause a shutdown. I noted that you are using some hardware and also have AI aircraft enabled. If you want to help diagnose this issue, you could do the following: 1. Disconnect ALL hardware. 2. Disable all AI aircraft. 3. Disable any third party plugins (except Gizmo). 3. Reload the sim. 4. Fly the Saab and report back if you have the same issues. I would also be interested to know what your frame rates are.

There is a post in the thread you linked (see this) that explains how to fix this (temporarily). The bug has been fixed on our end but the update that includes that fix has not been released yet.

This is a known issue and has been fixed for the next update (v1.5.1).

We DO NOT "override" the X-Plane mixture, but we do control it. As you stated, the mixture is usually not an issue in a turboprop, so if you are using hardware assigned to mixture, especially if it is "noisy", that would definitely be an issue that YOU will need to control at this time. The parameters that control the mixture ratio in the Saab can be found in this post. All systems, including how mixture is handled, will be addressed for Saab v2.

@parsec71 Nothing you stated seems to align with the comment from the OP about these files causing "major problems". And, since we have not had ANY reports of audio problems, I'm still curious just what the OP meant by that.

Yes, the "A" model does the same, and this is modeled. The fact that the engine will not re-start may be an X-Plane thing, but it will require some investigation to confirm. This will take some time and may actually end up being done for v2.0. Not sure why, but i can tell you that moving the power levers quickly into reverse is extremely unrealistic. The engines have no time to spool down, and that could be part of the problem. Normally, you would be at "Flight Idle", or slightly above, at touchdown (low engine speed), and then into Beta and Reverse. I'm not sure that our model is wrong in that respect.

Here are the conditions where the engine mixture will be set to zero (0): 1. Ng (N1) Overspeed when Ng >= 110.0 2. Np Overspeed when Prop RPM > 1573 3. Fire Handle has been pulled 4. Condition Lever is placed in "FUEL OFF" position. I was unable to see the prop rpm gauge in your video to determine if that is where the problem is. I suggest you re-test knowingly the above outlined parameters.