JGregory

Darran, You have several plugins installed, and you are using external hardware. My suspicion is that one of these is the problem. The correct way to diagnose this is to unplug ALL your hardware, remove ALL your plugins except Gizmo, PluginAdmin, and any whose name begins with XP. Then launch the sim and test. Another option would be to download the X-Plane demo, install the Saab, and test. If the problem is gone, you know it was either a plugin or hardware causing the issue. Place your plugins back in one at a time and test each time. If the problem returns you know which plugin is causing issues. Do the same with your hardware, plug each item in one at a time and test. Report your findings back here so we can determine your next step.

No, there is not. The dome lights are true "spill" lights, there are no _LIT textures associated with them. Your apartment is not a simulation. Lighting (especially shadows in daytime) is particularly difficult to simulate. The "map" lights (overhead) should work. I will take a look at what we can do for the next update but this may need to wait until v2.0.

We believe we have isolated the problem. The fix will be available in the next update. No, I cannot tell you when the release will be

darran, The point is.. if you are going to report a possible bug in the X-Aviation/LES Saab 340A, please use in-cockpit pictures so we can verify what you are reporting. I am still waiting for your Log.txt and GizmoLog.txt files.

The picture you posted above is NOT from our Saab 340A.

Please post your Log.txt and GizmoLog.,txt files.

The speed displayed on the EADI is a "Flight Advisory Speed" for long range cruise. When using the charts you are referring to, you need to set your power (torque) according to the chart (ie. max cruise power), not to match the EADI "Flight Advisory Speed".

Run the Saab in 11.41 and then report back. We will not diagnose bugs with the Saab running under a beta version of X-Plane.

If you are going to report bugs you MUST attach your Log.txt and GizmoLog.txt files. In addition, Vulkan is in beta so we do not make any guarantees of compatibility with the Saab.

We have not tested the Saab in 11.50. Since 11.50 is in beta we are not offering support for that version at this time.

At 10,000 feet at max cruise power your indicated airspeed should be between 225 and 231 knots depending on weight. Your indicated airspeed is 198 knots! You stated that you have power set to match the speed...how did you determine the proper speed?. This tells me that your power levers are not set properly and that is why the torque is too low. See Page 77 of the Charts.pdf for the speed.

We can't diagnose any problems unless you post your GizmoLog.txt and Log.txt files.

You still have plugins installed and several custom scenery packages that have plugins as well. I strongly suggest you download the demo and install the Saab in the demo. That will provide a completely clean installation that we can work from.

Your Log.txt file is 151mb, which is extremely large and mostly due to the plugin Airport Navigator writing messages to the Log. You are running a LOT of plugins as well, some of which are showing errors. You system is on the lower end of recommended specs. You cannot run unlimited amounts of scenery and plugins. Normally we would suggest you remove your plugins (except Gizmo) and see if that resolves the problem. However, due to the extent of the plugins and scenery you are running I would suggest you download the X-Plane demo, install the Saab in the demo, run the Saab and see if the problem persists, and then report back here.

I am unable to open the Log file, please post the original .txt files.

It sounds like the Saab scripts are not running. Please post your Log.txt and GizmoLog.txt files here so we can review them.

As I requested previously, please attach your Log.txt and GizmoLog.txt files from a session when these problems occur.

Is this happening with just the Saab? or all aircraft?

The pitch wheel and turn knob are unique in the way they are "actuated". The coming update will have a new manipulator that more closely matches the real-world aircraft. Unfortunately, the (X-Plane) manipulator that we need to use does not include scroll wheel capability. We will continue to test and modify this as necessary to make it easier for the users to use.

Please attach your Log.txt and GizmoLog.txt files.

it's the one marked "PWR" ...

The update will include a new VRconfig file, yes.

You still have a LOT of scenery files that are loading their own plugins.

What you are experiencing is the X-Plane shared Lua memory pool running out. The logs are reporting which program was running at the time, but it does NOT mean that program is the culprit. Gizmo has been tested extensively and it has never used (or abused) the Lua memory pool. So, even though the last two (2) logs you posted show Gizmo reporting the error, it is not likely that Gizmo is causing the problem. You previously indicated the following... That indicates that Gizmo was not abusing the Lua memory pool and the problem is most likely another plugin. We also have extensive experience with SkyMaxx so I doubt that is the problem either. The only way to narrow this down is go back to your stripped down version of X-Plane (all plugins and custom scenery removed except Gizmo) and then put back the plugins and custom scenery one-by-one and run the sim again until you find the offending plugin.

This should have nothing to do with the Saab. The documentation is out of date. You no longer need to assign your condition levers though the Saab menu system, simply use Prop1 and Prop2 in the X-Plane UI for hardware.