Jump to content

Recommended Posts

Posted

Inibuilds A350 Master WASM Crash Thread 1.2.1 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 1.2.1 will be removed from the post following the release of 1.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 - 

Posts not following this format are subject to deletion.

Thank you.

  • IniJamir changed the title to Inibuilds A350 Master WASM Crash Thread 1.2.1 FS2020
  • IniJamir pinned this topic
  • 2 weeks later...
Posted
  • Aircraft: A350-900
  • Simulator: FS2020
  • Version: 1.2.1. - Marketplace
  • Navdata Method:NAVIGRAPH
  • WASM Error: WASM: Exception c000001d in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm
  • Specs: Intel i5 11400F (Rocket Lake), GeForce RTX 3060Ti, 32GB RAM, 4TB SSD
  • Screenshot/Video: I dont have a video, but I remember, what i did approx. First time that happened was yesterday. I was preparing a long-haul flight from LSZH to MMUN. I started to inserting ETOPS waypoints to the backup NFD on the FO side. I pasted aprox. 2 waypoints and scrooling thru a lat. and long. and that happend just a freeze of displays, numbers, but knobs animations was fine. Then i restarted flight, loaded autosave and everything was fine, until I tookoff, climbed to approx 11 000ft and then a just scrolled the altitude know to set it to FL240. Than it happened, scrolling stoped and displays frozed, but knobs responds, for example EFIS CNSTR light and pushbutton with light responds, SPD BRK extension lever animated...just all displays like MFDU, PFD, NFD etc. freezed. 
    Today it happened again. At the morning I tried to delete everyting connecting with "inibuilds a350-airliner", like in WASM, community folder, liveries etc. Like a fresh install. Then i gone to A/C and started preparing the flight from LZSH to GCLP (attachment file) and I just wanted to move a QNH knob to set the AD elevation and happened the same again. I was not experiencing somenting like that for example on the version 1.2.0. Long-haul flight to USA was normal. 

    I just dont understand, that I updated to 1.2.1., flown a entire day aporx. 2 flights from LSZH to LKPR and back and nothing like that happened. I did not changed anyting. No more liveries installation, just turned off PC at the evening and turned on at the morning and that day was sucked.

    I would like to thank you for your time reading this and I know its very difficult to experiance lots of the problems of all users.

    You understand. I red, that you experienced this too during your flight so you know, that I DONT WANT to switch to another airplane, cause untile know everting went fine.

    Regards,

    Mathias  

LSZHGCLP_PDF_1770813591.pdf 1770818477.bin

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...