Unfortunately I got another CTD about 6 hours into the flight. I was over Greenland so not much more to go. This time it was sort of self induced but was going to happen any as soon as I started doing stuff anyway.

All was well so I went to an exterior view of the aircraft. The sim stuttered and paused for a second and I got a pop in the audio. At that point I know I was doomed. Went back into cockpit view and it was pausing and stuttering pretty bad but still working. As soon as I dialed in a higher flight level on the AP it froze and about 5 seconds later shut down.

This is a classic memory leakage issue. Probably related to the bug already reported. Different systems will react different with the bug but it will probably be fixed when the fix the official bug that has already been reported for FS2024.

I plan to do some more debugging and joining the discord so I can report it and read about others with the issue. I don't think I am alone though.

On 6/16/2026 at 12:25 PM, alexcolka said:

I can confirm too that iFly 737 Max 8 works great in both 2020 and 2024, and it is completely understandable that 2024 version is experimental, because 2024 is still a moving target developing between frequent System Updates, Imagine the work for developers too, adjusting every time the add on for new sim versions.

It is experimental because it is an MSFS 2020 add on that was simply ported over to MSFS 2024 as opposed to a ground up new build on MSFS 2024.

6 minutes ago, longhaul747 said:

Unfortunately I got another CTD about 6 hours into the flight. I was over Greenland so not much more to go. This time it was sort of self induced but was going to happen any as soon as I started doing stuff anyway.

All was well so I went to an exterior view of the aircraft. The sim stuttered and paused for a second and I got a pop in the audio. At that point I know I was doomed. Went back into cockpit view and it was pausing and stuttering pretty bad but still working. As soon as I dialed in a higher flight level on the AP it froze and about 5 seconds later shut down.

This is a classic memory leakage issue. Probably related to the bug already reported. Different systems will react different with the bug but it will probably be fixed when the fix the official bug that has already been reported for FS2024.

I plan to do some more debugging and joining the discord so I can report it and read about others with the issue. I don't think I am alone though.

I find the ifly is great and stable if you are doing a 30 minute take off and landing circuit. But when I do a 5 hour airliner flight I get a CTD.

1 hour ago, Danthepilot77 said:

they basically said they wont do anything more until a 2024 version is released.

Er? No, they've said they're looking at a hotfix. Obviously the first key is figuring out why it only affects some users.

19 hours ago, longhaul747 said:

It's in the MSFS2020 folder even though it is installed in FS2024.

Because it's still a 2020 aircraft.

Once they make a 2024 native version, the WASM will appear in the 2024 folder.

19 hours ago, alanw2005 said:

Why is this taking so long?

Because they wanted to get SP1 out the door first. the Native 2024 version is their next project before moving onto the Max 9.

Edited Wednesday at 11:03 PM2 days by Tuskin38

43 minutes ago, alanw2005 said:

I find the ifly is great and stable if you are doing a 30 minute take off and landing circuit. But when I do a 5 hour airliner flight I get a CTD.

I just completed a 3-hour flight from Chicago to Dalles and I completed without issue Lucky me. Have you tried uninstalling the Navdata and reinstalling if you're using Navigraph?

Edited Wednesday at 11:15 PM2 days by Bigmack

16 minutes ago, Bigmack said:

I just completed a 3-hour flight from Chicago to Dalles and I completed without issue Lucky me. Have you tried uninstalling the Navdata and reinstalling if you're using Navigraph?

Thanks!! Will give that a try.

3 hours ago, longhaul747 said:

Unfortunately I got another CTD about 6 hours into the flight. I was over Greenland so not much more to go. This time it was sort of self induced but was going to happen any as soon as I started doing stuff anyway.

I'm in the same boat every long haul causing CTD. I suspect they have memory leak that propagate itself during long ops :(

Longest flight I’ve done on the current version is 3.5 hours, no issues others then the low FPS

that was in the 8200 variant

I’ll try a long flight in the standard model tomorrow

Edited Thursday at 02:44 AM1 day by Tuskin38

8 hours ago, longhaul747 said:

was well so I went to an exterior view of the aircraft.

Long shot and apologies if I missed this info but what livery were you using. Suddenly hickups just when going to outside View could mean you use an old livery and/or did not update it through the iFly Manager? My flights in the Max did not take longer than 2hrs so far but may try a longer flight later just to check

EDIT just realized I did this yesterday without issues, so about 3hrs airtime. Will try an even longer one now

KDEN/17L N0456F370 EEONS8 WYNDM DCT HCT DCT LNK J60 JOT J146 GIJ J554 JHW Q82 PONCT JFUND2 KBOS/33L

EDIT2 doing this now, 6hrs airtime

KBOS/15R N0475F320 HYLND7 HYLND DCT NOVON DCT KENPA DCT SAW DCT COLDD DCT FOSIG DCT DDY DCT MLD J32 LLC DCT LEGGS BDEGA4 KSFO/28

Edited Thursday at 07:09 AM1 day by DAD

4 hours ago, DAD said:

KBOS/15R N0475F320 HYLND7 HYLND DCT NOVON DCT KENPA DCT SAW DCT COLDD DCT FOSIG DCT DDY DCT MLD J32 LLC DCT LEGGS BDEGA4 KSFO/28

just entering the bay area, no probs so far, also going outside

just landed happily - all fine on my end

Edited Thursday at 10:50 AM1 day by DAD

19 hours ago, G-YMML1 said:

Still haven't touched it yet. Does 4x time acceleration work correctly?

I use it all the time...works perfectly for me. The trick is that you have to use the "Intelligent Cruise" features iFly built into the aircraft so it behaves properly in cruise when 4x is automatically activated. With it on, once you hit your cruise altitude (It won't engage in climb or decent)....It will go up to 4x in between waypoints on your flightplan. It will switch to 1x a few miles before a turn, and then back to 4x after the turn.

One trick I use to really speed things up is review the flightplan and delete any waypoints that are essentially drawing a straight line, because the sim will slow to 1x at each of them (in cruise). If they are mandatory, then you keep them, but I don't fly on Vatsim (while testing), so I take shortcuts all the time to MAXimize my testing time. :)

According to Southwest's site, they use the 175 seat layout on the 737 MAX. Wonder why Jviation made the SWA liveries for the 189 seat layout.

Edited Thursday at 02:46 PM1 day by RNAVV19R

53 minutes ago, RNAVV19R said:

According to Southwest's site, they use the 175 seat layout on the 737 MAX. Wonder why Jviation made the SWA liveries for the 189 seat layout.

There's a 178-seat option, why don't you try that. I really don't think it will make much difference.

9 minutes ago, Bigmack said:

There's a 178-seat option, why don't you try that. I really don't think it will make much difference.

I'm aware that the iFly comes with the 178 seat option. I'm just referring to the SWA liveries from Jviation. They were done only for the 189 seat layout.