Freeze or CTD when loading the A300

[Skauber]

Hi! I have seen others reporting this, I wanted to know if there is any progress on figuring out what is causing this?

In my case, if I go to the location "%APPDATA%\Microsoft Flight Simulator\Packages" and delete the folder "inibuilds-aircraft-a300-600", it has a better chance in loading the airplane, but it will still CTD sometimes. 

My system is AMD 5800X3D, Radeon 6800XT and 64GB 3600MHz ram. I tried to deactivate everything in the exe.xml file except FSUIPC, and I haven't been able to find a pattern on which airport or livery, or cargo vs pax version on the issue. Once it loads, it has been working fine with no issues after. No other airplane or addon is causing any issue with loading in to flight. For more info on what is normally running with the sim, I will post my exe.xml below.

<?xml version="1.0" encoding="Windows-1252" ?>
<SimBase.Document Type="Launch" version="1,0">
    <Descr>Launch</Descr>
    <Filename>EXE.xml</Filename>
    <Disabled>False</Disabled>
    <Launch.ManualLoad>False</Launch.ManualLoad>
    <Launch.Addon>
        <Name>Aerosoft VDGS Driver</Name>
        <Disabled>False</Disabled>
        <Path>F:\Installed\MSFS\Community\aerosoft-vdgs-driver\aerosoft-vdgs-driver.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>FenixA320</Name>
        <Disabled>False</Disabled>
        <Path>C:\Program Files\FenixSim A320\deps\FenixBootstrapper.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Fenix2GSX</Name>
        <Disabled>false</Disabled>
        <Path>F:\Fenix2GSX\Fenix2GSX.exe</Path>
        <CommandLine>-path "F:\Fenix2GSX\"</CommandLine>
    </Launch.Addon>
    <Launch.Addon>
        <Name>Couatl</Name>
        <Disabled>False</Disabled>
        <Path>C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Name>MDClient</Name>
        <Disabled>False</Disabled>
        <Path>C:\Users\larsr\OneDrive\Documents\Maddog X Files\MSFS 2020\MDClient\MDClient.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Name>TDS Sim Software GTNXi Gauge Integration</Name>
        <Path>C:\ProgramData\TDS\GTNXi\FlightSimEXE\TDSGTNXiFlightSimEXE.exe</Path>
        <CommandLine>-FSIntegration</CommandLine>
        <NewConsole>True</NewConsole>
    </Launch.Addon>
    <Launch.Addon>
        <Name>noolaero-module-vdgs</Name>
        <Disabled>False</Disabled>
        <Path>F:\Installed\MSFS\Community\noolaero-module-vdgs\Binaries\vdgs-util.exe</Path>
    </Launch.Addon>
    <Launch.Addon>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Name>FSUIPC7</Name>
        <Path>C:\FSUIPC7\FSUIPC7.exe</Path>
        <CommandLine>-auto</CommandLine>
        <NewConsole>False</NewConsole>
    </Launch.Addon>
</SimBase.Document>

 

[Deleted Account]

Thanks, we are still working to fix that bug 🙂

[Skauber]

Great, hope it will be fixed. I did notice in a different that there were some problems logging the issue on your systems, so if there is anything I can help in logging or potential fixes to test I would be happy to help. It has been happening quite consistently here since installing the airplane. 

[funkyj4ever]

i have latest update still ctd randomly when loading

[vaudes]

I can confirm I have this too! CTD and sometime stuck on the page to load the flight. Problem with PAX version, not with CARGO version on my side.

[Charles KS]

How hard can it be to solve this FFS?

 

[cconesa]

I had a few CTD when starting the sim after having chosen the aircraft and airport to spawn from. I have noticed that these CTD occur when I have installed a new livery that was not present before or I have modified (i.e. added cargo livery to the pellets or similar). When I do the changes or additions I mentioned before, before starting the sim, I delete the data cache (which is not enabled anyway) and have not had CTD since I've done this. A similar thing occurs with the A310 and does not happen with other aircraft in MSFS. Is it possible that there is a cache of sorts for the aircraft, so it loads more efficiently in MSFS?. If you recall, in P3D it was required to sometimes "clear the shader cache" to stop these sorts of CTD. Does MSFS have a similar thing that is creating a conflict with the inibuilds A310/A300 aircraft?. Just a thought.

[Christoph4445]

I've had CTD's with the A300 for about a week now. Usually on loading the A300 where the start-up page just stopped loading, sometimes a real crash to the desktop. Today it froze on me when I tried to change the weight AFTER calculating the performance. MSFS was running ok, but the A300 was frozen. This is very annoying as I like this add-on a lot.

[Enr1]

This aircraft is the only one to still cause random CTD during flight loading in the entire simulation...

[lehbird]

Any update on this? CTD upon loading virtually every time. The only thing that SOETIMES works is if I load default MSFS AC first, then reload the A300. 

[IniSteve]

On 3/9/2024 at 8:04 AM, lehbird said:

Any update on this? CTD upon loading virtually every time. The only thing that SOETIMES works is if I load default MSFS AC first, then reload the A300. 

We are testing an update currently that hopes to resolve a number of issues, including this one. 

[Trostbrot]

Hi all,

I have the same problem (CTD almost every time when loading the A300 as the first aircraft after MSFS was started) - even with the new PW version (clean install).

 

Kind regards
Stefan

[drayton_k]

This happens to me every time!

If I choose the A300 from the menu on first boot then FS CTD. I then restart the sim and select the same aircraft and it boots in fine. This is so frustrating so I hope the fix will come very soon.

Regards

Keith

[funkyj4ever]

still this issue exist. Come on

[moxiejeff]

Inibuilds -- any update on this? I'm seeing more and more posts about CTD every time people try to load A306 into the sim.

I've never experienced this until 1.1.1 and now it's happening constantly.

[BetterPilot]

I have this issue still on both A300 and A310 V1.1.1

Very frustrating, please fix. 

[drayton_k]

Yes come on Inibuilds please fix this annoying problem, mine still crashes during first loading then fine after that.

[late9]

I just had it CTD 2 times and once total cockpit freeze after using the mcdu... this is becoming a real pain.. this should have been fixed a long time ago. 

[richboy2307]

Hi,

Just to confirm that it isn't some addon conflict, try running with only the A300 in your community folder (no additional liveries either)

To run with a blank community folder without losing your addons:
1. Rename your existing community folder to ``_Community``
2. Create a new ``Community`` folder in its place.
3. Copy only the ``inibuilds-aircraft-a300-600`` folder inside it.
4. Run the sim and see if same problem persists.

If YES, then you can close the sim, and restore your original folder as follows:
1. Copy the ``inibuilds-aircraft-a300-600`` folder back to ``_Community``
2. Delete the new ``Community`` folder you made
3. Rename the ``_Community`` folder to ``Community``

If NO, then that means there is some other addon conflicting with the A300. Usual suspect is bad liveries, so you could try by adding only some of the other a300 liveries in until you can reproduce the problem. Same process for other addons till you find the culprit.

The team is looking into CTDs and addressing the reproducible ones each update, however crash-on-load is not something our team or testers have been able to reproduce successfully as yet.

Please report back with your findings, thanks!

[flyer23]

Hi @ all,

is there a solution out now? I bought the A300 via MSFS Marektplace, have the crash-on-load only after the last update and only with the PW-Version (both pax and cargo), had also tried with a clean install of the A300 and no liveries installed. I think the sceneries are not the reason because the GE-Version is working fine. 

Regards Steven (who´s hoping to get a solution for this)...

[richboy2307]

Hi @flyer23

We do have a new update for the A300 which will hopefully address the issues you are facing. Enclosed is a post shared on our discord. Please try that update (once available) and do report back if you still face such issues. Thanks!