Are there also variables for the Mode Selector? I’m especially interested in the NAV button because triggering the standard sim event will not catch the glideslope in an ILS approach, it only engages the localizer.
My GNS530 is on VLOC and I have the correct frequency tuned (otherwise it would not find the localizer). Everything works fine and GS is catched if I press NAV on the Mode Selector using the mouse.
So, you say, I need to trigger APR and then NAV? Triggering APR only doesn’t do anything.
I am not flying the GNS530 variant. I flyGTN750NXi.
However, Those are standard sim variables in order to catch GS, APR must be activated. So more than likely with the CDI in VLOC pressing NAV in the virtual cockpit is issuing AP_APR_HOLD.
The VS can be manipulated in almost any autopilot by binding it to ALT ref increase/decrease buttons in the regular setup. Usually works fine once armed in the AP, even on the old Beech 18 Speery AP.
Anyway, you were right. Although the 400B has no APR button, triggering the APR standard event works, it engages NAV, the localizer and the glideslope. I had some glitches in my code when I first tried this.
I think flying VOR/NDB is today most challenging and the workload is crazy. But why not, if you like it so… that, surely makes you a better navigator than pilots that never used VOR or NDB for navigation.
you should, however start to dig into GNSS navigation, and use them both.
For example, a virtual pilot in General aviation will mostly never use VORs for RNAV backup, because it alway works in sim. But in reality a clever pilot will always crosscheck the GNSS position with VOR or put it in background in case GNSS malfunctioned.