Incorrect range increase/decrease logic on default GNS 530/430 unit

Bug Reporting Hub Resolved
, , , , , ,
1

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue:
The increase/decrease range keys on the GNS 530/430 has the incorrect logic. Pressing increase range (the top button) with the mouse actually zooms-in the display which is incorrect; increase range should zoom-out. Same applies to the decrease range button but reversed of course.

If applicable, which aircraft is experiencing this issue:
Any aircraft with a GNS 530/430.

[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. Select aircraft with GNS
  2. Try to increase range expecting zoom out.
  3. See an incorrect zoom in.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

[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?

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

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

AMD 9800x3d

MEDIA

Please add a screenshot or video of the issue occurring.

[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:
•

1 Like
2

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:
• See below Garmin GNS530 manual extract
Same issue with the GNS430
@AboezD : You may update your title/description with GNS430 too

If relevant, provide additional screenshots/video:
•
image

3

Update on this bug. I’ve just noticed that the correct logic is used on the DHC6 Twin Otter which is a Microsoft airplane so maybe it’s just the Asobo models exhibit the bug? I’ll see if I can find another Microsoft plane with a 530/430 unit to test.

Polite query: How and/or when does this bug report become feedback-logged? It is a genuine, reproducible bug albeit with only 1 vote(!) how will it become known to the developers?

1 Like
4

This is a 100% reproducible bug affecting every user (who flies just about any of the GNS530/430 aircraft), it has been confirmed by a forum moderator and yet remains untagged as even “feedback-logged”. Can someone explain the forum bug triage system to me? Is it based on votes? The opinion of the moderators? Will the developers remain unaware of this bug (unless they’ve already noted it themselves)?

ETA: this post isn’t a rant caused by my bug report not getting attention. I’m genuinely interested in how bugs get from the forum to the attention of the developers :slight_smile:

1 Like
6

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.

Generally, we log items based on votes, but we do try to also log based on activity within the topic.

1 Like
7

You state in your post one of the criteria is an “Attempt to recreate the issue” - it has been recreated by @DementedCorn327 and yet still not labelled “bug-logged”. I was hoping the round of fixes in SU3 would see this basic bug swatted but sadly it has not.

*basic but affecting every single default Asobo aircraft that uses a GNS530!

8

Definitely inverted for me as well on the stock Cessna 172 Classic. This should be 5 minutes fix. It was correct in MSFS 2020.

9

It’s been a while since this has been reported. Has this been addressed for SU4?

May you also check if the bug/ineffective implementation of the binding-events affecting the CLR-button has been logged?

(Another minor but annoying issue in regarding the range zoom: The default DHC6 mentioned here and the default C172 use different binding-events for the GNS range-zoom buttons. Not sure if there are similar inconsistencies with other default aircraft and the GNS units, but it’s a bit unfortunate when consistency is missing for basic control inputs… a clean-up would be very welcome.)

10

No (not as of SU4 beta 1.6.11.0).

13

Let’s hope that the C172 is one of the many aircraft that Asobo are improving for su4 and that this long standing bug is finally squashed.

14

And isn’t the range buttons reversed, if the 2020 version is correct.

15

Yes. That’s why I created this thread :slight_smile:

The other bug @GunStrauss8 has linked to is likely to be related to or caused by the same underlying error. Posting that finding may help the devs isolate the cause.

16

It’s probably not a general mysterious bug in the unit, it’s just the wiring of the buttons need some more work/love to sort out these 3 issues.

BTW: Now my post(s) have been hidden again. The MSFS forum feels like a hall meeting in North Korea.

17

Restoration of links in hidden post above. Other related issues to the “wiring” of buttons on the GNS units:

Really hope all three issues related to the wiring of the GNS buttons will be resolved in a coming update!

19

Fixed in SU5 Beta:
Continuing the discussion from Sim Update 5 Beta (1.7.7.0) Release Notes - February 20, 2026:

1 Like
20

Issue is NOT solved as of 3-17-2026.

The 430 is still exhibiting the same incorrect behavior.

The 530, however, is fixed.

21

Issue fixed for me in the SU5 Beta with both the GNS530 & GNS430.

C172 Classic:

Are you in the Beta ?
Which aircraft have you tested ?
Do you have the aircraft streamed or downloaded ?

22

FS 2020.

I don’t know about any ‘beta’.

Flying the DC-3 ‘retrofit’, and have not checked any other aircraft since I thought gauges reside in a separate folder from aircraft…right?

I’m on PC, so all the planes are on my HDD.

23

Issue was originally reported for FS2024 and it has been fixed in FS2024 SU5 Beta.

In FS2020 both GNS530/430 work as expected.
C172 Classic:

24