Thanks very very much. Will do all this today and report back. I have the day off.
I was unable to find your cheat sheet or videos that are relevant. This should be doable.
There was a poor soul on Redid this AM whose 737 suddenly crashed in career modes and he was almost in tears…
I have had consistent success using following this recommendation. I am flying 737 in career mode and it is working ok. ALT-N straight to taxi avoids the crashes with ground equipment as well. Now I just need to figure out the formula for recovering the 737 when you ALT-N to descent. atm, it is spawning the plane with chronic low airspeed, crazy trim setting and it often goes into a nose-dive. Apart from that it’s great 
As a side note / tip: If you do manage to wrestle the 737 back under control after ALT-N to descent you’ll often find yourself too close to the airport with too much altitude. I have got used to this and I basically fly a heading away from the destination while descending to a manageable altitude before sending an abbreviated flight plan from EFB to avionics. Then I just use LNAV / VNAV to fly to the beginning of the approach and this normally works out fine. I haven’t had any issues using ILS or RNAV approaches with the 737 max doing this.
Wish me luck. Am at the departure end of the runway in Fresno with everything cranked in. Beautiful day in California.
Just be wary of the AP on final. It’s not the smoothest GS hold in this 737. The engines spool up and down (hunting) a lot on GS and it over/undershoots as it does so. So it may be better to manually land from 500-1000ft. Also be aware that AP switches CMD1 and CMD2 have a habit of both being engaged as default during flight, which arms the auto land feature. But the Asobo 737 Max isn’t IMO up for autolands yet due to that engine hunting/spooling aircraft porpoising on final. So just something to look out for.
Exactly, as they say in aviation, any landing you walk away from was a good landing.
It was hunting and searching on the autoland. The 787 is much smoother. BUT IT WORKED.
It may have to do with the target speed. There were defaults in the AP and I did not change them. I saw the little A came up in the speed indication as did the PULL UP warning but I cranked in a little speed and landed at about 155 knots full flaps.
FPS was a remarkable 100 in the air going to SFO but again stuttered on landing whne it hit the textures of the runway.
VRAM was 5.5 GB when in the air but went to 7 on landing and that is when my poor 3070ti goes virtual.
This is a terrible bug and shows total lack of programming skill… I speak as someone with years of experience and who has actually written flight simulation code. This gets the people with better cards too since they seem to load in everything then can in the air and when the plane gets close to the runway there is more texture and surprise VRAM fills up… I just find this lack of insight amazing.
Anyway, maybe this will improve with the caching, but frankly I have no confidence in the crew in charge here.
Thanks everyone for the help getting me into the 737.
One last note on my second flight with full AP the autoland worked Ok with 40 DEG flaps at 155 knots.
Yet the FPS cranked to a halt at 7-10 and I think I give up for the time being. IMHO, harder to master the AP than the 787 and the same VRAM issues… need to get a better card than my 3070ti but not sure that is full insurance.
