JGregory

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.

As of v1.6.x many datarefs are now non-writeable. When v2.0 is released all datarefs will be non-writeable. I will make a note to look into creating a command for the GPU (available) but I can't promise what version of the Saab this will be included in.

As was posted elsewhere, this is a known issue and will be fixed in a future update. No need for any further reports.

Let's take this one step at a time. If you can recreate one of your problems (ie. runaway throttles), please post the exacts steps to make this happen and describe exactly what you are seeing/experiencing when the problem occurs. Screenshots and/or video clips would be very helpful. You many want to wait until v1.6.4 as there are some changes coming to the throttles mainly regarding the Flight Idle Latches and Flight Idle Stop. If you still have problems after trying 1.6.4 then let us know by following my instructions in the first paragraph above.

Metal is supported, but that doesn't mean there might not be (X-Plane) bugs as metal/vulkan are still relatively new. My system is almost identical to yours and I am having an issue with the temp gauge LEDs when using Metal. Suggest you try OpenGL as a test and let us know so I can report this to Laminar.

We have already acknowledged this problem elsewhere in these forums and in the update release notes. Comparing the Saab to any other aircraft is irrelevant and unnecessary. We are working on a fix and will advise as soon as it is ready.

Mike, Are you using Metal in your graphic selections ? If so, please change to OpenGL and report back.

Yes, it can happen while flying.

I believe that is the way it works IRL. That mode is a one shot thing and needs to be reset by maintenance.

All of the issues reported in 1.6.3 have been fixed and will be in the next update. The update is being packaged as we speak.

I just checked the de-ice systems in the Saab and they are working as they should. If you are unhappy about the way ice accumulates I suggest you file a report with Laminar.

There is a 3 minute gap interval cycles.

It looks like you were flying near the Prime Meridian. This is a known issue that is outlined in our release notes.

Ummm, you mean 1.6.3, right? 1.6.4 is not out yet! Sounds like you stalled the aircraft on descent. Condition Lever in the T/M position will yield unpredictable and usually "BAD" results, which is what it sounds like you did.

I just tested this and it is working as expected. Please post your log.txt file.

More generalities. If you want to start over you can start a new thread. However, if you do that, I suggest you take a different approach. Or, better yet, send me a PM.

Moving the Power Lever(s) has absolutely NO effect on the Condition Lever(s). If that is happening it is something related to you setup. Is that (waggle) a technical term? Please try to be a little more precise as to what you actually did. You didn't even bother to mention whether or not you used the TQ viewer to see if your hardware was synced. Or how about attaching some screenshots or video? I can't look at the code based on anecdotal musings. We do not have even ONE other customer reporting the same problems your are experiencing. Based on that and years of experience I would suggest that this problem is somewhere on your end. You must have me confused with someone else. Specific references please. Also, if you really read through the forums then you would know that we always require a log.txt file when you report problems but for some reason you didn't attach one. All of our other customers seem to be doing just fine. Again, no one has reported any of the specific issues you are supposedly experiencing. Why would I do that when you are the ONLY person reporting this issue and your first forum post here include this... "The plane is just completely unfunctional because of this. What a horrible experience ". Do you really believe that kind of behavior deserves an apology, seriously?

Those commands were deprecated in v1.6.0. If you search for "les" or "sf34a" (lower case) in the command (keyboard) selection page and it does not appear, then your installation is probably corrupt and you should try installing v1.6.3 again. You do not need to install 1.6.1 or 1.6.2, you can update directly to 1.6.3 from any previous version.

The GNS430 display of nav data date is NOT static. There is currently a bug in logic and will be fixed in the next update.

We do not have ANY reports of problems with the condition levers upon landing. The Power Levers are restricted from going below flight idle until all wheels are on the ground. If you are using hardware it is necessary that your hardware levers are in sync with the cockpit manipulators and will not function until they are in sync. You can observe this using the TQ viewer. A little hyperbolic, don't you think?

The commands that you are displaying are deprecated in v1.6.x. Either the sim is still caching those or your installation has failed. The new commands can be found here ....

This issue should be resolved as of v1.6.3. Let me know if you still have problems.

There are several lights in the Saab, please be more specific.

This feature is not modeled in v1.6. We will be considering this for v2.0.