Thank you for the bug report.
We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.
Thanks very much. I have continued to follow the issue but have not done any more systematic work on it. Think the video speaks for itself. In local flights with the 787 on LNAV and altitude hold, the GS does seem to be captured properly when intercepted. Thus the capture issue seems to occur only when VNAV is on.
Confirmed! I switch from VNAV to Altitude Hold when G/S gets active on approach (or any time before it crosses the middle ācaptureā area) and G/S engages without fault. I hope they fix the VNAV bug though for completeness!
Thank you for the sanity check. As an instrument rated pilot that has done real single pilot IRF in the clouds, you have to keep workload to a minimum or you make mistakes. This should be automatic.
I can confirm the same issue on the 737 Max in carreer mode on PS5. The glide slope will not be catched, if you donāt disable VNAV manually.
Please add the 737 Max 8 (Standard plane) as tag to the topic and to the internal bug ticket.
Confirming adding the 737 to the Bug. It must be in all the Boeings then. People probably just do not notice it unless they try to make a smooth transition to the ILSā¦
It looks like it does capture the G/S, but the FMA doesnāt reflect the actual AP mode correctly as long as VNAV is enabled. Thanks for the video.
Yes it is weird, it does ācaptureā but the glide slope deviation does not show up. The VNAV deviation seems to trump the GS whereas it should be the other way around. I am sure it would be easy to fix if somebody just lay an eye on it. Overall they have done a fine job with this autopilot, which is one generation more advanced than the other Boeing APsā¦ look at what went into the Vertical Situation Displayā¦ this may have moved laterally to the 737 but I do not fly that bird.
The 787 Vertical Situation Display Human Factors Evaluation Enhan.pdf (584.7 KB)
I found another bug tied to this. The 737 Max also loses randomly a already captured glideslope which you already followed a bit on ps5. The 737 just cancels the approach mode at will. Does the 787 as well?
Same as the Cessna Citation longitude as written here: Cessna Citation Longitude: Autopilot loses track of already captured LOC and/or glideslope (PS5) - #5
So please report that issue too, if you notice this as well and please add your posts to the thread above. The ILS mechanics of some planes in this game need maintenance desperately.
Thanks. Will keep my eye opened. Generally do not lose the GS on the 787ā¦ that AP works 99% correctly.
My other go to plane is the C 210. VNAV is not really implemented on the 210 but I run it on many of the same flight plans as the 787.
I am not familiar with the Citation. The 210 has the Garmen GNS 530 and the 172 has the G1000. Have flow both of those in real lifeā¦ the dials are a real PITA. The dials in the sim are easier to use than real life unless you have tiny hands.
EDIT: C 210 works OK: I put the same flight plan from the 787 into the 210 that I have for a local airport (Moffit Field KNUQ) that is very close to SFO. Using the GNS 530 with their version of LNAV (NAV) setting the altitude to 3000ā and turning on APR (Approach mode) the aircraft transitioned perfectly from the NAV mode to the GS on the approach and went right down to the runway. All I had to do was set the throttle, drop the gear, set the flaps and cut the throttle (and flare).
So maybe it is just the Boeing AP. If I run the same FP in the 787 it will not make the transition and in fact you have to enter the ILS in the FP as Direct to get it to capture the GS. Thus the 787 does not move seamlessly to the ILS even if the ILS is on the flight plan in LNAV mode. So there is something deeper that is wrong with the AP implementation.
The mentioned citation longitude runs a G5000 (transitions correctly from VNAV to GS, but loses a captured LOC/GS randomly)
As for the mentioned bug: not sure if this happens on PC. I play on PS5 and had the issue today twice directly back to back in the 737 Max. Captured GS, followed it constantly for at least 30s, than app mode disabled by itself (LOC/GS un-captured). Turned it on again, got lost within 3 seconds again. Then a reenabled it again, but this time the LOC and GS kept captured.
Same for the VNAV to GS transition. It never works unless you donāt disable VNAV manually.
Well, IMHO the basic code base for all versions should be pretty similar. When I used to do programming I believe in MS Visual Studio you could use the same C++ code to be compiled for different platforms. I suspect you on the PS are probably finding things that exist on the XBOX, Steam and the PC but just not noticed because they are subtle. PC users have complained that the XBOX is the lowest common denominator and the code base is really designed to run on it. My condolences if you have a PS5, which I believe is probably better than the typical XBOX, so you are in the same boat as PC users that have hardware investments that are not really used to maximum benefit.
I have an old XBOX and still play COD WWII hence my gamer tag, but I am not sure it can run MSFS. I have never looked. I should look.
I should also try the 737 ?Maxā¦ is that the default version?
I guess 737 max (by Asobo) is in the default version. I have the premium deluxe version and the 737 Max is the cheapest Airline plane you can buy in career mode - so for me it is a logical choice to play with to make money.
We on PS5 have still an empty store, so itās not an addon vessel.
We on ps5 have constantly crashing and resetting avionics since a hotpatxh few days after ps5 release. Maybe our A/P losing track of a captured glideslope problems are a symptom ouf our constantly resetting/rebooting avionicsā¦ Maybe itās a problem of its own. We donāt know, as the avionics at all are extremly unstable on console right know.
OK, you have the default version. I bought the ?PMDG version of the 777 and was disappointed with the AP and programming. Very tedious. And you had to get into the Simbrief ecosystem, which I took to be a racket.
I remember at the start I flew the standard 737 (corporate) but went with the 787 because the AP was simpler and more reliable. Iāll see if I can get it to work today and we have a Holiday tomorrow. I checked Google and did not see any IFR tutorials so i guess it will be general knowledge with this one.
I have a standard flight plan from Reno to KSFO that hits all relevant IFR components and that loads into the C-210 fine. Iāll see what happens with the 737.
FYI this is the FP:
There are two things to do in the CDU before T/O:
There is a funny dance you have to do with the AP to get VNAV to step down correctly. You need to climb to a cruise altitude with at least one fix at cruise and then VNAV will let down correctly in this case to 4000ā for the start of the ILSā¦ that is where the GS capture fails and you have to load the ILS Direct to finish the approach. 4000ā comes in UNDER the GS at the initial fix.
EDIT:
So I flew the Reno-SFO flight and the AP in the 737 needs even more work than the 787. I could get it out of RENO and to do the VNAV descent but it did not pick up the GS ever even by manually putting in the ILS and hitting APRā¦ had to manually land the plane. Also speed control seems pretty non-existent or folkloric. Remember why I went with the 787. For those of you using the Asobo 737 my condolencesā¦ maybe the PMDG? one if up to standards.
Another autopilot issue found today (737 Max 8, by Asobo). I had edited some altitude values in the autogenerated flightplan in the fms and flew to the destination (Istanbul). There were no discontinuities in the plan, because I cleaned them all. But: This time the flight computer did not calculate any T/D-Point and thus did not start to descent upon reaching the destination. It just ignored all altitude values from the flightplan (point was set to AT 6000). It stayed on FL420. VNAV was on and the button lit up.
As the avionics crashed (see other actual thread) several times during flight (I play on ps5) it might have to do with this. I observed ot today the first time. And no, the fms was set up correctly.
Yes the T/D point is also a black science for the 787. By trial and error I have discovered that you need a point in the FP that is definitely at the cruise altitude BEFORE you come up on the calculated T/D point. In the 787 you need to enter the cruise altitude into the CDU and you need to climb there. I messed with this a lot by trial and error and I just from a flight from LAX to SFO where this worked but I had to have a lower altitude that I might have normally had 16000 versus 35000. Too hard for them to make a manual. The 787 manuals from Boeing are unreadable too.