Xenon341

I just told you those date are only displayed for the navigraph AIRAC, even if you choose the sim default. You have the latest airac, disregard this date 🙂

I don't understand, if you choose Sim default, you have them. What make you say that you don't have the latest AIRAC ?

If I recall correctly, the date displayed in the FMC is the one of the default Navigraph database (AIRAC 2303 from 20th March 2023 to 19 April 2023), not the default sim one if you are using it. Microsoft deliver new AIRAC when they are out so you will benefit from them even if the date here is not the one you expect to see. https://forums.flightsimulator.com/t/airac-cycle-update-2506-msfs-2020-2024/725904/1

That's a WASM Crash. Please report it by following this guide. SU3 should help as Microsoft also fixed stuff internally.

Yeah that's a MSFS bug with Live Weather. You can switch to a preset weather then back to live weather and check if ISA temperatures are at normal level again

Guys, please, "same here" doesn't help 🙂 Post the necessary informations as required by the guide

Because you have to give the autosave and the OFP according to the guide and maybe the dev can detect similitude between the case. WASM crashes don't affect anyone that as simple as it is, why you got it, why I didn't, why ini test team didn't. As we don't know if a WASM crash is from the plane or from the sim, we report to ini. If it's a sim issue then ini will report to Asobo via the dev forum. Fenix is not on Xbox, A350 will be. WASM is required. So winning depend of who you talk to.

Hi, If you want them fixed, you need to provide the necessary inputs like described here, as WASM crashes are random and not easily reproduced. Thanks in advance !

Yes, Market place only as explained by Jorg on the FS Dev Stream.

Because gauges are handled by WASM and if they freeze that means the process has a problem. The process may have not crashed but it may became zombi. For the user it's the same consequence, instruments froze. There is a thread here if you want some reads : https://discord.com/channels/535246634448191499/1377432283966869644 As for PMDG, well, they are not imune to it, there are several case on their discord and even a dedicated topic on their forums. Let's hope that SU3 release will help with that for every developers that use WASM.

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.