JGregory

Your trim is indicating significant nose-up in ALL of these screenshots ! Try trimming for neutral prior to engaging the autopilot.

That's probably a bug. I will look into it.

Guys... you can see in the video that the Condition Levers are set @ 82˚... that WILL set off the alarm.

This may be what you want...

First, the Saab does not have a "flaps 5" setting. There should be absolutely NO difference between increasing or decreasing the flap setting, the gates are the same. We are limited in the tolerances of the gates so we won't be increasing them any further. This may be related to your hardware, maybe another user with the same setup can help out.

This problem will be fixed in one of the next couple of updates.

If you want to do a test, try it it OpenGL and let us know.

I have not seen this happen in the test flights I have done. You and MJRhealth are the only ones reporting this as an issue. At this time I don't know if there is a problem with the Saab or a problem on your end. I will continue to test and see what I can find, if anything.

Glad it worked out for you !!!

It's a little difficult for me to gauge how far that wall is but my guess is that what you are seeing is more than likely some kind of issue in X-Plane, not the Saab. Or, it may be a scenery issue. Does the same thing happen with the Landing Lights? Is that a custom airpor /scenery? Are you using Vulkan/Metal or OpenGL ?

The taxi light and landing light were adjusted to be brighter in 1.6.2. I will make another slight adjustment to the taxi light brightness for the next update. However, we will not be able to adjust tilt until v2.0.

Are you using Auto-Start ??

Your condition levers are less than 83˚. Set them to MAX.

There is nothing complicated with this. The flight idle stop is depicted as the red line in the TQ Viewer. The Flight Idle Stop is not something you can control, it is automated based on several parameters. The latches allow you to move below Flight Idle (when on the ground) and can be controlled either manually or automatically as follows ..... If you select the option for "Use PL Auto-Latch" in the User Preferences then the latches are engaged automatically when the Flight Idle Stop is released and you do not need to engage the latches manually at all, EVER. If the "Use PL Auto-Latch" is not selected then you will need to engage the latches yourself manually. However, you will NOT be able to move the Power Levers below Flight Idle until the Flight Idle Stop is released (red line is NOT displayed). In ALL cases your hardware levers MUST be in sync with the cockpit Power Lever manipulators. This can be observed using the TQ viewer.

There is no way the taxi light was lighting up buildings that are as far away as the OP shows in that screenshot. And if it were angled down too far it certainly wouldn't light up anything in the distance.

This is probably related to the issue of being near the prime meridian as outlined in the release notes. Try moving to another airport that is significantly east or west of EGPH and let us know what happens.

Whatever is going on with the lighting in the distance has nothing to do with the taxi light. Please take a picture from outside the aircraft, at nigh, with the taxi light on, pointing at the area in front of the aircraft, and post it here.

Select User Preferences in the Saab menu on the upper right of your display when you move the mouse there.

The only thing in that log that might be an issue is this plugin ....'X-ATC-Chatter" You might try removing that from the plugins folder and see if that changes anything. Other than that I don't have any suggestions. Obviously sound volume is somewhat subjective so I'm not sure there is a problem here. Make sure all the Saab sound sliders are to the right to do a fair test.

Please explain what "crashes" means..... did the sim crash to desktop, or did the sim "hang", or something else? What airport were you loading at? Try moving to another airport that is much further away and see what happens. You are also running a LOT of plugins, which could also be causing an issue. If you want to test this then remove all the plugins from your plugins folder except for Gizmo. Then relaunch the sim and load the Saab and see what happens. If the sim does not crash then one of those plugins is causing a problem. Put the plugins back in the plugins folder one at a time and then relaunch the sim and load the Saab. Keep doing that until you get the crash and that will tell you the problem plugin.

We have had no reports of issues with the external sound. And, on my system, the external sounds are what I would expect. The external sounds should be considerably louder than the internal sounds. Do you possibly have another plugin that is interfering with this? If you want you can post your log.txt file here and I will look at it.

The Saab basically overrides all engine inputs, so for all intents and purposes it is a custom engine model. But we are limited in how much control we have over the output. I don't think we will be writing our own engine model... that would present far too many compatibility issues in the future.

Please post your log.txt file here. What airport were you loading at?

I don't use or even own that software so I can't really comment. However, in Saab v1.6.x all manipulators (except for some levers) are non-writeable. And all of them have associated commands, which is the right way to interact with the cockpit. So, if shared cockpit is working now then you should be fine.

Nick is right... Austin models turboprop behavior based mostly on a PT-6 because that is what he flies. We have overridden a LOT of the engine behavior but it's a balancing act. If we adjust the fuel flow to "fix" the ITT swings then the engines will respond too slowly. I think we have found a good balance for now.