That’s not Airbus
I want to bump this because there have been a plethora of updates and none of the issues have been addressed - the game has been out almost four months too
SU1 changelog:
Boeing 737 MAX 8
- Fixed CLB derate logic to be in accordance with the FCOM
- CLB 1 and CLB 2 derate modes now revert to CLB when the derate fades out at high altitude
- Fixed an issue where CDU2 would be blank when spawning on the runway
- Fixed TAKEOFF SPEEDS DELETED sometimes showing incorrectly when spawning on the runway
- Fixed ident page navigation database dates
- Added LDG ALT flag on PFD and improved landing altitude logic
- Removed landing altitude from HUD altitude tape
- Now targetting +0.1 psid cabin pressure differential during takeoff
- Takeoff prepressurization only happens if the engines are running and bleed air is available now
- Removed altitude trend vector from PFD
Crazy how there is still no working lights on the BBJ variant
After a uneventful two hours, descending vnav and lnav path it went berserk over London, rolling and pitching upside down.
21 HOURS and it needs new engines! OMFG. I just checked and fixed the landing gear and Ground contact at the beginning of the flight from Iceland to FLA, and both engines flame out over Norther FLA.
Top tier insurance that just hit me with a $1.3 Million bill, didn’t pay a cent. The flight controls are $22 Million just to maintain I guess, because in 21 hours, no accidents or rough landings they must be made out of Balsa wood or something.
What collection of clowns designed this game? Not one aspect of it isn’t broken. I got restricted air space while standing in front of the plane before pre-flight inspection. What AirSpace?
Can you imagine being a manager at Asobo, or MS FS division? It must look like a kindergarten class. I’m not one to criticize people doing complicated work, but I just cannot fathom how many idiots much be in a continuous chain, when it comes to the development and implementation of this game.
I imagine a board meeting had to go like;
“well, we’re months behind, and due to dozens of people who completely pooped the bed, the game has no hope of being a sell-able product. Therefore the only choice we have, without a total firesale, is to stitch it together enough that it works 51% of the time for 51% of the customers, and then work on damage control non-stop and keep the boat afloat with sales income, and say a Hail Mary that we can get by without a class action bankrupting the whole division”
you spawned on a military airfield, at a guess. the game certainly does not check for those before assigning them as departure or arrival destinations, but it will happily ding you for flying into their prohibited airspace.
SU2 changelog:
Boeing 737 MAX 8
- Control surfaces are heavier when facing hydraulic failure
- Heat FXs from engines are now correctly linked to the good engine and not controlled by the behavior of left engine only
- Fix altitude warning playing in cold & dark
- Modified radio knob tooltips to show the current standby frequency
- corrected the name of the Sun Express livery for the aircraft selection
- Fixed flight and landing altitude knob animations
- Fix pilot camera position
- Fixed altitude knob animation
- Added automatic lighting adjustment on spawn to better match the ambient lighting
- Fixed overhead and pedestal screens that were incorectly tied to their section light potentiometer
- Adjusted automatic brightness curve for some screens that were hardly readable under some weather/light conditions
- Fixed XPDR not receiving inputs
- Added Livery SunExpress on 737
- Debugged Livery Korean Air on 737
- Debugged Commercial Static 03 on 737
- Fixed GPU not turning on plane when battery is off
- Fixed avionics fans sound playing at the wrong time
- Fixed an issue on the 737 that prevented its deice system to work properly
- Fixed screens and some avionics powering on when they shouldn’t in cold & dark
- Updated hydraulic system configuration and FLTs to fix low hydraulic fluid readings.
- Fixed external HUD max indicated airspeed to fix the missing crash condition if maximum speed KIAS is exceeded.
- Fixed Transponder button animation
- Added missing lines on MFD/EFIS knobs
- VFX added to B737 to simulate snow blowed by engines when turned in Reverse mode.
- Fixed Left ADF mode knob
- Added new official liveries ( S7 Airlines, Qatar Airways, Alaska Airlines )
- Fixed a few bugs on existing liveries.
- Improved the base plane textures.
- Fixed LNAV & VNAV armed indicators
so, a preponderance of graphical fixes, a couple of system fixes (underlined). I believe the kids used to say, “weak”.
Missing
Fixed the Stab-Trim from turning the 80 ton airliner into a veritable ping pong ball and porpoising at the rate of a paint shaker, at any increase in sim-rate.
SMH
This aircraft is behaving weird in career mode passenger missions. I did 2 missions and things worked fine but the autopilot seems to be slow to catchup to what it needs to do.
However in my 3rd mission flying to Sydney when I slowed down and applied flaps, the display kept showing flaps 5 and so I pushed the controller button multiple times and got a ding for flap overspeed. So I looked at the flaps and it was at 40 while the monitor was stuck at 5.
Next after acquiring the GS suddenly the AP decided not to descent. Also I started getting stall warnings while ACMD and AT were engaged. By then my controller throttle inputs were not working either. So I had to manually push the throttle levers with mouse. Somehow managed to land it manually after a go-around almost stalling before reaching the runway 16R. Got a B rating which should have been D.
I fly this as employee so this would not be maintenance issue. The career mode really needs fixing.
I have found that the 737 Max is not flyable in Career Mode. Add to that the bugs in the sequence of pre-flight operations presented by the sim.
I have been flying the 737 Max in Free Flight mode and very satisfied with it’s performance. VNAV being the only function I have not had sucess with. But in Career Mode the last several missions I attempted, many things did not go right. Among others:
- In NO case could I get the autopilot to engage correctly while in Career Mode. Doing everything the same in Free Flight, it works just fine.
- A flight plan would not load correctly from EFB to avionics.
Destination missing and I could not manually enter destination. - Total loss of joystick control in manual flight mode just after take off. Happened two or three times.
4 . ATC directing me to 5000 ft as I approached a 10000 ft mountain in the flight plan path.
I have flown the 737 Max in career mode for quite some time but recently I am into helicopters. Just did a flight today to check the latest state. Here is my take:
Autopilot seems to work correctly as expected. Both LNAV and VNAV working along with RNAV and ILS approaches. Just check your trim settings before take-off. If it is nose down too much and you are pulling on the yoke after take-off and trying to engage autopilot, it will not engage. In free flight the default trim settings is more neutral while in career mode it seems to me a bit nose down.
LNAV I normally set before take-off and it automatically engages - if not I use heading to manually help the GPS acquisition and it automatically switches to LNAV afterwards.
VNAV works as planned for me but risky to use in career mode - the ATC does not understand altitudes and I agree with your point no.4
The flight plan I check before accepting the mission. I have never got destination missing and it correctly ports over to the avionics for me so far. But I don’t touch the given flight plan except setting altitudes and file to ATC. The approach procedures sometimes get changed by ATC on the fly and I re-plan it on the MCDU accordingly. I have had trouble if I changed approach procedures or runways so I don’t touch it at all.
Today I had 2 new issues however.
-
Ran into mountainous terrain and wanted to ask ATC for altitude increase but the ATC window went blank:
-
Did a smooth landing but got dinged for max fps at touchdown exceeded. Not sure if it is me or if there is a bug. Happening to me for most of the landings now on the 737.
Also the usual issue of going past the first exit after landing gives dings for entering taxiway without announcing and since the rest of the runway is considered taxiway I get taxi speeding as well while trying to slow down after landing.
If I look at the ratings, respect aircraft condition is 97% while ding on landing smoothness - a bit incongruent.
And what does passenger satisfaction depend on? Could not figure out. May be the food was not good.
After the latest update, I don’t know which, the max in career mode has a defective autopilot and maybe some energy management. In VNAV and LVL CHG it will not obey to the speed restriction, and it will usually not climb anymore than 13-14000ft without nudging it with V/S. At the moment it is just barely climbing at 314 kts (set at 300 according to VNAV profile). Absolutely hopeless. And no, I am not going thru hoops to troubleshoot this, I’m just going to say career is broken at this stage. They haven’t even fixed the pc12 pressure bug, and now new bugs keep emerging.
300 is very high speed for climbing. I normally keep below 250 for the climb. Also are you manually setting the max altitude that you want to climb to by turning the altitude knob before engaging VNAV?
I normally don’t use VNAV in career mode as ATC asks for different altitudes and speed restrictions and when they don’t match the VNAV profile then it has to be done with manual speed override and level change mode anyway.
Hi, I usually use LVL CHG before FL100 to avoid getting spanked by ATC, sometimes I use it all the way to T/C. Yes, I set the altitude on the AP panel, also in the FMC INIT PERF page and press exec (the FMC first). This has worked flawlessly before. Now the speed set in LVL CHG is not respected, and the plane is not climbing. I’m not able to get the plane up to cruise speed at all. Flaps are retracted, as are landing gear.
Emptied the community folder now, and am currently trying the second career flight with the Max, from Basel. First one it crashed just when the engines were spooling up on the rwy. Second one I’m currently climbing away at LVL CHG, set at 250 kts. But it does not seem to heed the speed setting, it’s climbing at 269 ts. N1 button on AP panel is lit, Speed button does not do anything. I haven’t had to press any previously, speed button seems to be lit randomly/I’m not sure when.
Did you try to control speed thru the CLB page on the FMS? Or via other FMS means?
No, but I think I found the problem. Although all flight controls seemed normal, including spoilers, flaps etc and everything that could degrade performance, the ac was not climbing properly. So I had an inflight external inspection of the flight surfaces, and alas the spoilers were somewhat lifted. The speed brake handle was in the down (upmost) position, but after cycling it performance was regained for a few seconds, and spoilers were down. But they went up again after a while. So I had a look at the controls setup, and there it was, some control axis on the stick was assigned to the spoilers. God knows how that happened, but I guess it has to be user error. Sorry, and thanks for the input.

Did a smooth landing but got dinged for max fps at touchdown exceeded. Not sure if it is me or if there is a bug. Happening to me for most of the landings now on the 737.
Yeah, the “max fps exceeded” bug at touchdown is hunting me, too. Nothing seem to help. This happened to me on all ILS approaches (FMS calculated landing configuration, e.g. 30°/133 kts, SB armed, fully on LOC & GS).
It’s especially frustrating to get a reputation penalty, after dragging oneself through a 7h (in-game time ≈ 1 ¾ h real-life, max sim rate is 4x, anything beyond let’s the AP trimming go crazy, causing uncontrollable “shaking”) flight.
On top, I usually have to GA, because the FMS always gets the wrong IAS alt, not catching the GS on the first try. Then the ATC throws a tantrum after declaring missed approach, publishing it, selecting new approach, suddenly the acknowledgement button vanishes, causing another penalty for “missed ATC communication”).