Litjan

Hi Torbinator, I have seen the same (and stranger!) things with VNAV in descent. But I am pleased to report that Tom has implemented some coding changes related to STARs and it´s transitions (as posted above) that also seem to have a very positive effect on VNAV. I have done a few flights with VNAV descents, and I still see some quirky behaviour (mostly not adhering to the first of multiple AT restrictions), but overall the VNAV has become more predictable and more reliable and I am sure we can build on that and improve it further. I am curious what you guys will report when flying the next (1.32) patch. Cheers, Jan

You have quite a few "iffy" plugins running. Silver Lining, Xjet, ASXPConnect, etc. Disable all of your other plugins (just to test) and then see if it still crashes. Then add them back to see which one is the problem. Cheers, Jan

Not sure about the shaking - I think that needs careful consideration in VR - especially with inducing nausea etc. I recommend setting the response curve for the joystick to "linear" without any intermediate points. Cheers, Jan

Disable SkyMaxpro, Traffic Global and XPUIPC and try again. https://forums.x-pilot.com/forums/topic/17953-had-3-crashes-so-far-v13/?tab=comments#comment-150615 Also maybe try to update to the latest Gizmo beta (or revert to the stable V18.xx one) - found here: https://forums.x-pilot.com/forums/topic/18008-standard-troubleshooting-and-reporting-protocol/ Also note this: Jan

Quite a few "critical" plugins running on your installation (XPUIPC, etc.) - I would suggest disabling them to try if that helps, then add them back until you find the problematic one. Jan

Those are good choices - but I would recommend this: https://www.utem.com/shop/index.php?l=product_detail&p=5 There is also a colour version (more expensive!). Cheers, Jan

I count 16. Of which probably 5 can be considered "likely to cause trouble". Jan

Thank you so much for going through with this testing. You are right - sometimes computers are beyond comprehension. The complexity of X-Plane and the plugin ecosystem is very high! Please let us know if you find any additional info why this conflict exists! Cheers, Jan

It could be that the downwash model changes bites one aircraft harder than the other - depending on the wing-tail geometry...

Hi Kamaku, you have an extreme amount of plugins running - some of which even "sound" obtrusive. I bet if you remove all of them and then try - it will work. Afterwards you can move them back in (in batches) until things stop working. This will help you isolate the problem and we can try to find out what is not working with the combination. Cheers, Jan

The flightmodel is always a moving target with X-Plane . We try to stay on top of that, though - and thats why the "experimental flight model" is what we tune for. In the (near) future this experimental flight model will become the "normal flight model" - then all you guys have to do is UNTICK that box. If we waited with the tuning until they make that change it would still take us a day or two to release a patch and everyone would need to download and install and whatnot. I expect no sweeping changes to the modeling in the future - the flightmodel is moving towards "reality" in an asymptotic way, so any futher changes are bound to be even smaller than this one. And the difference between "standard" and "experimental" right now is so small that most pilots won´t even notice. Cheers, Jan

Ok, weird in that it would affect the switches? It really shouldnt... Computers continue to amaze me. I am running the plane in 11.50b9 and it works nicely (apart from the occasional "lost Vulkan device" crash). Cheers, Jan

If you had read your log.txt (yes, not only devs can do this, even the mere mortal user can) - you would have found this: E/GFX/VK: Vulkan device lost error! 0:00:06.446 E/GFX: No diagnostics for graphics queue, queue was empty! 0:00:06.446 E/GFX: No diagnostics for transfer queue, queue was empty! 0:00:06.446 E/SYS: MACIBM_alert: Encountered Vulkan device loss error! 0:00:06.446 E/SYS: MACIBM_alert: X-Plane cannot continue running and will now quit. So, there are two things problematic with your setup: 1.) You are running some plugins that can cause problems (new XPUIPC is not compatible, older version is), FlyWithLua (depending on the scripts) 2.) You are running the latest Beta of X-Plane and suffer a device loss error...which has nothing to do with IXEG. Cheers, Jan

I can not find any gizmo errors in your log. I can find two other plugins reporting problems, though. I suggest you follow this: Cheers, Jan

Grab and hold (with mouse) the switches to move them? Possibly other plugins (external hardware) in control of those datarefs? Jan

No - but anything messing with art datarefs can be (silver lining) and anything messing with other datarefs (fly with lua, xpuipc, ground traffic, etc) can be as well. So its impossible to say which ones are critical in combination with the IXEG, most of the time the user finds out and then often there is an updated version (because who keeps checking his plugins for updates all the time?) Cheers, Jan

Hmm, it could be that your external hardware is somehow interfering with our accessing the datarefs or something..

Sorry, I am afraid there isn´t. The preference file was changed (because we added more options) so the old version could not be retained. This may be different for future updates, though. Cheers, Jan

Hi Sean, thanks for the log files. You are running a dozen or so plugins that have caused compatibility problems in the past. To troubleshoot and find the offending one, please remove them, test, add back (in bunches) until you find the one that is causing it. Often there is an updated version for that plugin - sometimes (XPUIPC) only an older version works. Cheers, Jan

I have a keyboard macro to paste this link :

Hi Sean, it is likely that you have other plugins running that compete with lua for memory - which is really limited to a small amount of your total memory. The only short-term cure is to remove other plugins that use lua. The long-term solution will be to move our sounds to FMOD...which will take a few months of dedicated work (according to the estimate of Laminar Research´s designer that did the sounds for the 737NG and MD80). Cheers, Jan

Hmm...that sounds like some sort of "initialization issue". To narrow down - can you spawn the plane in the "non working" (turn-around?) condition...and then confirm the ILS is not receiving...then click the "reboot gizmo" (little flash sign) on the RIGHT side pop-out menu? This initializes the scripts again. Another thing I would like you to try is to disable "Global traffic", just to test. Not sure, but it could influence this somehow (you know, computers...) Thanks, Jan

Yes, it works normally with beta 9. To use those things you need to click on them to "hold" them, then drag the mouse in the direction you want to switch. Cheers, Jan