fearlessfrog Posted September 29, 2023 Posted September 29, 2023 Hello! Now SU13 is released I am getting a A310 CTD every time in aircraft loading (post hitting 'Fly' in the map screen) and have narrowed it down to being the 'microsoft-a310-american-n2291w' livery perhaps causing it? If I swap to other livery like something built in like WorldTravel then the flight seems to load ok. I get a CTD every time with the AAL livery so far.
fearlessfrog Posted September 30, 2023 Author Posted September 30, 2023 Just in case, I removed and reinstalled all A310 liveries using the Inibuilds Livery Manager. They are in the Community folder and not soft linked. It seems to be every livery other than the ones that come with the package with MSFS (e.g. Delta and Transat both CTD'd as well). I guess the workaround for now is to rock 'World Travel'. 🙂
Deleted Account Posted September 30, 2023 Posted September 30, 2023 Mmh, have to say I can't reproduce this. Can you please try with an empty community folder?
fearlessfrog Posted September 30, 2023 Author Posted September 30, 2023 Ok, thanks for the reply. For me the Inibuilds livery manager puts the liveries (like the AAL one) in my community folder, but I’ll try just with them alone if that’s what you mean.
Deleted Account Posted September 30, 2023 Posted September 30, 2023 29 minutes ago, fearlessfrog said: Ok, thanks for the reply. For me the Inibuilds livery manager puts the liveries (like the AAL one) in my community folder, but I’ll try just with them alone if that’s what you mean. Well yeah, empty apart from the livery 😄   1
fearlessfrog Posted September 30, 2023 Author Posted September 30, 2023 I renamed Community folder to oCommunity, created an empty one, went to the iniBuilds Livery Manager and went to put the AAL livery back in. Surprisingly it still had 'Uninstall' as an action against it, so it must store or cache that somewhere other than just having the existence of the folder? Hit 'Uninstall' on that livery and then 'Install' and got back a single lonely 'microsoft-a310-american-n2291w' folder in my C:\MSFS\Community. Started up in a stock airport (as all my other weren't there of course) and it worked. I use AddOns Linker to manage the folder so I'll have a go seeing what causes it, but I have a few things (GSX, Navigraph, Sky4Sim, 50 airports, 25 aircraft) so tbh probably not going to happen conclusively. Of all the suspects, it'll probably be something like GSX or maybe even FS Traffic, so I might try those. If I use my existing Community folder with everything in it but then just remove 'microsoft-a310-american-n2291w' folder then the A310 works fine, as it's not using an extra livery, just a stock one. Hope that helps.
fearlessfrog Posted September 30, 2023 Author Posted September 30, 2023 Curiouser and curiouser. I popped into the .to and grabbed a random livery, put it in the community folder and it all seems to work. Not sure what that means but I'm back flying even if I have to deliver parcels.. 🙂  (cargo variant wen?) 🙂 Â
Deleted Account Posted September 30, 2023 Posted September 30, 2023 Thanks for testing, would love to know when/if you find out what caused the crashes in the end 🙂
fearlessfrog Posted October 1, 2023 Author Posted October 1, 2023 Looks like it is GSX Pro causing the CTD with the A310 but only with certain type of liveries like the AAL. I'll report it over there but if anyone googles their way here then this seems to be the reason. The workaround is to exit the Couatl engine before hitting 'Fly' on the A310 and then once in the cockpit just start it manually again and it'll work (there's a default windows shortcut for 'Start Couatl for GSX MSFS' installed by GSX').
fearlessfrog Posted October 1, 2023 Author Posted October 1, 2023 GSX Pro people say it can't be them, as it shows MSFS crashing first in the GSX log. Maybe some sort of resource issue with MSFS and that GSX tips it over the edge in this case (not their fault, just the fragility of MSFS). This only happens with the A310 and GSX for me (not the PMDG or Fenix or CRJs), but the workaround gets me through it even if the odd 'I'm a people person!' GSX guy says it's just pure luck every time. No worries. 🙂
fearlessfrog Posted October 2, 2023 Author Posted October 2, 2023 I raised the bug/ticket at MSFS for this as it does seem sim related in that I can make it happen with an empty Community folder and no marketplace add-ons installed (sometimes, like 1 in 5). One workaround does seem to be you can use Dev Mode and then a 'Load Aircraft' and I've not got that to fail so far. So basically you spawn in with another aircraft and then switcheroo when all loaded in. Wanted to pass that on if anyone else gets this and wants to fly.
Andrew Peacock Posted October 3, 2023 Posted October 3, 2023 Hello, Just joined the forum to add to this, as I'm seeing the same thing after SU13. With an empty community folder the first time I select a non-default livery I'm getting a CTD, I don't think it's GSX related as I've never been a user of that. Usually, after re-opening the sim, I can go back and select the same livery and everything is fine. However, if straight after the sim starts I choose a different non-default livery, I'll get another CTD. Happy to provide any more info if it'll help, but admit up front that I'm on a fairly ancient PC (although pre SU13 I had no problems whatsoever). Cheers, AP 1
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now