Xenon341

Alright, odd indeed, ping Eddie on Tuesday if you don't have news from him.

Hello, Did you try to restart the flight with the "restart" option in the pause menu ?

Are you on SU3 Beta ?

If you are on a 7900XTX (just like me), I recommend the 24.12 driver, old but good 🙂 TAA + FSR3 for framegen and it works great (modulo some artifact on some plane like fan blades on PMDG 777)

If your instrument froze and the plane continued to fly, that probably a WASM crash. Can you report the problem as described in the following guide ? That's the only way the team can investigate your crash, as it doesn't happen to everyone. Thanks !

Hi there, Are you on SU3 Beta by any chances ? If yes, it's known. There is a workaround while waiting for SU3 release but it can have some unexpected effects : Open the file <Your_flightsim_install_dir>\Community\inibuilds-aircraft-a350\SimObjects\Airplanes\A350\common\model Changing "withExterior_showInterior_hideFirstLod=true" in Model.cfg to "false" Keep in mind that this will be undone a each plane release.

Hello EKBI, I had this problem myself on release day, you can try 2 things : 1) Use the alternate downloader in inimanager (go to the settings of iniManager) 2) Use a VPN ou use your mobile hostpot and try to download gain Let us know if that works for you 🙂

Hello Dougal, Sorry to hear that 😕 If you encounter this kind of crash agin, yes it's important to gather the maximum amount of info to let the ini team investigate. Please check this guide that explain how to report them. Thanks you !

Dot on managed seems to be MSN dependent, not every 350 has them (see the videod below, those 2 exemples don't have the dot on managed alt/speed/heading).

D-ATIS works, at least for the flight I did with LFPG ATIS (just hoppie). Didn't test the CPDLC though.

Ini said the flight model will not be changed and it's up to the user to apply the settings they want within controller setting and adjust the curve. (see ) To be honest, since 1.1.0 I like of the plane feels, 2 versions before that they adjusted something that induces an unpleasant dead zone and fixed it in 1.1.0. So, you see, it's very subjective.

From the changelog : Bugs & Feedback Addressed We’ve received feedback from VR users about MFDs not being clickable. The issue appears to be related to how mouse interaction checks occur per screen, which sometimes fails in VR frame updates. Investigation is ongoing, we hear you and are working on a fix.

Hi @dectenor1, people reprted on discord that clearing the wasm folder solved the issue for them (they had to do it twice for some).

Realistically you don't know. Camera angle has been notified in the Discord yesterday night with ini staff and they were surprised by it, they didn't want to ship the HUD and have the camera looking at the wrong angle, they did some adjustement in preparation for HUD integration but obviously, camera positioning is a problem in the current release, I have it too. I'm pretty sure they will come with a fix for it, wait and see.

It doesn't indeed but I didn't had to use the autosave feature a lot. Sorry this heppens to you. Can you upload a save where you encounter the problem ? You can see in the guide below how to extract it :

Hi there, Can you try to load the save twice ? Some variable might be not correctly initialized the first time so loading a 2nd time few seconds later can help. Regards,

You will have an option to disabled it when the feature will be complete in the next update 🙂

It seems to be 9070XT specific issue or at least Driver Handling of the 9070XT, not the plane nor the brand (other AMD card are fine). The issue seems to be in Indiana jones too. In the FS Forum thread, there is an AMD thread link, I suggest you to contribute there if not already done. The good news is some AMD staff is in there and raised the topic internally on June 3rd

Do you have a custom scenery for Singapore ? DO you have the same problem on another default airport ?

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