Xenon341

Also had one yesterday on 1.0.12 (reported on their Discord) without any error. Load the autosave after a sim restart and could complete the flight. I hope MS can enhance the log/debug tools for the dev to investigate those crashes.

That signs of bad WASM compilation. Delete the WASM folder and try to load the plane again.

Hi there, Furstrating indeed.. You can reload an autosave to finish the flight if you want. Concernant the WASM logs, they are lost when you close the sim. Otherwise, here are the instructions :

And don't forget to post the WASM logs as asked by ini in case of WASM crashes.

Can you report the crash as instructed here please ?

I can confirm too for the brake problem.

You just encountered the AP disconnect protection. Your sim is in pause. Bind a key to "PAUSE OFF" in MSFS settings and you can unpause. What has been raised to inibuild is that if it's a user initiated action, AP disconnect protection should not kickin (and if it kicks in, a message on the EFB should appear).

For CoherentGTUI.dll CTD, try to use SIM DEFAULT nav data instead of Navigraph (in your EFB, option menu, 3rd party). You still can use ANF to choose BTV exit. You are not alone, big thread on Discord : https://discord.com/channels/535246634448191499/1364323792507240451

That is very interesting. On Discord, according to multiples users, CoherentGTUI.dll seems to be solved with a Nav data change (revert to sim default) but WTF.dll had no lead. The livery lead might be promising ! For thoses with WTF.dll crash, did you tried to uninstall and re install the liveries ?

Did you tried what is suggested in this thread by ini ?

If you are using Navigraph as your nav data source, for the CTD related to CoherentGTUI.dll you can try to switch your Nav Data source to "Sim default". Many users reported that it fixes the CTD (but obviously this is still problem ini should fix no to be able to use navigraph)