fearlessfrog

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.

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. 🙂

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').

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?) 🙂

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.

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.

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'. 🙂

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.

The March 2 update on SU12 beta seems to have fixed this, as per the release note: > Fixed a crash when using WASM network api with a uri that has no path component. It has never worked for me before (always just flashed pending), but is now working ok and importing well. Thanks.

That's a bit generous 🙂 as the fix was to remove the option all together from the MCU and just let the EFB do it. I see the beta build rolled out to all in MSFS now, so curious to see if it fixes it for everyone as 'Fixed SimBrief Import' is still in the release notes, despite it not fixing it for anyone (that had an issue to begin with anyway). I'll try again, as maybe the A310 updates between the beta and the release version.

Perhaps the AIRAC has to be the exact same as the aircraft regardless of if the waypoints exists, which I think is 2211 in the A310? The simbrief.xml certainly contains the AIRAC version it's using. I'm using Navigraph AIRAC 2209 on a lapsed subscription currently, so maybe that it is?

There's a bunch of things you could try if the devs can't recreate the issue: - Gather detailed specs/configurations/addons from the people who have the issue, to see if there is a common pattern. - Produce a build with logging and let someone with the issue use it and then return the diagnostics to see what the issue is. - Try additional fixes like the last patch did, even though the thinking it was purely an Asobo hosting issue. I'd admit it's not a super important feature, as there are work arounds with using other apps etc but it must be nice from a development point of view of a newly released add-on to figure out why some of the customers can't use it all. Other aircraft all seem ok, so there must be something different about the A310 worth learning. From my end I know it's not my simbrief id, as I tried with Ellis's and it still didn't work.

I think that path might only work if you have the Steam edition of MSFS? The Microsoft Store edition uses something like: C:\Users\<Username>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\microsoft-aircraft-a310-300\work\flightplans I needed to create an empty flightplans directory, but now it works in terms of a direct Simbrief File download (the MCU simbrief way does not work for me).

Same here. Is it still thought to be a Microsoft server issue, and nothing that inibuilds can do about this? The latest patch notes said a fix had been made but still no luck. The behavior changed in that it doesn't get stuck at 'pending' but just flashes and no imported flight plan. Is there any info or diagnostics we can supply to help track this down?

Hello! Just updated to MSFS 1.29.30.0 and iniBuilds Airbus A310-300 v1.1.6. On the previous version I got a never ending 'Pending' on the Simbrief MDU button press and I now get a single flash and but unfortunately it's still not loading the flight plan - it stays saying 'SIMBRIEF'. The iniConfig app 'Export Plan' works fine with the simbrief alias I'm using (as does the simbrief file downloader), so still something going on in the sims way of accessing simbrief.