I tried the normnal things like cleaning WASM etc, but the planes keep loading forver. No errors. Also noticed when trying to load the Inibuilds A350/340 after that try no other planes are loading.
Anyone with the same problem?
I did flight yesterday with the A350 on Xbox from VHHH to LSZH and it worked for me on this beta. I was using Inibuilds VHHH & MK LSZH.
OK Thanks. I am on a PC. Might be the new driver.
I timed it on my 9950x, and the a350-1000 no cabin took 4:45 to load. I’m timing the a340 now, and it’s over 11 minutes and still no joy.
I have managed loading the A350-900 once, also after cleaning WASM, because initially it did not load. Now is does not even load the model for a flight. I can select it, then select a starting position.
But when I start the flight, it is just loading forever. And you can see the aircraft model is not even loading. Normally I know the initial load of the A350 takes a few minutes, but then you can see the model is already loaded.
I am not sure it is just the A350 that has issues, just did one of the challenges, it loaded once, I screwed up the landing, so I hit restart. It did not load again. After restarting the sim it did work again.
I’m also on the PC version
I tried the a340 again, but no load. I restarted the sim, and strangely, Free Flight had the a350 selected. It failed to load the a340 again. I restarted the sim, this time the a340 was selected in Free Flight. Installation of the a340 is not available in the Beta, so I disabled and re-enabled it. Still no load.
Update: I uninstalled both the Aerosoft a330, and the Toliss A340. The INI a340 Freighter loaded straight away after that. I disabled and re-enabled the INI a340, and now it won’t load again.
The INI a321 will also not load.
The FBW a380 will not load.
The AS 737max would not load.
I restarted the sim. Free Flight still had the INI a340 selected. I switched to the AS 737max, and it loaded fine.
I emptied out my Community folder, restarted the PC, and restarted the Sim. Only the Freighter versions of the a340 would load. The other versions would not even load in the Configuration screen.
It looks like AFTER failing to load the a340, nothing else will load.
Restarting the sim, and choosing another aircraft clears up the loading issue for other aircraft.
I tried and I see something here. I am on a 4070 Super TI. A350-900/1000 No Cabin loads and works. A350-90/1000 Cabin does NOT load. As for the 900ULR there is only one option with Cabin and it loads and works. The A340 only loads in Freighter versions.
ISSUE DESCRIPTION
Description of the issue:
Many addon aircraft like the inibuilds 350 and 340, FSS 727 and PMDG 737 are not loading anymore.
Loading screen gets stuck while still in the top view above the clouds
FREQUENCY OF ISSUE
Everytime
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
-
Select one of the aircraft above
-
Select any airport and hit Start now
-
Loading screen appears and nothing happens anymore
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using:
[PC Only] Are you using Developer Mode or have you made any changes to it?
Happens both in normal and developer mode. No changes made. Used just for display FPS
[PC Only] What GPU (Graphics Card) do you use?
AMD 7900xt
[PC Only] What other relevant PC specs can you share?
Ryzen 7 5800X3D, 64GB RAM, resolution 1440p
Same here on latest Build
Have you waited it out, these addons usually compile their WASM stuff after every update and it can take ages where the sim just sits there doing nothing.
Just leave it for a bit and see if it starts working eventually. I’d avoid interrupting it by hitting esc, as this can cause WASM issues.
Define “a bit”.
I waited for over an hour and nothing happened.
In the past, when loading an aircraft for the first time after installing it, the wasm build was taking 20-30 minutes max
the A350 can be flown without the Cabin if you select a cabin no luck
There’s a bug open on this already. If you try to load the a340, nothing else loads after that.
Do you mind pointing me in the direction of this bug? I’m just trying to keep on top of everything and make sure the forums are tidy!
1 Like
This was the other bug Addon aircraft not loading anymore that has been closed and merged into this one (title has also been updated to reflect issue happens with multiple 3rd party aircraft).
Thank you! I think we’ll log this one out of an abundance of caution in case there may be an issue with something underlying that is affecting lots of products collectively.
2 Likes
Thank you for the bug report.
We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.
1 Like
This is still present in 1.9.12.0.
Yesterday afternoon, I was able to load into both the PMDG 737-800 and the Inibulds A350 one time each. Subsequent attempts to reload resulted in infinite loading cicle/music.
I don’t own the A340 or the FSS 727, so those can be ruled out as any specific factors in my case.
I’ve been troubleshooting an issue where the iniBuilds A340 gets stuck indefinitely on the flight loading screen in MSFS 2024 build 1.9.12.0.
What we tested and found:
-
Performed a clean uninstall/reinstall of the A340 through iniManager.
-
Confirmed iniManager is pointing to the correct Community folder:
E:\FS2024 Community -
Confirmed MSFS itself is mounting the same Community folder.
-
VFS confirms
inibuilds-aircraft-a340is mounted correctly. -
The A340 installed through iniManager takes priority over the remote/streamed A340 package; MSFS reports the remote version as shadowed by the Community version.
-
Removed a mistakenly nested
Community\StreamedPackagesfolder that MSFS was trying to interpret as an addon. -
Tested different A340 variants:
- Passenger EIS1 initially hung.
- Passenger EIS2 initially loaded.
- Cargo EIS1 loaded.
- Cargo EIS2 loaded.
- Later, Passenger EIS2 and Cargo EIS2 also began hanging.
-
Tested with the Edelweiss / A340 Livery Pack III disabled and stock liveries only. The problem remained.
-
Removed all other Community addons and tested with only
inibuilds-aircraft-a340in Community.- No GSX
- No FSLTL
- No WinWing
- No MobiFlight
- No Navigraph
- No scenery
- No additional liveries
-
The A340 still hangs with this minimal Community setup.
-
Several warnings were ruled out because they also appeared during successful A340 loads:
navigation_graph_*.cfg can't be found- missing cabin seat-number textures
fapscreen.pngmissing- electrical
CIRCUIT_XML:8-15warnings
-
A
WASM: ERR_FATAL_FILE_ERROR (-239)seen in the console was traced to the WinWing WASM module, not the A340. -
The A340 WASM previously loaded successfully and reached:
DB LOADED
and
WASM: Module inibuilds-A340.wasm initialized. -
We then reset only the A340 compiled WASM cache.
-
After the reset, the current failed runs consistently reach:
WASM: Detecting module inibuilds-A340.wasm as a Release build WASM: Compiling module inibuilds-A340.wasmbut never continue to:
WASM: Module inibuilds-A340.wasm loaded... DB LOADED WASM: Module inibuilds-A340.wasm initialized.
Current conclusion
At this point we have effectively ruled out:
Community conflicts, GSX, FSLTL, WinWing, MobiFlight, liveries, incorrect Community path, iniManager installation path, and the normal A340 warning messages.
With only the base A340 installed in Community, the aircraft still hangs while MSFS is trying to compile/load the A340 WASM.
So the strongest current indication is that this is related to MSFS 2024 SU7 Beta 1.9.12.0, rather than a normal A340 installation problem.