JGregory

Those logs do not make reference to the Saab at all. The last aircraft that you attempted to load was the TBM.

A word of caution... the Datarefs being used in this script will be deprecated with the next update of the Saab.

There are MANY videos available regarding the Saab 340A. If you want me to review something that you are referring to you need to provide a link.

First, you refer to a video several times but have not provided an attachment or link to it. Over the last several years the engine model in X-Plane (especially turboprops) has changed considerably. We have made some adjustments along the way. However, due to the extensive customization we have implemented, we have had to do a complete re-write of the engine code. An update is imminent that will correct the issues you are describing. You make reference to "air conditioning levers" and a "max" position. The Saab does not have any "levers" related to A/C. And there are no switches or knobs that are marked "MAX'. Are you referring to the A/C temperature selector knobs or maybe something else? The load on the engines from use of the air conditioning (bleed air) was not originally modeled. This is something that we are reviewing for a future update. As the steering is hydraulically driven, I don't think there would be any change in steering behavior due to the air conditioning being on.

Ummmmm... v2 has not even been started except for some preliminary planning. Maybe you meant the next update ? If so, that will be RealSoon™.

No, the LES Saab 340A has the standard VSI.

Arni, Nothing has changed. The auto-start option is still selectable in the Gizmo Tool Tray (menu on right side of screen). If you don't see that then there is probably something wrong with your installation. The Saab was never able to use the "start with engines running" option. This is something we are going to be looking into for v2.0.

That is also fixed for the update.

The correct empty weight should be 17215 lbs. This will be fixed for the coming update.

And we appreciate that !!

Sorry we do not announce release dates in advance.

Patience guys, an update is coming soon that will resolve all those problems, and it's free !!!!

Laminar did not change anything in 11.50 regarding manipulators, so the Saab buttons, knobs, switches, etc. should work exactly as they had in the past. That being said, a new update for the Saab is imminent and all manipulators have been updated to current standards.

The reason I asked you to try the plugin solution is that we have not had any reports similar to yours. So, that was an attempt to eliminate possible problems. That being said, we are very close to releasing the next version of the Saab, which will be free to all existing customers. This should resolve all your issues as there is a newer version of Gizmo than the one you are using and the code (from the Saab) that you are reporting showing errors with the timers doesn't even exist anymore in the new version. So, rather than trying to diagnose an issue that is "old news" (ie. old version), I ask that you be patient and let us know how the new version works when it is released. I know that's not the answer you probably want to hear but it's probably the best for now.

The Log file does not point to why you had the crash, so it may not be the Saab. You have a LOT of plugins installed. I would recommend the usual diagnostic protocol... remove all third party plugins from the plugin folder (except for Gizmo), store them in a safe place (not the plugins folder), and then test the Saab again. If you do not get any crashes you can put the plugins back in the folder one at a time and test each time. If you get a crash after re-installing a plugin, that plugin is most likely the cause of the problem.

No, the current version of the Saab does not have commands for the ToolTray items.

PM sent.

Not sure about the HP Reverb, but there are many people using the Saab in VR.

Anthony, While I appreciate your attempt at diagnosing the problem, these facts still remain the same.... 1. The engine/prop code in the Saab is very complex. We override the throttles and the props. Therefore, observing the Dataref you mentioned above is not applicable and really does not provide any diagnostic value. 2. The next update (yes, I know it's taking longer than expected) has all new manipulators and logic for most of the systems. As previously stated, we are no longer "patching" 1.5.1. So, whatever answers/conclusions you've arrived at are not going to be addressed or applicable to the next update. Given these two facts alone, I suggest that you not put any further effort into diagnosing an old version that will not be patched and whose code is changing drastically in the next update. When the new update is released I hope you will try it out and let us know how it works for you. If you are still having problems we will be happy to work on diagnosing them against the new systems logic. FYI... none of our internal testing of the update is producing any kind of issues with the engines not starting, with or without hardware.

Yes, that, and anything else that is "plugged-in" (USB, etc) would be considered "external" hardware.

I think at this point you will just need to fly the passenger variant until the next update comes out. Even if we could verify your issues, we are not making any changes or updates to v1.5.1. We will test the cargo version for the next update to verify it is flying correctly.

I would like to add... the next update of the Saab (before v2.0) will work in Vulkan/Metal. And that update will be free to all current customers.

Some hardware requires a plugin to interface with X-Plane.

Not sure why you would ask that, but hardware plugins certainly could be a problem.

yes, hardware = joystick, rudder pedals, yoke, throttle quadrant, panels, etc... anything plugged in !