Hi all.

Is anybody else having instant CTD's with the A320NX (Dev) . It worked fine until 3 days ago, but since then whenever i click fly it CTD's. I have deleted the aircraft, cleared the other fbw A320nx  files (Not folders) left behind after being deleted. Even tried the stable version, doing a clean install after.

I use the addon Linker and have only the FBW A320NX in Community folder, still the same. The default A320 loads fine. I even re-installed MSFS yesterday in an attempt to rectifiy the issue, and it's still the same. ( I am not using anything other than default liveries, and default airfields to prove the issue is either with the A320NX or something has changed in sim thats causing the problem.

 

Any help appreciated.

 

I had also those crashes while loading an airport with A32NX.
The only option that worked ( at least on my setup):
After SU5 when you enter on MSFS world map and have a different aircraft and change to A32NX i had ctd when loading an airport.
the only way to avoid those crashes was to have A32X as my main Aircraft when MSFS is loaded.
weird issue....

After 5 CTD's and a lot of perseverance, I managed a 3hr flight in the FBW32NX, which went beautifully. I'm using the latest Dev version. I'm pretty sure the CTD were caused by the annoying UPD5 Sim update, which hopefully will end after hotfix 2 due the weekend.

I get around it by deleting the "state.cfg" for the FBW A320. This file contains Hobbs Meter information. It rebuilds itself.

Deleting this file before I open MSFS allows me to select and fly the FBW A320 without a CTD. Not deleting the file will guarantee me a CTD on first startup.

Mine (MS Store Version) is found at..............

C:\Users\your_username\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SimObjects\FlyByWire_A320_NEO\state.cfg

CTD on load for me. 

Apart from having the FBW as default aircraft on startup, turning on the developer mode before loading the flight helped with the CTDs for me. Can be turned off again after the flight is fully loaded.

Yes as above I also had a CTD when I tried to start a flight after changing to the FBW from another aircraft. When I started again with the FBW already in the hangar it loaded fine and I was able to complete a 2 hour flight without incident (well.. apart from the temperature fluctuations at altitude).

Three things to try:

1) When you get to the "Ready to Fly" screen, let the aircraft load completely (let all the views cycle through) before you hit the button.

2) Try from a default MSFS airport. I found a fair few of my CTDs were actually airport/scenery related - but as I had the A32NX selected, I put it down the that.

3) It appears sometimes that if you change *to* the A320 from another aircraft in the same session, the A320 might crash. Restarting the sim with the A320 loaded/saved in the menu from the previous session might help.

Having had a few MEGA Linker sessions to isolate the incompatible addons, I now (finally!!) appear to have a stable MSFS - and the FBW A320 seems to be working really well (touch wood!!).

Edited August 6, 20214 yr by Adamski_NZ

Great info many thanks all.  @Seth2021 Spot on, it now loads fine, many thanks. I'll look into that as well  @michaelray

 

Cheer's guys

16 minutes ago, RALF9636 said:

Apart from having the FBW as default aircraft on startup, turning on the developer mode before loading the flight helped with the CTDs for me. Can be turned off again after the flight is fully loaded.

Well blow me down. I turned on Dev mode and it loaded. Default airport though. Now to see if it'll last a flight.

Join the many...........😟. I can load once in a blue moon.

For me it's 50:50. I can load it at some airports. But for example LFPG gate V4, constant ctd, when I click Fly button. Can someone try load it at that gate?

Edited August 6, 20214 yr by xenonsk

I too used to struggle getting a flight started after SU5. It would generally crash just after the airport and the FBW were loaded. I tried everything, Turning the online connection, AI and live weather off and setting the graphics to low-end would sometimes work. But what worked one day, could easily lead to a CTD the next.

Then, fed up with it, I playfully decided to set my graphics to high-end ( my pc is 5 years old so no way it qualifies for that and I have a Nvidia 96x card) and  extend the rolling cache from 8 to 16. 8 was set automaitcally when I installed the game.

Not sure of course which really helped but now I have had 4 working starts in a row. No more issues so far so maybe it helps any of you.

 

 

I'm suffering from the same problems. I can load a flight and the cinematic previews show up. But once I hit the button to enter the cockpit, it instantly crashes. I managed to get into the cockpit a couple of times when starting the flight on the runway, but not at the gate in cold-and-dark. I also tried various things to no avail. MSFS is just completely bugged at the moment.

Edited August 6, 20214 yr by carlito777

14 minutes ago, carlito777 said:

I'm suffering from the same problems. I can load a flight and the cinematic previews show up. But once I hit the button to enter the cockpit, it instantly crashes. I managed to get into the cockpit a couple of times when starting the flight on the runway, but not at the gate in cold-and-dark. I also tried various things to no avail. MSFS is just completely bugged at the moment.

Have you tried the dev mode workaround mentioned above? Try loading a flight with dev mode enabled.

Edited August 6, 20214 yr by jarmstro