This plane behaves in so many strange ways I don’t know where to to begin . Also can’t even turn off the cabin lights nowhere on this plane . Absolute disaster.
I keep getting a nosewheel and gear malfunction now as it seems that it thinks that the GSX tug has damaged it. The aircraft then won’t steer properly and needs ridiculous amounts of breakaway thrust. Asobo have simulated something but it’s not an aircraft and it’s not a 737. Just quit for the night. I’ll stick to Airbus for a while. The Fenix runs well and the ini A330 is not bad at all. I’ll wait for iFly before going back to the 737.
You lasted a couple more tries than I did. I gave up, went back to FS2020 and made 3 flawless flights in the iFly MAX instead. The casual simmer doesn’t need that level of cabin modeling and systems depth, but they do need something that flies at least generally as well.
1 Like
So, glutton for punishment that I am, I gave the MAX another chance. Unlike last time, I was actually able to make a full flight, but it was not without its (significant) challenges. I flew from FlyTampa’s KBOS to Drzewiecki’s KDCA. Both of these are 2020 Marketplace sceneries, streamed from the cloud. More on that later.
First, still no way that I can tell to call a ground power unit, so I had to start the APU on battery power, and then use that while I preflighted the plane. I tried to use the new FS2024 flight planner tool but there doesn’t seem to be any real equivalent of Simbrief’s profiles. Although the aircraft was able to be selected for the flight and I could get a route, I didn’t see any obvious or plain way to get the tool to give me any kind of planned fuel burn. After futzing with it for a few minutes I went back to Simbrief instead.
Second, on departure I was given a clearance direct to a waypoint that bypassed a big chunk of the planned climb out procedure. I put the direct to into the FMC but the plane didn’t recalculate the route. Instead it wanted to continue flying the entire SID. Since I was taking off into heavy clouds and icing conditions, I just followed the flight directors and didn’t try to fight the box.
Third, during the descent into DC, there are several hard altitude constraints. The plane managed the first (at 11,000’ I believe), then about 22 miles until another hard constraint (10,000’), then 8 miles to a third (also 10,000’), then several others heading onto the downwind for runway 01. The plane managed the 11,000’ fix, but was slow to descend for 10,000’ at the next fix. After that segment, it was very slow to descend in order to make a 7,000’ hard constraint later on. Admittedly, winds were pretty gnarly and so far as I can tell, there’s no way to import winds data into the FMC for this aircraft. Maybe the flight planner tool is supposed to do that?
Fourth, during cruise as I neared TOD, I looked up weather for DCA and wanted to preset the altimeter. Suddenly the MCP altimeter knobs didn’t work. They rotated left and right, but the set altitude could only be changed from 29.91 to 29.93. Further, pressing the MCP button would not switch between STD and local pressure. This was the same on both sides of the flight deck. Ironically, I had no trouble setting the altimeter on the standby instruments. Even keyboard shortcuts (which I verified in the controls menu to be sure I remembered right) would not toggle back to local pressure. Oddly, the minimums knob worked fine.
Fifth, at some point, my right mouse button stopped letting me free-look around the cockpit. WTH?
Sixth, although the FMC let me enter a fix, that fix and the range rings I defined were not displayed.
Seventh, upon landing, thrust reversers did not work. I was using the same controller profile I had been using with the 787-10 where those bindings do work, but the Max may be coded differently. This one may be on me. I don’t know yet for sure.
EDITED TO ADD ONE I FORGOT:
Eighth, during the take-off roll, I got a Master Caution for Air Conditioning. The packs were on, the bleeds were on, the APU valve closed and the isolation valve set to Auto, and the cruise altitude was set so I ignored it. During the climb, the Master Caution recurred several time. I turned each pack off and back on, set each one to High and back to Auto, closed and re-opened the isolation valve, whatever. The Master Caution kept going off. At no point did the Cabin Altitude exceed about 8,000’, and dP never exceeded about 8 psi. After all that, I finally just ignored it. About halfway through cruise it finally stopped going off.
During my descent into weather, alarmed that I couldn’t set local pressure (which was 29.64, so significantly different than standard), I went into the Controls settings again and set custom controls to increase and decrease the altimeter setting. That let me set the correct pressure. Then miraculously, having done that, the MCP button to toggle between local and standard started working again, as did my right-mouse button free-look.
Lastly, although my speedbrake control was bound to the first axis of my Boeing throttle quadrant, and moving the lever extended and retracted the spoilers in external view, the lever in the cockpit did not move. My throttles moved, but not the speedbrake lever. Again, WTH?
Anway, that’s the last I’ll be flying this one absent some real, intense development work.
NOTE RE SCENERY: I have loaded into both of these streamed 2020 Marketplace sceneries before today without issue. This afternoon, however, it took a solid 5-7 minutes for the scenery and local terrain to load in when I was attempting to start the flight. The runway textures and Boston coastal terrain never did really load in clearly in the world map. One I did select a gate to start from, it again took several minutes more for the aircraft and scenery to render in sufficient for me to start. Several times during the flight I received the low-bandwidth warning as well. None of this creates confidence in the streaming paradigm chosen for 2024, folks.
5 Likes
If you are trying to pre set them while set to ‘STD’ they don’t work. It’s another bug. Take it off of STD pressure and altimeter dial works. You just can’t pre-set it other than by +/- 00.01.
I had a fix show up, but couldn’t enter range rings either, it wouldn’t let me.
This is a bug. It’s been reported. You get this going off a lot during various stages of flight. The OHP has orange bleed warnings light up too.
The speedbrake arming has a weird (anomalous) set up. Just try setting it by mouse and you will see what I mean. I often have to try 5 times with the mouse just to arm the speedbrake. It’s approx 2-3 clicks towards you and then one click up to arm (the armed light will then come on). Bugged I think. I frequently switch to passenger cabin view during this process to have a look at the wing to make sure I haven’t accidentally deployed them. Lol.
Funny that you mention this. I just discovered today that engines/wings de-ice and window heat don’t actually do anything to de-frost/ice the aircraft. I had to take off at EGNM this morning iced up. With a de-rated T/O too. Lol.
I even tried a GSX de-ice first (I realized this is just a visual), but the de-icing in the Max wasn’t doing anything so short of jumping out in walk around mode with an ice scraper 
nothing was working.
Interestingly last night (UK time) I was trying to fly KPGA-> KPHX again, I had done it the day before with some streaming issues seen (but surely with some data cached from the previous flight too), but last night was insanely bad with blurry textures and a minecraft like look just about the whole way, scenery streaming in either too late or not at all. It was back to Nov 2024 streaming again with minimal server access. I think there must have been something happening with FS2024 servers over the weekend. Too many users again? I haven’t seen it this bad since late Nov/early Dec.
Asobo 737 Max Bugs/issues
I’m about 30 flights in with the Asobo Max. It is serviceable in it current state but I have a list of 28 bugs that I have to be aware of while using it. No way I’m doing 28 bug reports though. My current list of 737 max bugs are (some of them have been reported already) -
- Selection screen default is Business Jet config every time, no config/livery combination retained (why?)
- ALTITUDE DIAL increase should be to right decrease is should be to left currently wrong/opposite animation
- ALTITUDE DIAL no acceleration so slow (only 100ft increments!) in order to set target alt
- GROUND POWER shows as available but will not turn ON & does not result in power to aircraft, seems INOP
- SQUAWK code currently can not be set manually (except by using GTN750)
- VHF COM and NAV displays and OHP digital dispalys are tied to background illumination dials.
- No way into passenger virtual cabin as clicking on cockpit door take you outside aircraft
- Default brightness of both pilot and co-pilot PFD’s are too high as default. Night time brightness particularly bad.
- At various stages of flight the orange WARNING LIGHT for AIR CONDITIONING comes on with BLEED warning in OHP
- Autobrakes RTO does not disable after t/o
- ILS approach too much hunting/spooling of engines with pitch oscillations on approach
- Auto land not smooth/prone to nose dive/impact due to previous issue.
- Engine derate T/O setting when for example set to TO-2 changes CLB to CLB-2 (they should be independent).
- Perf Init screen will not accept cruise wind (just says invalid entry)
- No trip (cruise/descent) winds can be imported
- GSX pushback causes aircraft to porpoise. Front wheel lifts up and down in a wave like fashion
- Baro can’t be pre-set when on STD pressure (white text under STD) only up/down by 0.01 and no more
- Clock doesn’t change in proportion to sim rate increase
- Why do both CMD lights turn on when you engage AP CMD1 after takeoff should be separate
- APU start up sound only plays when APU gen then APU bleed is turned on
- MCP brightness of digital panels too low/uncontrollable for daylight use
- With transition alt set to 6000ft in the FMS it works on climb, but uses 18000ft transition alt on descent
- Speedbrake has dubious arming procedure requiring 3 clicks back then 1 click up quite tricky to arm
- VNAV descent ahead of TOD instead of going to -1000ft/min until VNAV path intercept, drops to -3000ft/min, meaning path can’t catch up. Have to use V/S at -1000ft/min instead until path catches up then hit VNAV and it will descend by VNAV PATH.
- Passenger cabin lighting on all the time & too bright at nighttime
- No way to control exterior doors eg via EFB
- Aircraft will not de-ice with engine/wing de-ice aircraft remains frosted (passenger)
- Aircraft will not de-ice window heaters won’t do anything aircraft remains frosted (passenger)
2 Likes
If this is Asobo’s response to detailed 737 MAX which was showcased prior to MSFS 2024 release then it is an absolute disappointment. The default 737 max is a joke, they have got even the basic things wrong. Anyone who has flown high fidelity airliners before PMDG/Fenix will find this plane absolutely appalling.
1 Like
Yeah well that didn’t work. I could not toggle it off STD in order to change it. Clicking the button on the MCP did not register, and the default 2024 keyboard shortcut ( comma - ; ) did not work. I even went into my keyboard settings and changed to the 2020 profile and tried the old standby (B) but that did not work. As I said in my post, the one thing that did work was to create new shortcuts to increase and decrease the altimeter setting. Once I did that and got the altimeter preset for my descent pressure, I was suddenly able to toggle STD off and back on again.
As for the rest, I’m not interested in faffing around with so very many fundamental bugs. Saturday I made a supremely satisfying 4.6 hour flight in FS2020 in the iFly MAX and experienced approximately zero bugs; and today I intend to fly the PMDG NG all day which, based on 2.5+ years of past experience, will also give me a great deal of satisfaction.
3 Likes
There’s certainly a knack to get that center baro button pressed. For the longest time I thought it wasn’t working. Left mouse click (&hold) and then right mouse click toggles the modes. Different from other aircraft I think. I’m just over on FS2024 full time now so will wait patiently for the NG and the 777 PMDGs to arrive over. Sounds like the 737 will be getting a nice (paid) upgrade too.
When did they say it was going to be this though? It isn’t an ‘Expert’ series.
I’d place it as somewhere above entry level, it needs some previous knowledge to set it up correctly. It would be more intermediate if it didn’t have so many bugs. The thing that lets it down are the 28 (that I have counted) bugs. Beyond that, sure it isn’t as in depth as a PMDG but who on earth thought it would be and why?
3 Likes
Let me add a few :
- The switch to choose between displaying VOR2 info, NDB2 info or nothing on the Captain’s rightmost screen has no effect, it always displays VOR2 info ;
- The toe brakes are quite weak ; it takes forever to speed down to exit speed after landing, even with a plane far from max weight ;
- The engines idle thrust is way too weak, a Max can start rolling at idle or (at worse) very low power ; but right now in game the plane won’t move with the engines below 30% N1, this is plain wrong.
I can work around these, and others (I have most of the issues the OP described), but the huge problem are the CG issues … the plane is almost uncontrollable in manual flying, because as soon as the thrust changes (manually or A/T), the pitch also does.
If there’s a magical procedure to set the weight / CG that can make it stable, I have not found it (and the terrible terrible EFB doesn’t help).
I get zero oil pressure when starting either engine 100% of the time. What am I missing ?
Agree
As a PC user，I will never fly the “default aircraft”. Asobo should provide the SDK and help the 3rd DEV . We have ifly 737max on 2020, not on 2024. Stop waste the time on the “default aircraft”
Hi @MayuyuYukirin99
FYI, the MSFS 2024 SDK is available for anyone to read & use online, here.
(It can also be downloaded for off-line use from within the game if you enable developer-mode).
Third-party developers can get support on a dedicated Developer Support Forum, here.