Capt_Axel

Faulting application name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000 Faulting module name: FlightSimulator.exe, version: 1.38.2.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000001eaaf77 Faulting process id: 0x19870 Faulting application start time: 0x1DBC40D2267A571 Faulting application path: D:\AppsD\GamesD\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe Faulting module path: D:\AppsD\GamesD\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe Report Id: bc7cd745-18ff-4d44-85a0-5119d8d56afc Faulting package full name: Faulting package-relative application ID:

CTD on every flight, I cant even load into a flight session all.

Whenever I reinstall the 350 and when I delete the WASM folder, I notice that the addons remembers certain setting such as the last aircraft config used. Are settings stored in an extra place than community and WASM? for example I know ini manager automatically adds simbried and hippie data if you saved them to the app. I just want to make sure I do a clean removal of the A350 for testing.

After selecting the a350-1000 and starting a flight, the sim crashes during the loading screen. I reinstalled everything, deleted the WASM packages, restarted the PC and restarted the PC but no luck. Also in 1.0.0.9 simbrief imports wouldn't work on the a350-1000.

It's hit and miss for now. Even after loading in the sim I get met with a WASM crash within 30 minutes. Best to wait for 1.0.9, really annoying problem...

I have a solution, but first it looks like something is deeply wrong with inibuilds WASM code. Maybe it was the new 2504 AIRAC but something broke it. Now for the fix: 1) delete your wasm folder including the 'work' folder 2) uninstall the a350 from inimanager 3) install the a350 from the inimanager 4) when you load your flight after install, make sure you load on a runway (extremely important) FYI: on my next flight after this I and other people got a WASM crash so I shelved the a350 for now...

Same problem! I tried a specific A350 flight several times and each time there was a WASM crash as the plane was about to slow down for approach. Now, the plane doesn't even load in the sim even after emptying the WASM folder. Something broke and we are not the only ones. I use 2020.

Same problem

Shouldnt be this way. There is a justplanes full length video about Air Caraibes from TFFR to LFPO and they had 6.4T EFOB before push back with winds entered etc. They landed with pretty much that amount of Fuel. Why is it not working here?

The fuel calcs are messed up, really annoying for a long haul plane.