GNS530/430 Direct To not displaying airport name

Bug Reporting Hub Aircraft & Systems
, , , , ,
1

ISSUE DESCRIPTION

Whenever I use the Direct-To function (button) on the GNS530, it will not display the actual airport I’ve set as DIRECT TO on the 1st subpage of the NAV page. It just shows -----. It is still showing the correct route to the airport, in this case, WA46, but otherwise, no indication of what airport its actually navigating to. Occurs with any airport.

This is on the JF Piper Warrior ii and standard msfs-2020 WT GNS 530. The issue is the same on any aircraft using this GPS.

I have attached an image of what it should look like and how it used to work in the past.

If applicable, which aircraft is experiencing this issue:

  • Any aircraft using the GNS430/530

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?

  • Yes

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

  • Always

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Choose a plane with the GNS430/530
  2. Select the D-> (DIRECT TO) button
  3. Watch as the route is plotted but no airport info is displayed

SETTINGS

[PC Only] Are you using Developer Mode or have you made any changes to it?

  • No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

  • DX11

[PC Only] What GPU (Graphics Card) do you use?

  • AMD 7600xt Nitro +

[PC Only] What other relevant PC specs can you share?

MEDIA

image
image705×560 36.3 KB

What it should look like -

image
image323×240 5.61 KB

[END OF FIRST USER REPORT]

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

2

I’ve never used the real unit but my gut feeling is this is by design. You aren’t building a flight plan, you are just flying to somewhere from your current position. You have no origin, just a destination.

When you are building a flight plan you enter a waypoint as your origin, and then a series of waypoints for your plan or a simple A to B. You activate a leg, and you will be flying direct to your next waypoint. “Direct to” doesn’t do that. But as I say, I’m not familiar with the IRL unit, and I could find no examples on YouTube of a user demonstrating Direct To, and then bringing up the flight plan page.

3

The in real life GNS works the way I mentioned. I’ve used them extensively in the past when I used to fly. The origin is your current location and it shows a depiction of a D> to the location you input.

The second screenshot is from the official Garmin GNS simulator.

4

So in your second image you are going to Direct To 51K? I did try to find a copy of the 530 trainer, but its really old, and will only work with Windows XP. I think the sim one does show your destination, but at the top of the flight plan page.

5

Yes, for testing purposes, I hit the D> (direct to) button, input 51K, Enter, Enter and that is what shows up on the display. A direct to indication in magenta to 51K. I used this all the time in the various aircraft I flew in the past in real life.
I do believe this used to work just fine in older iterations of MSFS2020, but I could be mistaken. Was playing a lot of X-plane at the time so I could have gotten confused

6

This should work on Windows 10. The one I use
Garmin: 400W/500W Series Trainer - WAAS Updates & Downloads

7

Do you have the same issue if you follow the OP’s steps to reproduce it?
• yes

Provide extra information to complete the original description of the issue:

430 added to the title since same issue

If relevant, provide additional screenshots/video:
•

8

I’m surprised this hasn’t had any traction considering its a pretty big issue when it comes to the functionality of the GNS.
Is it normal for Asobo to take a while to reach these bug reports?