Xenon341

Hi there, What you can do : 1) Retract the spoilers 2) Put the thrust levers to CLB mode (2 detends prior the one you have currently) 3) Press (with right mouse click) the altitude knob to tell the plane to climb to 37000 feet

Hi there, Can you post details about the CTD (in windows event observer) ? That was a problem prior to SU2 on 2024, I had plenty of them with Navigraph but since SU2, absolutely no CTD with Navigraph. If you install via Navigraph Hub then use sim default in the EFB, you should have Navigraph data indeed but I don't know if it works well that way. Any way, any information you can give is important (crash dump, event message from windows observer etc.)

I copy paste to you the answer they gave on their Discord to another user with the same problem :

Check if you have left rudder inputs

I like the report I see, those of Der Michel are always interesting to read I learn a lot of stuff. But just to give some informations, there are multiples FCOM, multiples revisions of the avionics. There are also a lot of options company dependant (Like the BTV Autobrake off audio warning speed threshold). I have in mind the AIRCFT STATUS page that was indicated as wrong in those forums with picture as evidences. But the AIRCFT STATUS page in the ini version is also correct, just not the same avionics revision. I'm saying this just to underline that every bug report has to be verified. Ini may have missed stuff, but they also have their own sources for what they do. And qualify a report can take time, and once qualified, it needs to be prioritized, implemented, tested and released. All of that within an already filled planing as you can imagine. I still hope to find some fixes as you do, especially on the WASM crashes sides but this is also on Asobo side and some enhancement are planned for SU3 iirc. PS : I'm not an ini employee and have not any stock in the company.

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)