Loading the A310 leads to CTD

reloaded the sim and A310 and it worked this time. this is what the log.txt looks like when it loads

[iniBuilds-A310] Info: Logging initialized
[iniBuilds-A310] Info: LVar init completed
[iniBuilds-A310] Info: Registered update loop with interval of: 33ms
[iniBuilds-A310] Info: Registered update loop with interval of: 33ms
[iniBuilds-A310] Info: Registered update loop with interval of: 33ms
[iniBuilds-A310] Info: Starting Clock system
[iniBuilds-A310] Info: WASM: failed to read throttle configuration from disk → create and use default
[iniBuilds-A310] Info: WASM: failed to read throttle configuration from disk → create and use default
[iniBuilds-A310] Info: Simconnect connecting…
[iniBuilds-A310] Info: Simconnect connected
[iniBuilds-A310] Info: Registered update loop with interval of: 15ms
[iniBuilds-A310] Info: WASM: failed to read options configuration from disk → create and use default
[iniBuilds-A310] Info: Simconnect disconnecting…
[iniBuilds-A310] Info: Simconnect disconnected
[iniBuilds-A310] Info: Shutting down CLOCK system
[iniBuilds-A310] Info: LVar de-init completed
[iniBuilds-A310] Info: iniBuilds A310 is saying bye bye

I have exactly the same problem. I not running last beta, just trying fly A310 today, I just press FLY and boooooooooom CTD. Reinstalled, not helped.

I done reinstallation via Marketplace and in the end of installation had info that I using DirectX12 and it’s in beta and causing problems (?) and back to DirectX11 will resolved problem… So what I done is: uninstalled again, back to direct11, installed again via Marketplace. But this time I just installed clean A310 without enhanced mod - and A310 works. Tried with enhanced mod also-works. I back to DirectX 12 - CTD. I have RTX4090 and i9-13900K, using DirectX 12 with Frame Generation ON. It’s A310 not compatible with DirectX 12?

I use the A310 with DX12, no Frame Generation, no issues.
Did you try it with Frame Generation off?

1 Like

The A310, like volocopter, like ATR, need a Puce with AVX instructions. Else CDT…

1 Like

Posts related to AVX (Advanced Vector Extensions). Not sure it is the only reason for CTDs with the A310 but for some hopefully it can help:

Thank you for that idea. For me it works now. I disabled DLSS and A310 works how it should.

1 Like

Similar problem here. My A310 CTD’s about 65% into the flight loading screen.
to reproduce:
Start Sim
Select A310- any livery
Select airports KSLC Runway 34R to KABQ Runway 08
CTD while flight loads.

This also happens at other airports where I select departure and destination airports.
I’ve noted this behavior also with the CS77- perhaps there is a gauge common to both aircraft.

My Leonardo MD-82 doesn’t CTD nor do other aircraft I tried.

Sometimes it won’t CTD if I select just a departure airport.
Of course I’ve been through all the usual trouble shooting steps- updated graphics drivers, removing addons from Community folder etc.

I am on the original install of MSFS from when it was first released.

Continuing the discussion from Loading the A310 leads to CTD:

MSFS v1.35.21.0

A310 iniBuild I solved my CTD and all of you may have the same issue.

I had uninstalled a lot of aircraft I don’t use and A310 uses some of those gauges.

My Solution I reinstalled 1 aircraft version of each one I had uninstalled and was able to load A310. :heart_eyes:

I have everything installed but yet it causes CTD.
Thanks though. I have re-checked if I was missing anything.

Really weird today its back CTD when click to Fly. :hot_face:

Ok guys I think I have solved it for me I had turned off V-SYNC turned it back on no crash. :heart_eyes:

Just loaded MSFS at CYVR Vancouver going to try a flight, fingers crossed.

Hi there, also getting CTD with the stock A310 - not an issue of mods as it happens in Safe Mode as well.

How did you go?

I get CTD on every attempt. I always have Vsync on and always TAA. Even with empty community folder. No other issues with any other aircraft.

Discontinued updates, they destroyed the sound pack to make it awful and gave up saying Ā« it’s msfs engine there is nothing we can do about it Ā» and now they expect us to but their A300… not sure I’d trust them.

Did a flight on Friday CYVR to KMIA 7 hours with no issues.

I understand that everyone’s system is unique and a solution may therefore not assist everyone. But I have discovered that reverting to DX11 has solved this problem for me. I have now loaded the A 310 four consecutive times from a fresh start to MSFS without a CTD. I was previously unable to do this. My setup, for information, is an i7 12700KF (3.61GHz), 32 GB RAM with a good ole’ 1080TI (11 GB RAM). If this assists anyone, you are most welcome.

I have a similar system; 12700k, 2060super, 32gb ddr4, m.2 nvme ssd. This ctd on clicking fly for 75% of flights has pretty much rendered the aircraft unusable for the past 3-4 months. It’s very unfortunate as it’s a fantastic aircraft, but really makes me rethink purchasing the A300. Seems like such a critical issue but for some reason it’s not talked about by INI and there seems to be no interest by them to address the issue. I get it, it’s difficult work, but the aircraft at the very least should run, if nothing else…

I’ll give it a try with DX11. I always run DX12.

I just decided to give a 50th chance to it. So I loaded it, Default one, white livery and used an Asobo airport and guess what?
Yes!! you guessed right. It didn’t even loaded it simply closed the game.
Definitely a no for me
I hope LatinVFR or Aerosoft makes it