737 MFD looses MAP view capability on MFD on longer flights

[ZielonyLDZ]

ISSUE DESCRIPTION

Dear Team,

I am facing reoccuring problem with Asobo 737 MAX 8. Description of the issue: 737 looses MAP capability on MFD during longer flights. The PLN screen shows everything that should be there (including descent deviation), the only missing element is lack of magenta plotted course and waypoints. Instead of waypoints, yellow label MAP is presented. At the same time, INIT > POS menu on page 2 shows different positions between IRS and GPS. Upon landing and turning both IRS knobs OFF and back to NAV caused both MFD’s (PF and PM) to become unavailable in MAP mode. Turning power off in the plane did not reset status, FCU keeps all the previously programmed details (inluding invalid position).

Let me know if I any additional details might be required.

Kind regards, Z

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)? Each time I do a longer flight (>3h)

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

1. Select Boeing 737 MAX 8 in free flight mode

2. After ~3h of flight, left PFD in MAP mode will loose magenta path line and show yellow MAP label

3. Ater landing, cycling IRS OFF and ON causes both MFD’s to become unavailable in MAP mode and FCU shows invalid coordinates.

YOUR SETTINGS

Base PS5, Digital Deluxe version MSFS2024, controls via Dualsense joypad, Logitech MX Master3S mouse and MX Keys Mini keyboard.

MEDIA

Left MFD went off, showing only “MAP” in MAP mode, right MFD worked corectly in all modes:

IRS status mid flight:

FCU status mid flight. Coordinates on PF FCU and PM FCU are identical. Right MFD works in MAP mode, left one shows only yellow MAP (this is close up on FCU’s, screenshot taken at the same time first screenshot above was taken).

Status after landing and cycling IRS OFF and back to NAV. The position between L and R IRS/GPS is no longer coherent, right MFD stopped working in MAP mode as well:

Edit: Different flight, same behavior. At around 3h into the flight, IRS R and GPS L positions became frozen, causing left MFD to stop working in MAP mode. Video demonstrates position readings frozen, MFD showing yellow [MAP] and flight time.

Microsoft Flight Simulator 2024_20260304162828

[ZielonyLDZ]

Another thing I have noticed, which probably is the culprit of the problem. Upon initialization, when IRS is still aligning, POS INIT page instead of showing position on GPS L and GPS R (as IRS L and R are still aligning), it shows position on IRS L and GPS R.

Conclusion - current value of variable IRS L seems to be assigned incorrectly, the current value should be mapped to GPS L.

[MacinkoRedcell]

Does any one encounter the issue that IRS alignment not completes on 2024 Xbox?

[GrimReaper68469]

Same here, many times in the flight MFD shows that. But I had it in the airbus family too.

[ZielonyLDZ]

What you show is different issue. Your nav mode works as expected - you can see the magenta line. Instead your PFD is not showing correct data. Is this permanent or it goes back to displaying everything in couple seconds?

[Arzgebirg1679]

This is tied to the avionics crashes…. Sometimes the map crashes during flight and sometimes it does not come back. Same for the pfd.

[ZielonyLDZ]

I have been flying, until one point, solely 737. PFD did not fail permanently, as in the screen shared, not even once (on PS5). It was doing it from time to time, but it was always going back to normal state after few seconds. It was not the case with MFD, which was failing permanently around hour 3 of the flight.

[GrimReaper68469]

I had the INS align lit up when I had those on the display, but maybe you’re right, it’s different from the bug told above.

[Arzgebirg1679]

I had longer flights (London to dubai) with the 737 max 8. At some point even the pfd does not come back after crashing (staying in alignment mode) as the map display. So the longer the flight, the higher the risk that some display that crashes may not come back to usability. For me this is the same issue like the ever crashing other glass cockpits (g1000, 3000, 5000, etc.)