iFly 737 MAX 8 Gets New Update (2025)

MSFS

iFly has updated their Boeing 737 MAX 8 to version 1.0.3 for Microsoft Flight Simulator 2020.

This significant new update features a long list of bug fixes, changes, enhancements and more. Whilst the team are working towards the MSFS 2024 compatible build and MSFS 2020/2024 Service Pack 1, they decided to package all those items completed to date for the MSFS 2020 MAX 8.

The lengthy changelog can be found below.

If you don’t already own the iFly Boeing 737 MAX 8 for Microsoft Flight Simulator 2020, you can buy it from the Flight1 website for $69.95.

To update, you will need to make sure you have v1.0.2.7 of the iFly Manager.

“This must be a full, new, fresh, clean installation! Use of iFly Manager version 1.0.2.7 or later is required. Use the Manager “Uninstall” feature. Note: If you do have the correct version of the iFly Manager, you will be notified to upgrade. If you do not upgrade the Manager, you will not be able to install v 1.0.3 of the MAX.”

iFly 737 MAX 8 Changelog

• CDU keyboard J triggers the animation of the letter A
• EFB Airport MAP to freeze the aircraft.
• YAW Damper Light (delay increased from 2 seconds to 3 seconds)
• The length of the engine BRM time is dynamically adjusted according to the
  external temperature. When the temperature is extremely low (above -10 degrees),
  the BRM time can reach 3 minutes.
• Thanks for adding the delay between selecting GND and the START VALVE OPEN
  light but it’s a bit too long now, by about a second (just based on my impression of
  it). Also, you should get N2 indications the instant that the start valve opens, there’s a
  lag there too in the iFly which shouldn’t be there.
• The N1 fan visually snaps immediately to high speed outside as soon as there’s
  N2 rotation, although N1 indications are as expected.
• The BRAKE TEMP caution light is still present even when the brake temp sensor

  option is selected.

• LE flaps transit light illuminates on rotation and comes on and off intermittently
  during the initial climb. If this is based on some report from irl, let me know but it’s
  something I’ve never seen in several thousand hours of flying the NG/MAX.
• After takeoff without VNAV armed, the speed bug was set to V2, the bug was well into
  the low-speed bricks with the alpha floor symbol flashing on the speed window. V2
  It’s pretty close to the bricks but definitely shouldn’t be in them. ZFW was set and
  checked both in the FMC and in the payload page in the EFB and I did click on “set
  payload” during preflight.
• Engine acceleration is slow from idle at low altitudes. Takes about 20 seconds to
  “unstick” when adding thrust. Flight idle should prevent this at low levels.
• With the seatbelt sign deliberately left in AUTO, no chime is audible when the
  flaps or gear are extended. It still chimes when turned off after parking, so the
  sign is coming on, it’s just not dinging.
• Quick align (switching IRS to ALIGN, then back to NAV and re-entering
  coordinates) is resetting the full align timer and taking 10 minutes. Quick alignment
  should only take about 30 seconds after the switches are turned back to NAV.
• THRUST REQUIRED message shown on FMC in the flare, that doesn’t happen
  on our jets, not sure if it’s some kind of interaction with a company option.
• Fuel-used counters are being reset to 0 without using the reset switch. Showed
  zero fuel burn, so must have occurred on shutdown.
• KEY bindings through Plugin not being saved
• Brake Temp and Pressure Lights
• PFD Small details
• WINDOW HEAT LIGHT ON TO SOON
• PLI does not appear at slow speeds with flaps retracted
• GLS warning light when press shows GPS lighting up instead of GLS
• Radio Altimeter is not correct in the flare
• Black Box bug on VSD mode
• Lights test small bug
• HGS Tweaks and Fixes

• a. Flight path symbol – in flight, this is depicted as a gull wing symbol in our aircraft. While that may be an option, I’ve never seen any video or images from any aircraft using the HGS 4000 with any other symbol. On the ground during rollout or for a low-vis takeoff, the ground roll reference symbol has straight “wings”, but in flight, it immediately becomes the gull wing symbol.

• b. In IMC and AIII modes, the localizer and glide slope needles are referenced to the course set arrow and the glideslope reference line, respectively. In the iFly Max, they seem to be referenced to tick marks on the flight path symbol itself (which don’t exist in the plane). It reminds me of the DCS Hornet ICLS, but that’s not right for this HUD. Note one of the attached screenshots in AIII, showing a localizer needle displaced slightly to the right from the course set arrow, and the guidance cue commanding a slight right bank to correct.

• c. Rotation cue – This (the tie fighter wings looking symbol around the aeroplane reference symbol) should become visible when TOGA is pressed on the ground. Currently, it only appears at Vr. And then, it rises far too rapidly. The whole idea of it is that you rotate at a rate that keeps the aeroplane reference symbol captured within the rotation cue, so it should be rising between 2 – 3 degrees/sec. From the manual: “Using the technique of keeping the aeroplane reference symbol centred in the rotation cue, rotation rates vary from 2 to 3 degrees per second with rates being lowest on longer aircraft. Liftoff attitude is achieved in approximately 3 to 4 seconds depending on aircraft weight and thrust setting.”

• d. 15-degree pitch line missing for takeoff.

• e. AIII – flare cue briefly disappears when meeting flight path symbol. Should not do that; that would be a disconcerting moment to briefly lose all flight guidance ;).

• f. AIII – in the rollout guidance after touchdown, the ground roll reference symbol is up in the horizon line and the rollout guidance cue is well below it. Thus, it is impossible to keep the guidance cue centred in the ground roll reference symbol, as they are vertically misaligned on the combiner. See screenshot.

• g. Runway remaining value seems always to be in meters regardless of the selected unit.

• h. HUD is too bright on the dimmest setting. You should ideally be able to have the symbology very faint, barely visible as a ghost image. I’m guessing this could be a sim limitation though

• i. The MCP course set arrow often seems to not be aligned with the runway centerline. This is a problem if the localizer reference is going to be corrected. If the loc needle is correctly referenced to the course set arrow, then that has to be aligned with the centerline.

• j. I’ve noticed that sometimes the guidance cue is not centred even when the autopilot is on and the plane is perfectly following the flight guidance.

• Wheel Well Fire Warning
• v1.0.0 – Reference N1 indications
• Reverse Bug/Problem
• “25” bug should not show on flaps 30 landing
• Added ACP/ECP wake-up mode
• Flap manoeuvre speed incorrectly bugged
• Ok, tried an engine flameout tonight at
• MINS RADIO in -1000 after scrolling below 0 and then up
• LNAV issue with overfly waypoints
• Aileron Balance Tab Issue (more info)
• TO-B should not take selected temperatures
• The taxi lights and landing lights are sending inverted information to the simulator
  variables
• Key Binding seat belts off (move down) is missing
• Left Turn Holds Still Rendered Incorrectly
• VNAV PATH SPEED AT FLAPS 1
• Aircraft PLI
• VR View is Outside the Flight Deck
• Issues with path drawing
• Floating text in VCFloating text in VC
• MFD Option not working
• Speed brake Modeling
• In addition, AP has improved the logic of altitude capture during low-altitude N1
  climb. For example, if the aircraft is currently flying at 1000ft, and then selects
  2000ft, presses LVL CHG, the original gau will cause the aircraft to exceed the
  commanded altitude by hundreds of feet, but now it is controlled at around 100ft.
  If the aircraft is currently at 1000ft, select 3000ft, then it will not overshoot
  This is mainly because if the altitude difference is too low, the aircraft needs to
  switch to altitude hold mode while it is in the state of pulling up. It takes time for
  the aircraft to switch from the state of pulling up to the state of pushing the stick.
  That is, it takes time to switch from G>1.0 to G<1.0, and this time causes the
  aircraft to overshoot.
• Insufficient Fuel Message
• RW Slope entries at CDU
• A/T Acceleration Too Slow on TOGA
• VSD Black Box
• Icing Effect: Engine inlet cowls
• The LEGS page cannot input altitude until the cruise altitude is entered
• Custom Waypoint as SID
• No OFF SCHED DES Light
• A/T Slow to Add Thrust
• Supply Duct temperatures
• Speed brake Armed Light
• Thrust Lever Animation
• ILS frequency, course, and DME are not displayed on PFD until in range
• When ND is only displayed on the right side of the screen, the waypoint, MCP Alt,
  and DH altitude in the VSD area are not displayed.
• After the RTE2 route is ACTIVE, modifying any RTE2 data will cause the DEST
  airport data of RTE2 to be lost
• Problem with altitudes
• Autopilot Pitch authority
• RNAV Departure Incorrectly Parsed
• Icing effect: Windshield
• Controls Lockout As Default Setting
• Still having issues with path drawing
• GMAD OLOMA2A Arrival
• Flap Maneuver Speeds Bugged Incorrectly on T/O and G/A, V1.0
  typo in the circuit breakers
• Incorrect CDU RNP Entry Format
• VNAV SPD
• LIRP RNAV Z Rwy 22L Go Around Direction Drawing Incorrect
• ND Faulty LNAV Procedure Turn Drawing
• Autopilot Pitch Speed Control
• EGT on Cold Soak Start
• GCLP ILSX RW03L INCORRECT DRAWING
• Added new trim wheel sounds, slow vs fast sounds are different.
• Added a plus hundred callout sound.
• Added reverser lock “crack” sound about 2 seconds after touchdown.
• Reworked spoiler auto deploys sound and added spoiler auto stow sound.
• Added click for putting throttles to idle.
• Added cockpit rain sound.
• General balancing as per feedback in the discord server.
  Decreased Cockpit Electrical background whine sound.
• Fixed R1 Service Door missing open/close sound.
• Fixed Landing gear in Cabin not audible.
• VNAV approach flies Vref on final (does not take FMC wind correction into
  consideration)
• Incorrect EAI Behavior with Bleeds Off
• Battery Power Only
• VNAV path optimizations
• LOC Approach Navigation Source Reference
• [TAKEOFF] Engine N1 limit not adhered to
• TCAS – Missing message?
• Mach to IAS transition in descent
  

Read More in MSFS