Facility runway data `PRIMARY_THRESHOLD` and several others flagged as invalid

[MSFS 2024] Bug Reports SimConnect
1

Version: SDK 1.5.7, Sunrise 12.2, build 282174.999

Frequency: Consistently

Severity: High

Marketplace package name: N/A

Context: SimConnect_AddToFacilityData()

Similar MSFS 2020 issue: No issue logged, but when running against 2020 (after build with 2020 SDK) the same errors are given. These fields appear to be refused in both simulators.

Bug description:

When building a facility data structure, the following runway fields are reported (through an Exception message) as invalid:

  • PRIMARY_THRESHOLD
  • PRIMARY_BLASTPAD
  • PRIMARY_OVERRUN
  • PRIMARY_APPROACH_LIGHTS
  • PRIMARY_LEFT_VASI
  • PRIMARY_RIGHT_VASI
  • SECONDARY_THRESHOLD
  • SECONDARY_BLASTPAD
  • SECONDARY_OVERRUN
  • SECONDARY_APPROACH_LIGHTS
  • SECONDARY_LEFT_VASI
  • SECONDARY_RIGHT_VASI

Repro steps:
See demo 9-4. When run to display e.g. “EHGG” details and with debug output enabled:

C:\dev\Dutch FlightSim Developer\developing-with-simconnect\out\build\windows-clang-debug-tests-2024\part-9\9-4 - MSFS 2024 List Facilities in C++>.\9-4-MSFS2024-List-facilities-in-CXX.exe EHGG --debug
...[some output left out, there is a lot]...
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 48 ('PRIMARY_DESIGNATOR') to facility definition 1.
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'PRIMARY_THRESHOLD' to facility definition 1 (sendId=54)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 49 ('PRIMARY_THRESHOLD') to facility definition 1.
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'PRIMARY_BLASTPAD' to facility definition 1 (sendId=55)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 50 ('PRIMARY_BLASTPAD') to facility definition 1.
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'PRIMARY_OVERRUN' to facility definition 1 (sendId=56)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 51 ('PRIMARY_OVERRUN') to facility definition 1.
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'PRIMARY_APPROACH_LIGHTS' to facility definition 1 (sendId=57)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 52 ('PRIMARY_APPROACH_LIGHTS') to facility definition 1.
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'PRIMARY_LEFT_VASI' to facility definition 1 (sendId=58)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 53 ('PRIMARY_LEFT_VASI') to facility definition 1.
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'PRIMARY_RIGHT_VASI' to facility definition 1 (sendId=59)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 54 ('PRIMARY_RIGHT_VASI') to facility definition 1.
...[skip a bit]...
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'SECONDARY_THRESHOLD' to facility definition 1 (sendId=68)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 68 ('SECONDARY_THRESHOLD') to facility definition 1.
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'SECONDARY_BLASTPAD' to facility definition 1 (sendId=69)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 69 ('SECONDARY_BLASTPAD') to facility definition 1.
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'SECONDARY_OVERRUN' to facility definition 1 (sendId=70)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 70 ('SECONDARY_OVERRUN') to facility definition 1.
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'SECONDARY_APPROACH_LIGHTS' to facility definition 1 (sendId=71)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 71 ('SECONDARY_APPROACH_LIGHTS') to facility definition 1.
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'SECONDARY_LEFT_VASI' to facility definition 1 (sendId=72)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 72 ('SECONDARY_LEFT_VASI') to facility definition 1.
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'SECONDARY_RIGHT_VASI' to facility definition 1 (sendId=73)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 73 ('SECONDARY_RIGHT_VASI') to facility definition 1.
[2026-02-01 11:54:51] [SimConnect::Connection] [DEBUG] Added field 'CLOSE RUNWAY' to facility definition 1 (sendId=74)
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Added field 33 ('CLOSE RUNWAY') to facility definition 1.
...[skip to message handling bit]...
Connected to SunRise version 12.2
  build 282174.999
  using SimConnect version 12.2
  build Unknown
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Dispatching message with ID 1
Received an exception type 20:
- Related to a message with SendID 54.
- Regarding parameter 2.
The data passed is invalid.
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Dispatching message with ID 1
Received an exception type 20:
- Related to a message with SendID 55.
- Regarding parameter 2.
The data passed is invalid.
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Dispatching message with ID 1
Received an exception type 20:
- Related to a message with SendID 56.
- Regarding parameter 2.
The data passed is invalid.
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Dispatching message with ID 1
Received an exception type 20:
- Related to a message with SendID 57.
- Regarding parameter 2.
The data passed is invalid.
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Dispatching message with ID 1
Received an exception type 20:
- Related to a message with SendID 58.
- Regarding parameter 2.
The data passed is invalid.
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Dispatching message with ID 1
Received an exception type 20:
- Related to a message with SendID 59.
- Regarding parameter 2.
The data passed is invalid.
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Dispatching message with ID 1
Received an exception type 20:
- Related to a message with SendID 68.
- Regarding parameter 2.
The data passed is invalid.
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Dispatching message with ID 1
Received an exception type 20:
- Related to a message with SendID 69.
- Regarding parameter 2.
The data passed is invalid.
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Dispatching message with ID 1
Received an exception type 20:
- Related to a message with SendID 70.
- Regarding parameter 2.
The data passed is invalid.
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Dispatching message with ID 1
Received an exception type 20:
- Related to a message with SendID 71.
- Regarding parameter 2.
The data passed is invalid.
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Dispatching message with ID 1
Received an exception type 20:
- Related to a message with SendID 72.
- Regarding parameter 2.
The data passed is invalid.
[2026-02-01 11:54:51] [WindowsEventHandler] [DEBUG] Dispatching message with ID 1
Received an exception type 20:
- Related to a message with SendID 73.
- Regarding parameter 2.
The data passed is invalid.
...[remainder left out]...

Attachments: N/A

Private attachments: N/A