Come on guys, someone has a problem with iFly Max and some hardware and it’s suddenly a disappointment? I ditched MSFS2020 as soon as F24 got released, but last time I flew it in MSFS2020 it was an awesome addon. And let’s not talk about how it compares to Asobo Max…
3 Likes
I haven’t had any real issue in the iFly at all, and I’ve been flying it since release day.
The devs just this morning released a bunch of WIP images of the aircraft in FS2024 on their Discord, though still no word on a release date target.
2 Likes
Maybe try flying it again. If you missed the point made by Fortn00b15 he is talking about game braking bugs introduced in the latest update that have haven’t been fixed, and devs are fully focused on FS2024 update to address them. Hope it’s clear now.
1 Like
my max is completely updated and i’ve flown it numerous times (in '20) over the past week and haven’t had a single issue with the plane. i guess i’m lucky!
5 Likes
While @DrVenkman3876 @scoobyx say there’s nothing wrong with it. And no, I’m not going to install 2020 only because of that. So yes, that’s clear now - I’m happy they’re working on a MSFS2024 compatibility now.
1 Like
flawless as usual 
I haven’t read the whole thread so not sure if this has already been discussed, but I have seen the problem you mention here with the throttle cutting out right after takeoff. However, I found that if during your takeoff roll you press the TOGA button on the throttle the plane takes off and the throtte doesn’t cut out and it climbs out normally.
Just mentioning this in case it helps others that have run into the takeoff throttle glitch.
Even though I’m also very disappointed that this throttle bug still hasn’t been fixed, I use two workarounds that allow for smooth takeoffs and keep the aircraft usable for me.
Workaround 1:
Before takeoff, set your V2 speed on the MCP.
Arm the autothrottle (A/T ARM).
Normally, the procedure would be to advance the thrust lever to 40%, let the engines stabilize, and then press TOGA.
The workaround: instead of setting the thrust lever to 40%, move it to the center detent (in my setup, that’s about 50% thrust), then press TOGA.
The reason: most thrust levers have a dead zone at the center detent. This dead zone prevents the lever from sending “noise” during takeoff and avoids overriding the autothrottle.
Workaround 2 (if you’re still experiencing the bug or your thrust lever doesn’t have a center detent):
(I know some 737 purists will say this doesn’t follow Boeing’s official procedures—but hey, I just want to help people get airborne at all.)
Before takeoff, set your desired climb speed (e.g., 240 knots) on the MCP, not V2 speed.
Do not arm the autothrottle. Leave it off.
After spooling the engines to 40%, advance the thrust lever to full power and begin the takeoff roll.
Once the engines switch from TOGA mode to CLIMB mode, you can safely arm the autothrottle and engage your desired mode (e.g., LVL CHG) to continue climbing at climb speed.
The bug seems to occur only while the engines are in TOGA mode.
1 Like
This thinking might be at the root of your problems. “Most thrust levers” don’t have detents at all. I know some consumer flight sim gear does, especially stuff intended to replicate Airbus throttles. Boeing thrust levers are continuous in nature, with no detents at all.
Further, in the EFB for the iFly, there are settings regarding thrust lever override to help deal with noise in controller thrust levers. You should investigate setting those and see if that resolves your problems.
2 Likes
I’m aware of the EFB settings related to thrust lever override. However, none of the available options prevent the bug from occurring.
Once again, as other users have already mentioned in this thread, this issue did not exist prior to version 1.0.3.
What happens is that the engines completely shut down in TOGA mode during the initial climb, and the aircraft enters what appears to be a landing configuration—this is also accompanied by a “RETARD” message on the PFD.
This abnormal state cannot be explained by thrust lever noise, nor by the fact that I’m using a thrust lever with a center detent.
As a software developer, I use the term “root cause” with caution. Thrust lever noise might trigger something, contribute to the issue, or even cause a race condition introduced in version 1.0.3—but it is certainly not the root cause.
By the way, I can operate all PMDG Boeings using the same thrust lever without any issues and was able to operate the iFly before 1.0.3 without any issues.
1 Like
Can someone please contact the developers and tell them to add some blurred reflection material on the PFD and MFD. I don’t use Discord.
IRL:
In FS2020 (iFly 737 Max):
(1) That is an issue with all 2020 planes that have not been specifically updated to 2024 to fix this reflectivity.
(2) This is not a 2020 plane that has been updated to 2024 (yet).
Hopefully the 2024 version of the airplane will have PFD and MFD reflectivity. But, the new screenshots that iFly has unveiled show no reflectivity either.
Good for you getting it to work in 2024. I haven’t had success yet (SU2).
If iFly were to add reflectivity to the PFD and MFD, there would definitely be users who find it distracting, as it could make it harder to read the precise data on the 738M displays.
It would make sense if iFly added reflectivity to the PFD and MFD, but only if they also included an option to disable it - either in the settings or during installation.