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.

First 2 flights, both with FMC/flight path freezes

Featured Replies

On 1/2/2026 at 2:14 AM, RoyalAviator said:

Has anyone investigated whether Navigraph navdata can be the culprit here? I saw a couple of the threads allude to this.

 

Regards,

Could be, although flying with default AIRAC is tricky on VATSIM. Im wondering if it has anything to do with streaming vs downloading.... Im eagerly waiting for the inistore release - something tells me MSFS marketplace download hosting is quite rubbish, might lead to issues. I was streaming the A340 up until eysterday when I downloaded it, first flight and I get the system freeze (different to WASM crash).

  • Replies 69
  • Views 39.9k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • I can confirm the iniManager makes absolutely no difference - im suspecting this is a MSFS2024 online services / connection issue. Its completely random .... It happens during climb out, sometimes dur

  • Happened to me while still sitting on the apron. I was going through preflight and MCDU simply stopped responding.

  • Ok, my third flight attempt, I've completely turned off the gsx synchronisation features in the efb, and immediately the nose wheel steering works AS IT SHOULD. So thats a step forward, once I'm in cr

Posted Images

This is still happening to me with the latest 1.0.7 update. Im using default navdata and currently streaming the aircraft from the marketplace (I had same issues with the package downloaded) 

@iniBuilds is this a known issue? Its been over 3 months and still no official response as to whether this is being investigated.

Is there any way this could be a marketplace issue? Is there anything inherently different about an aircraft downloaded from marketplace vs iniManager in the way that it loads or communicates with the sim? @Eddie

I'm begging for a response here, or at lease some form of acknowledgement.

image.thumb.png.1e9f84b87a8b3977c1bf7eeba5aa60c6.png

Edited by Roders

14 hours ago, Roders said:

I'm begging for a response here, or at lease some form of acknowledgement.

Hi. The marketplace build is identical code wise to the manager build and is merely package in accordance to the MP framework. Sadly, there is nothing conclusive about the freezes that occur in this manner.
Best we can currently do is note them and send the info to Asobo. We have been in constant contact with them since this first started occurring but have yet to pin down a reason as to why only a small percent of users experience them. 

5 hours ago, IniSteve said:

Hi. The marketplace build is identical code wise to the manager build and is merely package in accordance to the MP framework. Sadly, there is nothing conclusive about the freezes that occur in this manner.
Best we can currently do is note them and send the info to Asobo. We have been in constant contact with them since this first started occurring but have yet to pin down a reason as to why only a small percent of users experience them. 

Thanks for the response! Once my transfer request has been approved I’ll be using the iniManager version to test further. The only reason I mentioned this is because I’ve had no issues with the A350, although that was a few months ago in MSFS 2020.

I know the underlying code is identical, but I do wonder whether differences in how the aircraft is packaged or how it interacts with the sim could play a role here. Initially I was suspecting some kind of internet-related issue. Even though my connection itself is very solid, I currently only have access to a wireless connection rather than wired Ethernet.

Would it be possible for others in this thread to confirm whether they’re using a wired or wireless connection?

@IniSteve would it be worth considering whether a very brief interruption in connectivity could trigger this issue? Something momentary. The freezes only seem to happen on long-haul flights, which is where the chance of a small wireless dropout is higher. Since this appears to be a sim communication issue, it doesn’t seem completely impossible.

@iniBuilds I might be clutching at straws here, but it could be worth investigating. It might also help explain why only a small number of users seem to be affected if it correlates with those running the sim on wireless connections.

Just a thought, happy to help test or gather more info if useful.

I can confirm the iniManager makes absolutely no difference - im suspecting this is a MSFS2024 online services / connection issue. Its completely random .... It happens during climb out, sometimes during cruise. Temporary connectivity issues while using wireless internet might be the culprit. @IniSteve can you try recreate this, perhaps the team can try purposely disrupt their internet connection while flying the aircraft, see if they can reproduce this. The joys of online gaming!

I cant begin to describe how much of my time I have wasted trying to troubleshoot this issue - could you please at least give this a try and report back... im begging you @iniBuilds!

image.thumb.png.1e67e19eca88975f3ba9c2eeca10765b.png 

 

Hi!

I am suffering from the same issue since the latest VIP update. Everything went well before that. I don't have any WASM crashes but after around 2 hours into any flight the aircraft just freezes.
FYI I do have wireless (5G) internet but I am connected to my router via LAN so WLAN is no issue. Any idea what to do?

@IniJamir In the WASM master thread it is stated: 

Quote

The "sim-freeze" is a separate event that is tied to something on the server side which we are investigating with Asobo.

Is it that what we are experiencing?

  • 2 weeks later...

I've experienced a PFD and system freeze as well. On my way from Cape Town to Frankfurt. Checked the console and it was not a WASM crash. I was lucky to have noticed it in time and loaded my save to recover.

image.thumb.png.14458301192bb09ffc7ea94be1c3352b.png

  • 3 weeks later...

Sorry for posting twice in a short time. I've tried switching from Navigraph navdata to In-sim navdata, no difference. I've switched off Automatic step-climb import, no difference. However, I do notice that the crash happens after an automatic step-climb. May I confirm whether it is the same for everyone?

I've tested 2 flights with the following settings and had no sim freeze and flight path deviation.

  • In-sim navdata used
  • Disable auto import step climb
  • Disable auto step climb
  • Not entering any step climb in the FMS, only by selecting level with FCU then Alt push.

Edited by C. Schaffhausen

9 hours ago, A340iB-2025 said:

What is the disadvantage of using the sim-navdata vs. the navigraph-navdata?

I have no idea, but since I didn't end up freezing and deviating I'll keep flying like this until Inibuilds finally fix it for good.

  • Author

Just popped back to see this thread, sad that this is still happening! hopefully Inibuilds can squash this in the end. Personally I was able to get a full refund for this product through microsoft, hopefully the L1011 isn't like this!! fingers crossed, can't wait for the L1011

On 3/5/2026 at 12:52 AM, A340iB-2025 said:

What is the disadvantage of using the sim-navdata vs. the navigraph-navdata?

There shouldn't be any

On 3/4/2026 at 5:10 AM, C. Schaffhausen said:

I've tested 2 flights with the following settings and had no sim freeze and flight path deviation.

  • In-sim navdata used
  • Disable auto import step climb
  • Disable auto step climb
  • Not entering any step climb in the FMS, only by selecting level with FCU then Alt push.

I just finished a 15 hour flight in A340 with Navigraph Data, Auto-Step Climbs, Auto-Imported Step Climbs and while I haven't had the freeze you detailed happen to me recently, it has happened once to me since release. We have seemingly squashed the WASM where one changes there STAR/RWY as we've been unable to reproduce it internally during wide-range testing recently. It just goes to show how difficult it can be to navigate and squash WASM issues as they arise, but we haven't forgotten nor given up.

  • Author

So I literally just had the same exact crash happen to me, but this time it was in the Inibuilds A330-200 thats part of the base msfs2024 sim. I didn't think the A330-300 or -200 suffered from this same issue. Where in the A340 I was having the crash every other flight atempt. I've only ever had the crash once in the maybe 25 flights ive done so far in the Inibuilds A330. And to be fair, all my flights in the A330 have been in the longer -300 variant, and today was my first longhaul in the -200.

1 minute ago, Mantock said:

So I literally just had the same exact crash happen to me, but this time it was in the Inibuilds A330-200 thats part of the base msfs2024 sim.

I experienced the exact same thing around a month ago, pretty much every second flight with the A340, and then once in the A330-300 while departing Mumbai. I have since gone back to MSFS 2020, much more stable platform.

 

@IniJamir was there any feedback from the dev/testing team on my connectivity theory? Did anyone try to purposely disrupt their internet connection while flying the A340 to see if the issue can be recreated? Im still partly convinced this is a sim connectivity/stability issue. I havent tried any flights without auto step climb enabled. I never flew with Navigraph data enabled as the sim navdata is up to date anyways.

 

Since this happens with both the 340 and 330 im leaning more towards an internet/connection related problem. As I have wireless connection, any small disruption might result in loss of comunicaiton between sim and module, which is basically what this issue is (not WASM related).

Screenshot2026-03-12000774.thumb.jpg.d8e073e3a0be750ba64d9d51d525e2cc.jpgScreenshot2026-03-12000775.thumb.jpg.8ebdab9b31084ea1dd86b24a05245b15.jpg

i've attempted this flight now twice. First I crashed somewhere in Russia because it completely froze up, now in the middle of nowhere. The first flight from EDDF to RJGG also took me 2 attempts to accomplish properly. Every second flight ends in a crash, either WASM or like in the screenshots a complete freeze where nothing works anymore. This was supposed to be a 15hr flight and again like with the A350, I can't trust it to complete any longhaul with this thing. I'm tired of this. And no, autosave is not a solution when the crash happened hours ago and I just woke up to see this.

This was with default navdata as well as Navigraph, so no difference between the two. Auto step climbs enabled and also automatically imported from Simbrief,

Edited by Skyrock

I have not encounter the issue in 1.0.10, but now I do. The sim was minimized in the task bar and I was not able to open the window again. I disabled auto import step climb and entered them manually, auto step climb enabled, navigraph navdata used.

image.thumb.png.91d0501a4b17b5438fcf26d391e40d14.png

  • 1 month later...

Another flight freeze, this time on 1.0.11. The sim was minimized in the task bar and I was not able to open the window again. I disabled auto import step climb and entered them manually, auto step climb enabled, navigraph navdata used.

image.thumb.png.735b56884270467657df78616ab32abe.png

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.