Xenon341

Yes but there are WASM crashes that don't output logs, I had some that I've reported and we are not alone. Still reporting the same information can be useful for the dev team.

Hi there, Were you on the ground when you took the screenshot ? Is it the same when you are at high altitude ?

La correction doit venir de Microsoft à priori. Si c'est vraiment bloquant pour toi, il faudrait retourner sur la SU2 🙂 --- The fix should come from Microsoft. If it's a blocker for you I suggest rolling back to SU2 🙂

Hi there, Can you add some informations requested in those instruction ? That would help the team find the cause. Thanks !

Hi there, Are you using Navigraph ? Some people said that, as a temporary workaround, selecting sim default nav data stop the stutter. Is that your case too ?

It will be disableable when the HUD feature will be delivered in the next patch next week. A last minute bug forced them to disable the feature, but as the modeling was done they left it there.

Hi there, Are you on SU3beta ? If yes, it's known and is a SU Beta problem. If not, that's not normal indeed.

On the discord they said that they changed some files structure on the package that triggered the update.

There were some problems with the FS2020 liveries, are you on 2024 ? They just updated a bunch of liveries for 2020 some minutes ago, try to see if there are updates.

Auto derotation in 1.1.0 seems better from my point of view.

I’m flying air France F-HUVG right now it works. try to uninstall liveries and plane, clear wasm folder and try again ?

Are you using AIRACT 2605 rev2 ?If not, update navdata from EFB. Rev1 caused sim crashes.

Message from the ini discord :

Hi, Can you go to your controller settings and see if a key is bound to "SET PAUSE OFF" ? It's ESC by default but it may be use for another bind, try to bind it to a dedicated button and try to unpause again.

You can contact direct support through the ini manager, considering your problem it could be better.

And maybe try to uninstall via inimanger then start and close the sim then and install again, you clearly have a problem ^^

Yeah the WASM compilation failed. Try deleting the a350 folder inside the WASM folder and reload a flight. It should take a few minutes to compile and let you fly.

Yes turbulence to low is something to do, not only for ini aircraft btw. Time compression can cause problems but I'm not sure they are the cause in your case (or maybe it is if you had some turn to do and the plane couldn't process fast enough). Other probable cause : live weather bug in the temperature. If the ISA temps is at about +50°C it's not normal (it means 50°C hotter than normal and it affects engine performance, you lose speed as engine produce less thrust that they could do a normal temperature, AP disconnects, you fall), in that case, just switch to preset weather then back to live weather it should solve it

The plane couldn't climb to your desired altitude. 1) The plane entered "AP in prot" to protect the plane it took control back because a lack of speed probably (increasing AoA hence the A.Floor protection). 2) Why the plane couldn't fly higher ? Multiples causes. We would need the PERF page information to see what the plane had calculated. We would also need a. pciture of the flight deck to check what were your controls settings.

OP, check your rudder pedals, I guess you have a heavy left rudder going on.

Ok well sorry for that.

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