Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

A340 Not Loading On Start-up

Featured Replies

Every time I try to load the A340, it doesn't want to load. I have waited almost an hour. I have cleared the WASM folder multiple times, I have uninstalled and reinstalled both the aircraft and the game. I have also tried having just the a340 in my community folder, and it still wouldn't load. The A350 loads just fine. Also, if I exit the loading screen of the a340 and try to load a different aircraft, nothing else loads. However, when I load a different aircraft before the a340, it works.

I am having the same issue and did the same steps you did. Never got to fly the plane I bought which is disappointing. Hopefully this gets fixed as the a340 looks really good!

I got it to load! How I did this was opting out of the FS2024 beta so I could download the from the FS marketplace instead of just streaming it and then it loaded in within seconds. To me it seems the beta was a problem but I that may just be for me.

I’m experiencing exactly the same problem with the A340.

I have already waited for more than 2 hours, but the aircraft still doesn’t finish loading. I have also followed all the troubleshooting steps recommended by iniBuilds, including clearing the relevant folders/cache and even completely uninstalling and reinstalling the A340.

Interestingly, the Cargo version loads correctly, but the passenger versions do not. They get stuck during loading and the aircraft never appears.

Unfortunately, none of the recommended troubleshooting steps have solved the problem.

This problem only occurs with this particular aircraft. I have no loading issues with any of my other add-on aircraft. Therefore, it seems reasonable to believe that the issue is related to the A340 itself, and I really hope that iniBuilds can find a solution as soon as possible.

You are an excellent company and I have a lot of respect for your work. I truly believe — or rather, I want to believe — that you will find a solution to this problem very soon.

I confirm all the above problems. The aircraft in the beta version is not loaded, only the cargo version. I had to exit the beta version and the plane booted normally. Apparently version 1.0.12 is incompatible with the beta version of MSFS2024. So don't worry in vain. Troubleshooting steps will not help.

Agreed I have waited over an hour with no luck, however, the freighter loads immediately. I am also in Beta 6

I understand that returning to the stable version is the recommended solution while SU7 is in beta, and I also understand that beta versions can introduce compatibility issues.

However, what I find difficult to understand is why this problem is so specific and severe with the A340.

All of my other add-on aircraft continue to load and work normally in the SU7 beta. The problem only affects the A340, and even more specifically, the Cargo version of the A340 loads correctly, while the passenger versions do not load at all and remain stuck loading indefinitely.

I have already followed all the troubleshooting steps recommended by iniBuilds, including clearing the relevant files and folders, completely uninstalling and reinstalling the A340, and restarting my system. I have also waited for more than two hours for the aircraft to finish loading, but without any result.

There is also an important reason why I would prefer to remain on the beta version. On the stable version, I have another serious issue during long flights: when I reach the destination airport after a long flight, my FPS can drop dramatically and become extremely low. This is one of the reasons I want to remain on the SU7 beta and see whether the changes in this version address this long-flight performance issue.

Therefore, returning to the stable version would allow me to use the A340 again, but it would also bring back the serious FPS problem I experience after long flights.

I completely understand that iniBuilds cannot guarantee full compatibility with a beta version of MSFS. However, I would really appreciate it if this specific A340 issue could be investigated further, especially since my other add-on aircraft work normally and the Cargo version of the A340 itself loads without any problem.

The A340 is an excellent aircraft, and I have a lot of respect for the work iniBuilds does. I genuinely hope that a solution can be found that will allow me to continue using the A340 while remaining on the SU7 beta.

  • Staff
16 minutes ago, Jason Alexiadis said:

I understand that returning to the stable version is the recommended solution while SU7 is in beta, and I also understand that beta versions can introduce compatibility issues.

However, what I find difficult to understand is why this problem is so specific and severe with the A340.

All of my other add-on aircraft continue to load and work normally in the SU7 beta. The problem only affects the A340, and even more specifically, the Cargo version of the A340 loads correctly, while the passenger versions do not load at all and remain stuck loading indefinitely.

I have already followed all the troubleshooting steps recommended by iniBuilds, including clearing the relevant files and folders, completely uninstalling and reinstalling the A340, and restarting my system. I have also waited for more than two hours for the aircraft to finish loading, but without any result.

There is also an important reason why I would prefer to remain on the beta version. On the stable version, I have another serious issue during long flights: when I reach the destination airport after a long flight, my FPS can drop dramatically and become extremely low. This is one of the reasons I want to remain on the SU7 beta and see whether the changes in this version address this long-flight performance issue.

Therefore, returning to the stable version would allow me to use the A340 again, but it would also bring back the serious FPS problem I experience after long flights.

I completely understand that iniBuilds cannot guarantee full compatibility with a beta version of MSFS. However, I would really appreciate it if this specific A340 issue could be investigated further, especially since my other add-on aircraft work normally and the Cargo version of the A340 itself loads without any problem.

The A340 is an excellent aircraft, and I have a lot of respect for the work iniBuilds does. I genuinely hope that a solution can be found that will allow me to continue using the A340 while remaining on the SU7 beta.

Hi,

While I understand your concern, I think we also have to be understanding of the situation from our side. iniBuilds cannot reasonably chase down issues that appear within a sim update beta when, in many cases, the issue may be related to the core sim rather than our addon.

If we implement a fix based on behavior observed in a beta, and the issue is subsequently resolved on the MSFS side, we would then have to go back and rework or revert our own changes. Unfortunately, this simply isn't a practical approach.

I hope this helps clarify our stance and the reasoning behind it.

Thanks for your understanding!

Kyle - Community Manager

iniBuilds Ltd. | inibuilds.com

Thank you for explaining your position in detail. I now understand your reasoning better and why it would not be appropriate to make a change to the A340 based solely on an issue occurring in the beta.

My disappointment is mainly because this particular A340 you released was one of the main reasons I bought MSFS 2024. That is why it is especially disappointing for me that I currently cannot use the passenger version in the SU7 beta, while the Cargo version loads normally.

I understand your suggestion to return to the stable version, and I will wait to see how the beta develops and whether the issue is resolved in the upcoming versions.

Thank you again for the explanation and for your work on the A340.

Create an account or sign in to comment

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.