Vantskruv

╲╲╭━━━━━━━╮╱╱ ╲╭╯╭━╮┈╭━╮╰╮╱ ╲┃┈┃┈▊┈┃┈▊┈┃╱ ╲┃┈┗━┛┈┗━┛┈┃╱ ╱┃┈┏━━━━━┓┈┃╲ ╱┃┈┃┈┈╭━╮┃┈┃╲ ╱╰╮╰━━┻━┻╯╭╯╲ ╱╱╰━━━━━━━╯╲╲

As I always do, if aircraft has a GS indicator, I calcluate TOD and descend manually. 2000 ft/min, and try my best to hold GS speed through whole the descent. It is easiest in headwind, because you know that GS is low, and you can still keep the same GS below FL100. Tailwind though, GS is quite high, and it will be harder to hold the lower you go. Also, you may come in too fast at FL100, which means you need to slow down, which at that end means you have made a premature TOD. Often I try to do it by feeling, sensing to drop down a little later, depending on winds dow below. Hence VNAV is so boring.

About the first error, have you checked that you have 64 bit Python installed (or 32 bit if the plugin uses that architecture). Hence, for me, ELF errors is common if there is a mismatch between 32 bit and 64 bit architectures.

So, testing again selecting ARRIVAL for ZSSS, on the ground, no crash with v.1.1.1. Either the problem for my case is solved in v1.1.1 or my crash was a random one.

I had a recent crash. While in flight, I was pressing the PROC button on the MFD, and then scrolling down to ARRIVALS. When pressing ENT-key, the simulation froze up, and after a couple of seconds X-Plane crashed. I am not sure if any plugins interfered with this, but I think unlikely, because the crash happened with an action of my....but never say never.... Airport affected was ZSSS from global airports, X-Plane v11.26, maybe in my case there is some problems with navigraph data. Current AIRAC was 1812 rev 1. Used version v1.1 in the crash, now I have installed v1.1.1. I will try to replicate it to see if there is another crash later in the evening. Need to make some pancakes first. :) Log_TBM900_crash_ENT_ARRIVALS_ZSSS.txt

10. No mouse-drag for the altitude preselector.

Yes it is not fun when everything crashes. Therefore I've made three dangerous python scripts for X-Plane, which deactivates problem-inducing plugins. I.e. CEF plugin for FFA320, Gizmo and xEnviro. So it is always possible to fly the aircraft you want, if you know what is causing the crashes and can solve it by this method. Saab 340 is a great airplane, but I really miss xEnviro, I do not like the XP:s default weather, even with FSE and Reshade installed, the same goes for SMP. I'am currently not sharing the scripts, because I'm afraid it can ruin some others computer (hence they are renaming the plugin .xpl files to .xpl_). Also they are quite ugly where I am running the python scripts from BAT files, which I've shortcutted to.

Oh, that is sad. Have been looking forward for the update. Oh well then, Gizmo and the Saab will be put on shelf until problem is solved be either of the companies (Gizmo, LES or xEnviro) who is responsible for this.

You are running xEnviro, it seems there is some incompatibilities between Gizmo and xEnviro.

So deactivated all plugins except X-Camera, xEnviro and Gizmo (of course). And it did crash again. I disabled now xEnviro, currently no crashes have happened. Time will say what is really wrong. I will fly the Saab a while without xEnviro, and then I will activate xEnviro again and see what happens. Thanks for your support, great plane otherwise, I really like. Edit: I already sent a bug-report to xEnviro team, so I hope you can put your heads together if this is the culprit.

Hahah, here you go! The time of crash was 12:26. I will try to remove some more plugins. debug.log GizmoLog.txt Log.txt METAR.rwx OPENGL32.log stack_trace.txt xEnviroLog.txt

So, I installed Gizmo and the Saab 340. I now get frequent crashes in X-Plane 11 when flying the Saab, I do not see any major hints in the logs, but I have a suspicion what the culprit is. I think there may be incompatibility between Gizmo and xEnviro, either Gizmo or xEnviro makes X-Plane crash. Looking at the log of xEnviro, I do see at the time of crash it is polling for weather data. Reason I am posting here in the forum is that this Saab version is new, and it may not be a incompatibility between xEnviro and Gizmo, it can instead be a bug in the Saab, or it can be incompatibility between Saab and xEnviro.

v.1.5. Well, it seems for me the prop assignment does not work for both condition levers. Hence, it works to assign the condition levers to the separated prop axes number 1 and 2, but it is not possible to assign both condition levers to the main prop axis: Prop Main axis (controlling both condition levers) - does not work. Prop 1 axis (controlling condition lever 1) - works Prop 2 axis (controlling condition lever 2) - works So for those who has lesser than 3 axis on there joysticks (I think most people have 2 axis on their throttle joysticks), there may be a problem, as they need to assign the throttle axis to the keyboard (if they have the same problem as me). Lucky for me, I am able to assign both throttle levers to my smaller third axis on my Warthog throttle. But maybe that is better than having both condition levers bound on one axis, I am not sure yet because I am an unexperienced twin-prop pilot.

Waking up in the morning, seeing the email that an update is released for the Saab 340, looking outside the window, it is nice weather, thinking about what to do, have some hard decisions to choose, seeing that XP11 is not supported, choice went from hard to simple. Anyway, Great Job Goran_M!