Litjan

That is correct. Unfortunately all waypoints that begin with "N" or "S" and end with "E" and "W" are going to cause this... unfortunate fallout from the "user created waypoint" addition. It will be fixed very soon. Workaround for now: Either avoid manually entering these points (automatically loading them in a STAR or SID is no problem), or make a route (without them), save it, then edit the .fpl (in coroutes folder) with a simple text editor to include them. Then you can load them via the "company route" function. Cheers, Jan

I downloaded your Log.txt and you are still running all those plugins. Here is the relevant section from your Log.txt: Fetching plugins for C:\X-Plane 11/Resources/plugins Loaded: C:\X-Plane 11/Resources/plugins/PluginAdmin/64/win.xpl (xpsdk.examples.pluginadmin). Loaded: C:\X-Plane 11/Resources/plugins/NavigraphSimlink_64.xpl (Navigraph Simlink for X-Plane). Loaded: C:\X-Plane 11/Resources/plugins/ASXPConnect/64/win.xpl (HiFi). Loaded: C:\X-Plane 11/Resources/plugins/AVS/64/win.xpl (ru.ffsts.airportvs). JARDesign 3D Sound Engine v310320 Loaded: C:\X-Plane 11/Resources/plugins/BSS/win.xpl (jardesign.sound3d). 2020-06-10 19:04:23 BetterPushback[xplane.c:539]: This is BetterPushback-v0.48 libacfutils-0e818a4 Loaded: C:\X-Plane 11/Resources/plugins/BetterPushback/64/win.xpl (skiselkov.BetterPushback). Loaded: C:\X-Plane 11/Resources/plugins/CEF/64/win.xpl (FlightFactor.CefLoader). FlyWithLua: Your system path is C:\X-Plane 11/ FlyWithLua: System Dir: C:\X-Plane 11/ FlyWithLua: Plugin Dir: C:\X-Plane 11/Resources/plugins/FlyWithLua FlyWithLua: Plugin Scripts Dir: C:\X-Plane 11/Resources/plugins/FlyWithLua/Scripts FlyWithLua: Plugin Internals Dir: C:\X-Plane 11/Resources/plugins/FlyWithLua/Internals/ FlyWithLua: Plugin Modules Dir: C:\X-Plane 11/Resources/plugins/FlyWithLua/Modules/ FlyWithLua: Plugin Scripts Quarantine Dir: C:\X-Plane 11/Resources/plugins/FlyWithLua/Scripts (Quarantine)/ FlyWithLua: Plugin Version: 2.7.22 build Dec 9 2019 14:41:43 Loaded: C:\X-Plane 11/Resources/plugins/FlyWithLua/64/win.xpl (CarstenLynker.FlyWithLua.NG). G64: 0.000: Gizmo64 Script Engine v18.02.27.0200 Windows G64: 0.000: built: Feb 27 2018, 02:00:08 Loaded: C:\X-Plane 11/Resources/plugins/Gizmo64.plugin/64/win.xpl (gizmo.x-plugins.com). [REALVIEW INFO]: Starting X-Plane SASL plugin v3.2.7+0b9658f [Commercial Edition] [REALVIEW INFO]: RealView | Global | Start Full Loaded: C:\X-Plane 11/Resources/plugins/RealView/64/win.xpl (1-sim RealView). Loaded: C:\X-Plane 11/Resources/plugins/SilverLining/64/win.xpl (SilverLiningV4.Clouds). [SKUNKCRAFTS UPDATER INFO]: Starting X-Plane SASL plugin v3.6.5+8783e05 [Commercial Edition] [SKUNKCRAFTS UPDATER INFO]: SkunkCrafts Updater | Global | Start Full [SKUNKCRAFTS UPDATER INFO]: Loading cursors... Loaded: C:\X-Plane 11/Resources/plugins/SkunkCraftsUpdater/64/win.xpl (1-sim SkunkCrafts Updater). TGXP: Traffic Global V1.0.9113 TGXP: Unable to identify DataRef sim/graphics/view/using_modern_driver TGXP: 19 TCAS (multiplayer) aircraft enabled. TGXP: Scenery path 'C:\X-Plane 11/Custom Scenery/MisterX_Library/Earth nav data/apt.dat' doesn't exist, skipping. Loaded: C:\X-Plane 11/Resources/plugins/Traffic Global/win_x64/Traffic Global.xpl (jkcc.trafficglobal). WebFMC: Plugin version 1.5.3 WebFMC: WebFMC Pro starting up WebFMC: Expecting backend binary in "C:\X-Plane 11/Resources\plugins\WebFMC\webfmc-win.bin" TGXP: Scenery path 'C:\X-Plane 11/Custom Scenery/HD Forests/Earth nav data/apt.dat' doesn't exist, skipping. WebFMC: IO Thread run WebFMC: WebFMC started Loaded: C:\X-Plane 11/Resources/plugins/WebFMC/win_x64/WebFMC.xpl (com.greenarcstudios.webfmc). TGXP: Scenery path 'C:\X-Plane 11/Custom Scenery/Airport Environment HD/Earth nav data/apt.dat' doesn't exist, skipping. TGXP: Scenery path 'E:\Custom Scenery\yOrtho4XP_Overlays/Earth nav data/apt.dat' doesn't exist, skipping. WebFMC: Server version 1.5.3 TGXP: Scenery path 'E:\Custom Scenery\Ortho_Washington_2017/Earth nav data/apt.dat' doesn't exist, skipping. TGXP: Scenery path 'E:\Custom Scenery\z_ortho_New_England/Earth nav data/apt.dat' doesn't exist, skipping. WebFMC: WebFMC network address(es): 192.168.1.15:9090 TGXP: Scenery path 'E:\Custom Scenery\z_ortho_MidAtlantic/Earth nav data/apt.dat' doesn't exist, skipping. TGXP: Scenery path 'E:\Custom Scenery\z_ortho_California_v5/Earth nav data/apt.dat' doesn't exist, skipping. TGXP: Scenery path 'E:\Custom Scenery\Hawaii/Earth nav data/apt.dat' doesn't exist, skipping. TGXP: Scenery path 'E:\Custom Scenery\Ortho_Oregon_2017/Earth nav data/apt.dat' doesn't exist, skipping. Loaded: C:\X-Plane 11/Resources/plugins/XSaitekProFlight/64/win.xpl (XPlane Plugin.1.2.6.0). [RealityXP.GTN][INFO ] [RealityXP.GTN][- ] # win.xpl version 2.5.25.0 Loaded: C:\X-Plane 11/Resources/plugins/rxpGTN/64/win.xpl (RealityXP.GTN). [XJet] Init properties. [XJet] Plugin path: C:\X-Plane 11\Resources\plugins\xjet [XJet] Props path:C:\X-Plane 11\Resources\plugins\xjet\jvmplugin.properties [XJet] Init JVM. [XJet] Plugin path: C:\X-Plane 11\Resources\plugins\xjet [XJet] Plugin started. Loaded: C:\X-Plane 11/Resources/plugins/xjet/64/win.xpl (com.airfoillabs.xjet). "Iffy" means "it is unsure IF they will run well with the IXEG737" - they are all great plugins and such, but people have reported compatibility problems before and often there are updates for those plugins that fix those - or the plugins are very old and made at a time when certain coding conventions were more "lax" and did not cause conflicts. So - if "unticking" the plugins in the disable menu doesn´t (seem) to work for you, you need to manually clear them out of your plugin folder (just move them somewhere else for now). Then run the 737 and see if it runs stable. If it does, move your plugins back into the plugin folder one by one. As soon as the 737 starts CTD again, remove the last plugin you added, start adding the remaining ones one by one. Once you have all plugins loaded that will let the 737 run with CTD please report which plugin is not compatible and we will see if we can do something about that. Cheers, Jan

Yep, it is noted and we will see how we can implement it. In the regular 3D cockpit we move the viewpoint (pilots head) slightly - obviously that doesn´t work in VR, so we need to figure out some other method. For now get your wife to shake your chair slightly when rolling down the runway . Cheers, Jan

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