Well, I could not control myself and decided to try to fly the 737 from Reno to San Francisco, my milk run. Fixed the lighting and loaded in my 787 flight plan and edited the discontinuities OK.
Was very hard to use the autopilot. Not sure if it was me (most likely) or if it was buggy. I tried to look at a couple videos and they were of little help, had to hunt and peck and never got LNAV or VNAV to work. Used HDG Select and Level change to get to SFO. ILS/GS did not work. Do I have to hand enter the frequencies? Anyway, could land it by hand.
To good news was the the FPS were better than with the 787. I have to see what VRAM it uses. Still had some stutter when it hit the runway textures.
Thanks for the encouragement. I think this aircraft is flyable in present shape, probably better than the 787 when I get the AP nailed.
Hi, was just about to put 2024 up on the shelf as had problems with my goto airliner (787) and is worse than in 2020. Decided to try the 737 and had a few problems with the AP. Are there serious problems with the AP?
@A68yoSniper I’ve moved your question (plus responses) to a new thread in User Support Hub > Aircraft & Systems to avoid the main discussion thread going off track, and to give more space for your troubleshooting.
I don’t believe the PMDG 737 is currently compatible with MSFS 2024 at all, so if you’re trying to use it in 24, there’s no telling what might not work. Probably many things.
The autoflight system all works very well in 2020, though. Not perfect, but no sim airplane ever is.
Yeah, the PMDG line is not currently compatible with FS2024 and won’t be for weeks or months yet, likely. You can get the 737 to load though when I’ve tried it, I had a bunch of trouble that made me realize if I got it into the air, it wouldn’t be a good experience. I stick to FS2020 for my Boeing airliner flying.
If you’re still having these problems in FS2020, then I would suggest you find the 737 Tutorial document on PMDG’s site and make that flight.
Thanks, this is the Asobo 737 that comes with MSFS 2024.
I got the Asobo 787 eventually to work but with my 3070ti it stutters on the runway (runway texture) and I find it disagreeable. I was hoping the 737 might be simpler and work better in terms of FPS/VRAM.
I seem to have most of the AP working now. Am using a simpler flight plan from Fresno to SFO. This is created with the flight planning page and seems to import the VNAV settings except for altitude, which I can manually enter. See the nice intermediate altitude of 7000’ for ARCHI IAF.
Looking grim, mode buttons do not seem to work either. Seems the frequencies LEDs are not lit up but they do show a frequency… dimly. Tried both sides… pilot side hard to see.
All the numeric VHF dials lighting are tied to the main panel backlighting dial to the bottom left of the console. So just turn it to the max to see the numeric frequencies lit up They shouldn’t be controlled this way, so it’s a bug. Same goes for all the numeric dials in the OHP tied to backlighting dial up there.
The arrow in you VHF pic is pointing to the VHF COM radio stack. The ILS get entered into the NAV 1 to the bottom of that same picture.
I have a quick start guide for the max if you want to compare your set up with how it should all work. It is the one called “Asobo B38M Quick Start Guide-v1-0-2.txt” on my Google drive
The Asobo max is flyable, but it has quite a few bugs in it (I’ve counted about 20) but I’ve flown it a lot recently.
The LED’s aren’t very bright, for sure.
The one you have the arrow to is the Nav 2 radio, ILS should use Nav 1 on the pilot’s side, but either way, clicking the up or down ^ should cycle between these:
The button indicated should turn the frequencies I would think, but when the mouse is held over it it says: frequency selector but it does not select nor does the swap button work.
It looks like this is a real bug and is a fatal flaw.
Think I will fly the flight and see if the VNAV switches over to the ILS frequency… humm wonder if VNAV overrides this control.
Well, I took it into SFO and the VNA worked for the firs step down but not beyond that. Remarkably the ILS LOC work but not the GS.
The FPS was worse than the 787 so looks like this is a double exercise in frustration.
Thanks for the help but looks like the Asobo 737 has fatal flaws, yet seems like they would be correctable since they have their 787 working.
I guess I can file this officially as a bug? Its official:
No 737 automatically tunes radios. You’ll be waiting a long time for this to happen .
From what I’ve read, the Asobo Max is a complete mess. If you want a properly working 737, you’re better off with either the iFly Max or the PMDG NG in MSFS 2020.
The red arrow in your image is pointing at a COM VHF stack, not a NAV one. The NAV frequencies are entered in the panel above that red arrow where it says NAV and ILS.
You swap those frequencies from standby to active by using the left most up/down arrow switch. They work, I use them regularly.
If you are struggling to get LNAV and VNAV working follow my guide I posted earlier. You need to enter performace data into the FMS too.
The Max has some bugs and issues but you can still fly it. After 20-30 flights in it I can say that LNAV isnt one of the bugs. VNAV on the other hand works under certain situations and not others.
Yeah, I corrected my shot to the NAV radios after a bit but they still would not change. VNAV is so complex it is hard to eliminate user error. Where do I find you user’s guide so I can give it a better shot?
I am worried about the VRAM situation and if it is managed poorly in this plane probably should not put much time in as I prefer the 787, which I understand pretty well and self-populates most VNAV settings from the flight plan site, except for the altitude.
It is late, but I will see if it gets from fresno to SFO and does the ILS… with GS.
So far so good 1/2 way to SFO all the altitudes set in VNAV with defaults from the web based flight planner. Running at 60 FPS. See how long that lasts. Some stutters on takeoff runway.
First off you have ILS frequency for 28R 111.7 correct, but you only have it dialed in to NAV2 on the RH panel. I generally have ILS frequency dialed into and active on both NAV1 and NAV2
Secondly both the course dials on the MCP should be set to runway heading : 284 degrees
Thirdly you need to go to FMC → INIT REF → INDEX → APPROACH
and copy and paste your landing config (flaps/speed) into the FLAP/SPD field. This will set up your VREFS.
.
