A350 crash after update

[David Cherrie]

2 hours ago, tesla said:

It turns out that it's not just me who can't fly long distances after updating 1.0.8,The error code is consistent with yours one by one 0X8000003.I have no issues with the previous version, and I have not made any changes to my computer or simulation settings.If you're nlucky, start the englucky, you can fly for 6 hours. If you're uine and then exit to the desktop。

You just have to look at the Cross the Pond data and the amount of people who started their flights in the A359/A35K did not complete their flights.

[Prabin]

My simulator is also crashing to desktop intermittently from intro screen. Based on 

https://forums.flightsimulator.com/t/fs-2024-new-install-keeps-ctd/714476

I turned hardware acceleration to off in windows. I did a 4.5 hour flight from SCEL to SCIP with no issues. Maybe it is an issue with the sim itself? Can the readers check the settings and try this out?

 

Thanks.

[Stefan64]

A350 CTD. Happens with version 1.08 even without SU2. Stable version has the same problem. Very bad.
CTD after approx. 15 minutes flight. 
i9 RTX 4090 64GB Ram.

[tjockklat]

msfs 24 SU2. 10 min after takeoff started lagging like crazy. Didnt ctd, but felt like a slideshow. Has never happened in the fenix with like 200 flights. Always stable and high fps on the fenix.

Edited April 30 by tjockklat

[Stefan64]

A350. A complete reinstallation helped me. Uninstalled via Ini Manager. Deleted all A350 folders, including WASM A350, as described in the video above. ILS flight Nice - Zurich was successful. Steam Stable Version, i9 64GB RAM RTX 4090

[Stefan64]

Hello Ini team. CTD again after 15 minutes of flight. Very annoying and incomprehensible. Reinstalling didn't help. Please find a quick solution!

[LukeSkyBellic]

Have you had any improvements since the release of 1.0.9?

Edited May 10 by LukeSkyBellic

[Prabin]

No. First flight crashed after 2.5 hours. 😞

[Prabin]

For the first time I completely uninstalled FS2024 and addons. Then I reinstalled Inibuilds A350 along with the other well known Boeing product. I did a flight of 7 hours duration with no issues on both of them. I hope this is a good sign.

 

 

[macbrush]

Have you ever found a solution? I haven't flew A350 for awhile, and met with exactly the same issue when I need it for my virtual airline. The only thing I can think of is that I have recently updated my Windows 11 from 23H2 to 24H2, and there was an accumulative update for 24H2 last week as well, otherwise I cannot think of anything else. I've uninstalled everything A350 including the WASM folder to no avail. I gave up and am flying a A380 as sub now.

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: 0x80000003
Fault offset: 0x0000000001f0ffe2
Faulting process id: 0x74EC
Faulting application start time: 0x1DBE2E626AFA674
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 17a6d98c-4cf5-4df6-8664-5dd93840377c
Faulting package full name: Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Edited June 21 by macbrush

[macbrush]

Okay, I found a solution to my problem. The problem is that something in the community folder is preventing A350 from compiling after update. So I moved everything except A350 from the community folder to somewhere else, load up both A350 900/1000 in some airport, i.e. successfully compiled, then put everything back into the community folder. Everything is working fine now. I couldn't be bothered to find out which addon is conflicting, since i have over 20GB of them, but if I ever found it, I'll post here and let you know.