All Activity

So this is kind of a two part report. Its a reoccurring issue with the OANS giving errors saying "ARPT NAV NOT AVAIL". I have tried clearing WASM folder, removing navigraph.txt, reinstall and nothing seems to prevent this error. It always seems to pop up after a flight with it working perfectly fine. A workaround I have been told and which prompted this report was to reset the navigraph credentials in the EFB and sign in again, which worked the flight before. This time it WASM crashed the plane. This is an issue that needs to be addressed. Aircraft: A350-1000 Simulator: FS2024 Navdata Method: NAVIGRAPH AIRAC 2601 OFP: N/A WASM Error: WASM: Error during EFIS_gauge_update execution. Error code : 0xc0000005 Specs: i9-12900K, RTX 4070ti SUPER, 64gb DDR4 RAM Autosave File: N/A - I dont use autosave

Anyway I managed to carry out my flight from RKSI to KDTW and got myself to cruise level. When I returned after 6 hrs of sleep I found this: I have so many questions but I dont know where to begin investigating lol BTW, there is no wasm as all buttons are clickable nothing seems frozen.

Hello Jamir, Please find attached requested screenshots.

Did you move from 2020 to 2024? It may have installed in the old 2020 folders.

Good Day, first screen freeware scenery flightsimto, second screen freeware inibuilds scenery, third screen volanta on left side inibuilds and right side flightsimto, here real charts Layout1 (2) WFANG Best Regards

ok I think I seem to figure out the culprit. After each clean install or before starting up sim I would delete wasm folders. This time I kept wasm files and folders and the problem seems to have resolved.

As the title says. Where I have the Community Folder has the aircraft in there but it doesn't show up in my aircraft menu in game nor does it show up in My Library \ Community. Is there a "shadow" community folder somewhere where this file needs to be? Very confused.

Hi I have tried multiple clean reinstalls and tried different liviries but I am getting the same weird cockpit screen displays. I am using MSFS 2024 Delta livery. Custom cabins are uninstalled. Using default cabin. BTW earlier I had custom cabins installed and that had my cockpit missing altogether. I am not sure if the custom cabins have messed up some hidden files that I am unaware of. The version in use is v1.2.0 If anyone can help I would really appreciate it. Thank you

I've attempted in disabling the KLAX v1.0.1 POIs and the results did not change. Also running the latest 2024 version of Vol 1 v1.5.0 (as well as Volumes 2.3 and 4).

Hello Capt James, ENSB Svalbard is also a hand-crafted scenery that is include with World Update V: Nordics. I know you said that you double checked the scenery database but I just want to verify that you "Disabled" the scenery in the My Library section. If you have done this already then could attach media of the dual vaults in sim as well as your content library showing ENSB from WU5 as disabled in the content manager, thank you.

Hi, I am currently loaded into KLAX Enhanced Edition with the POIs disabled in the IniManager whilst having the SamScene3D Vol.1 currently loaded and I am not getting a sandlot or the hybrid merge of the two SoFI Stadiums if you leave the POIs enabled. Did you check to make sure you are using an updated version of SS3D Vol.1 for FS2024 and not the original FS2020 version; as well as ensuring you are on an up to date version of KLAX Enhanced? I did not have to change any scenery load order in order to get the SS3D SoFI Stadium in, just disabled the POIs and everything worked as displayed below.

Hi, I looked into this issue with DTW in FS2024 and I was able to adjust the snow it is maximum density potentials in the weather tab and I was able to find that snow does accumulate on the runways and other hard surfaces do accumulate snow as seen below in the attached images. However as you did point out the grass areas and certain- -roads do remain without snow and this does come down to an established sim limitation in the thread below regarding LOWI and it's snow coverage:

No matter what flight I do, even 4 hours, to 14 hours the screens will freeze causing the airplane to loop when I'm sleeping, after 2 good flights which I did 3 months ago KATL-FACT, and KORD-EKCH, my A350 no matter what I do such as clearing wasm folders, reinstalling, emptying community folders, the A350 will now freeze my insturment screens and cause a loop, I load the autosave IF it happens close to when I wake up. doesn't happen on the A340s though... Can this be fixed? it's ridiculous... A lot of people have this issue either fix it or refund.

Hi, I loaded up PHNL v1.2.2 and was able to confirm that the C and G Terminals are indeed suffering from an interesting lighting issue, I will raise this to the team, thank you!

Hello, regarding the bumpy runway; this has been reported to be the case as in real life and as such is a feature by design as the airport itself is inherently challenging to land on from being an all-ice runway to extreme wind conditions. See this thread here: As for the the airport being offset to the west, are you using the coordinates provided in this thread here: if not, it may be worth trying again with this information above; if you are using this information than would it be possible to gather media (preferably recordings or screenshots) with current versions of the scenery and Nav Data and upload them in this thread that way I can present it to the team? Thank you.

Hi All, Since installing ENSB I can see 2 x seed vaults on Longyearbyen. I've double checked the scenery database and I can't see anything amiss. Is/ has anybody else experienced this?

Good Day, i install scenery at98 via IniMager, first bug bumpy runway not possible land i try delete scenery index, second issue airport look like offset to the west from navigraph nav date Best Regards Thank you 🙂

Enabling Developer Mode and changing the Scenery load order is probably going to be the solution. I remember having trouble with FlyTampa's LAS scenery conflicting with Navigraph and had to change the load order to solve it.

Any word on a workaround from the devs? Would really help out folks that use the a400 in some of the 3rd party career apps utilize the full payload capacity

Any updates @iniSteven?

That is most likely due to the planned approach. Then you are using outdated navdata from 2023.

Inibuilds A350 Master WASM Crash Thread v1.2.0 FS2020 This thread will be the new location for all WASM Crashes relating to the Inibuilds A350-900/1000 for Microsoft Flight Simulator 2020 Below this message will be where users can upload their WASM Crashes pertaining to the current version of the A350. NOTES: If you do not see orange expectations screens on your displays or "WASM exception in X gauge" in the developer console it is not a WASM crash. The "sim-freeze" is a separate event that is tied to something on the server side which we are investigating with Asobo. All WASM Crashes existing in this thread will be removed following the release of a new update. i.e. Any Crashes identified in Inibuilds A350 v1.2.0 will be removed from the post following the release of v1.x.x and so forth. Please ensure that when posting WASM crashes you post the WASM log from the in-game console alongside any media (photo/video) and a brief description of what you were doing leading up to the crash. Instructions on what to do are located in this thread - Thank you

Hi. It sounds like your ng token is not refreshing. Can you try logging out and in from the OIS and then seeing if it downloads the correct dataset?

Hi Luke. This isn't what we need actually. Please follow the steps outlined here if you encounter another crash (orange screens) and we can take a look - Thanks!

Hi, are you able to provide any real world media corresponding to the ramp areas that are visible in this screenshot from the simulator? If you can provide real world visual representation of the area provided whether it be videos that clearly display the gates in question as well as the bridges, I will be more than happy to pass this along to the developers, thank you.