WT GNS 430 Missing Nearest/Comm Data in MSFS 2024 (Works in 2020)

Version: 1.39.2.0 & 1.4.20.0

Frequency: Consistently

Severity: High

Marketplace package name: bfg-navion-l17b

Context: All phases of flight with battery on and avionics powered

**Similar MSFS 2020 issue:**N/A

Bug Report: GNS 430 “Nearest” and “Comm” Data Not Displaying in MSFS 2024 Without PMS50 Mod

Title:
WT GNS 430 “Nearest” and “Comm” Pages Blank Without PMS50 Installed (MSFS 2024 only)

Sim Version Affected:
MSFS 2024 – Current release version (1.4.20.0)
Not reproducible in MSFS 2020 (latest SU15 stable)

Aircraft Affected:
Navion L-17B (custom aircraft using stock WT GNS 430 integration)

Repro Steps:

  1. Load MSFS 2024 with no PMS50 GNS430/530 mod installed
  2. Load into the Navion L-17B (or any aircraft using the stock WT GNS430)
  3. Observe the GNS 430 screen – pages like “Nearest” and “Comm” show blank fields or no data
  4. Install the PMS50 GNS mod and relaunch the sim – the pages now populate correctly

Panel.cfg Reference Used:

[VCockpit01]
size_mm=350,190
pixel_size=350,190
texture=$AS430_Screen
htmlgauge00=NavSystems/GPS/WT430/WT430.html, 0,0,350,190

Expected Behavior:
The GNS 430 should populate Nearest Airport and Comm page data using default WT files, even without any third-party mod installed.

Actual Behavior:
With no PMS50 mod installed, these pages remain blank in MSFS 2024. Behavior is normal in MSFS 2020.

Additional Notes:

  • PMS50 support confirmed their mod does not override any core sim files.
  • This appears to be a core WT430 regression in MSFS 2024 or a sim-side dependency that is missing without the PMS50 mod installed.
  • Likely tied to changes introduced in SU2 or default WT430 v2 behavior.

Attachments:
2024

2020

As mentioned in the other thread, this bug (caused by heliports nearby), is fixed in the v1 GNS in SU16 and I believe also SU3 flightings.

The reason it’s a lot more noticeable in FS2024 is the much larger quantity of heliports.

Which other thread has the heliport issue that is also causing my GNS430 not to display the Nearest and Comms correctly? I can’t find the reference and this sounds like a really odd bug if that’s what is causing it. I’ll double check if SU3 fixes it.

It is an odd issue. There was some code that expected every airport to have at least one runway when calculating the longest runway for the nearest airport page, and it threw an exception/crashed if there were no runways. I don’t know for sure if that also caused the nearest comms to also stop working.. quite possibly. If you find either unfixed in SU3 please do report back.

2 Likes

Hello @B4Gunner

This is fixed in the current version of SU4 beta.

Regards,
Sylvain

1 Like