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 36 minutes ago36 min 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 24 minutes ago24 min 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.