Kakugo

Hi, when using the GTN with the JustFlight Turbo Arrow, which has no HSI but a simple DG, logic dictates that the HSI-related options should be off and one should enable "Connect GPS to VOR1 indicator". This works fine but the problem is that this also replaces the DME distance for NAV1 with the distance to the next waypoint, if the GTN CDI is set to GPS. I saw that this is a known issue since years, and I was wondering if there is any hope to have the DME distance indicating the actual distance to the station tuned on NAV1 irrespective of the CDI setting.

I can only say that I have an AMD CPU and I had the issue, so it's unlikely it's related to the Alder Lake architecture.

If you buy a navdata update from Jeppesen, you can download it on a PC using Jeppesen Distribution Manager, and you'll find it in a tarball somewhere under C:\ProgramData\Jeppesen\Jdm\jdmcache (if I remember correctly). You don't need a Skybound G2 USB adapter (I don't have one).

I reverted to W10 and don't plan to retry with W11 any time soon, but I'm sure that I didn't enable game mode and I didn't change the HAGS setting, so I had the default, whatever it is. On the other hand, on W10 I have HAGS ON and it doesn't create any issue. I vaguely remember that I had even played with the Windows compatibility mode on the trainer exe file and gave it a high priority in the task manager while it was running, but I wasn't systematic about it. What I'm sure of if that nothing I did helped. Maybe something worth trying, it could be that I didn't do it properly.

Ignoring for a moment that buying a recent obstacles database is not particularly useful for IFR training, I was wondering if anybody had any experience with doing it from the Garmin web site (without owning any Garmin hardware)...

It worked beautifully, now the vertical deviation indicator works perfectly for both ILS and LPV approaches!

I'm trying to familiarize myself with the aircraft definition, but it will take time... For the moment I found this piece of code in an *.obj file: ANIM_begin ANIM_trans_begin sim/cockpit2/radios/indicators/hsi_vdef_dots_pilot ANIM_trans_key 0 -0.24516 0.16553 -0.30094001 ANIM_trans_key 2 -0.24516 0.15153 -0.30094001 ANIM_trans_key 3 -0.24516 0.15153 -0.30094001 ANIM_trans_key -2 -0.24516 0.17952999 -0.30094001 ANIM_trans_key -3 -0.24516 0.17952999 -0.30094001 ANIM_trans_end ANIM_hide 0 0 sim/cockpit2/radios/indicators/hsi_display_vertical_pilot ANIM_hide 1 1 sim/cockpit2/radios/indicators/nav1_flag_glideslope TRIS 2556 96 ANIM_end I don't know what to make of it, though (for example, I don't know the meaning of the arguments to the various statements). I also sent an email to Carenado, hoping that they will shed some light. Something I haven't tried to do yet is to check if the problem is there also for the Laminar GNS.

I noticed something weird with the RXP GNS 430 in the Carenado F33A. If I do an LPV approach, the autopilot will capture the glideslope but the glidepath pointer in the HSI is not visible. For an ILS approach on the contrary the glidepath pointer is visible and works normally. I am not totally sure that the cause of the problem is the RXP GNS 430 (the settings are pretty standard, by the way) but it would be good to have some suggestion... What could technically make the vertical CDI invisible for LPV approaches only, considering that the vertical guidance is actually there and it's working?

In case it helps, I had tested also the standalone Garmin GNS trainer (v3.00) and it was working just fine even with W11.

I bought the coverage called "Worldwide-Fee" and in fact it contains three separate Navdata sets: Americas, International and Transatlantic. The price is reasonable and there are no issues whatsoever.

Eventually I reinstalled Windows 10, and the GNS started working fine again. It's definitely something with Windows 11...

Just to add that I also tried with a clean X-Plane install with just the RXP GNS plugin and the problem is still very apparent: booting the GNS takes ages and then it's very sluggish.

Just to say that I'm having the very same problem. I did a clean installation of Windows 11, but preserving my X-Plane installation. I had uninstalled the RXP software before and reinstalled it after the Windows upgrade.

Extremely useful, thanks! I have just a couple of questions: In the Jeppesen site I don't see any NavData set called Transatlantic, but they sell a set called Worldwide-Fee. Assuming that they wouldn't sell a database that has been discontinued as per Service Advisory 1846 Rev B, does it mean that Worldwide-Fee is the Transatlantic database? The fact that in your table the code for transatl is ww seems to go in that direction. Do you plan to produce a similar table for the GTN?

Does anyone have evidence that the G500 Jeppesen database for worldwide coverage will work fine on the RXP GNS and GTN? Like others, in the past I bought it for Europe only and it worked, but I'd like to choose the worldwide coverage next time.