this is a new issue for me and it used to work just fine.
I just set up my new Honeycomb throttle quadrant bravo and have the latest MSFS and the latest Windows 10.
Glide slope comes on white but is not intercepted when I press APR on AP. Aircraft remains at its altitude and does not descent unless I descent using VS.
1 Like
Not enough information.
Aircraft type?
Avionics is stock or Working Title?
Are you at or below the the altitude fix at the FAF with a three degree glideslope?
Some GS/GP require you to continue past the FAF with a three degree GS descent until actual capture, which could be past the FAF and as close as 2nm to the threshold.
Also which approach are you trying? If it has a waypoint between the FAF and the runway it’s bugged and won’t capture until that waypoint.
It depends on the aircraft. If you’re using A32NX Development version, they currently don’t have VNAV function implemented yet, so it can’t automatically descent on an RNAV approach with V/DEV guidance.
What I usually do is once I reach the descent point according to the charts. I switched to FPA/TRK mode and I set my descent profile to follow whatever it is on the charts. If it’s 3 degrees, then -3 degrees. If it’s 3.5 degrees, then I set -3.5 degrees.
Chances are, as you descend, you can fine tune your descent angle to follow the V/DEV indicator until you’re comfortable enough to disengage AP and handfly the aircraft down the runway.
1 Like
I use everything stock and this is happening with the Daher TBM 930.
I know how the AP and GS works and it just started not working when I added the Honeycomb Bravo. Maybe a coincident.
It has always worked as long as I am under the Glidepath. The diamond comes down, it intercepts and then it works all the way to the ground. Except at the very end where it is usually too low. Just a bug I assume since it needs to go to the touchdown zone.
RNAV 7 SBA
Used it many times before
I use everything stock and this is happening with the Daher TBM 930.
I know how the AP and GS works and it just started not working when I added the Honeycomb Bravo. Maybe a coincident.
It has always worked as long as I am under the Glidepath. The diamond comes down, it intercepts and then it works all the way to the ground. Except at the very end where it is usually too low. Just a bug I assume since it needs to go to the touchdown zone.
I would say you need to consider using the Working Title G3000 which will eventually become part of the core sim post. There are many improvements therein including procedure legs and IAPs.
The magenta diamond can be inaccurate. The reason I recommend the Working Title G3000 is they implemented the Flight Path Marker/Velocity Vector. As long as the VV is steady over the runway piano keys, you are indeed going to make the runway and have a three degree glideslope. If it starts to waver then you know you need to adjust power.
Can you tell me how to use the working title G3000?
“Working Title G3000 - Intro” Working Title G3000 - Intro
Follow the instructions listed. Make sure you are using the folder as explicitly referenced in the instructions. Many first time users drag the higher level folder into the Community folder which won’t enable the Mod.
Great improvements include synthetic vision, wind indication/speed, height obstruction warning scale, Traffic Avoidance warnings and many others. This is also the first Garmin mod in the sim to include advisory VNAV.
I would forgo the road data for now, you can download if you like, but it can complicate things until you get used to the new features.
An RNAV approach is not a precision approach, it’s not designed to “go to the touchdown zone” or “all the way to the ground”. You’re supposed to be visual at minimums (–> charts) and then fly the rest manually.
1 Like
You are missing the point
What I’ve found with some RNAV approaches is that the IAF is far closer to the runway than the approach plate would have you expect. Yes the glidepath turns white but the bug remains quite small. If you manually descend from the published IAF you will probably find that after 0.5 to 1 mile the bug suddenly seems to activate properly, gets larger and will eventually capture. I think it’s just not terribly accurate in some locations.
There are different variations of RNAV approaches, just like there are variations in radio-based approaches (VOR vs LOC vs ILS). The ILS-like WAAS approach in the US is called LPV (localizer performance with vertical guidance). It gives you a glidepath like an ILS would, though technically it’s not a “precision” approach it will also get you down to 200 AGL usually. Though, these are very hit-or-miss in MSFS right now. Sometimes I don’t get guidance until 1 mile out, like @Dalwhat describes.
Some other variations of RNAV approaches are the WAAS LP (localizer performance, which is precise lateral guidance only), GPS LNAV (lateral navigation only but less precise), LNAV/VNAV (lateral guidance with vertical navigation; VNAV mostly does not work in MSFS except for in some mods).
Anyway, basically YMMV right now with RNAV approaches. If it happens to be an LPV approach, sometimes you’ll get a proper glidepath but it’s pretty random in my experience. Look up the approach plate via the FAA if you’re flying the US and check the bottom to see which types of RNAV approaches are actually available. How it should work is that your avionics tell you which approach it’s using, e.g. LPV vs LNAV/VNAV vs LNAV based on its current abilities. Unfortunately the Garmins don’t show that info like they would in the real thing.
The most trusty is still the ILS if you want vertical guidance.
I agree with AviatorFB that most replies seem to be missing the point. I have been flying both the TBM and Grand Caravan with a route and approach loaded and active for quite a while now with a Bravo Throttle and had no problems with it picking up the glide slope. However, after the latest World Update it has stopped working. I have tried it on several airports where it has worked in the past but the aircraft apparently picks up the glide slope but then ignores it and flys on into the distance.
I get your point and I didn’t mean that, that’s why I quoted the other parts. The RNAV implementation by Asobo is an interesting variation anyway but I haven’t noticed what you describe above. I’ll try KSBA.
I approached NAPPS at 1800’, appr (FMS and GP) armed and it displayed the magenta diamond in the center. shortly before the FAF (NAPPS) it jumped up and then captured normally. Everything displayed before NAPPS is nonsense but that’s how it works in the sim atm. Be at the altitude of the FAF and it will capture the glide path.
Mine used to work perfectly too until a few days ago.
The only thing different, for me, is the new update and new honeycomb bravo.
Capturing the glidepath on RNAV approaches has been an issue since the beginning. Several topics on this matter. No word that I have seen from MSFT about improving the overall IFR experience.
I’m new at this and still learning. What is a FAF? Thanks