Version: SDK V1.2.2 MSFS2024 V 1.3.10
Frequency: Always
Severity: Medium
Similar MSFS 2020 issue: not checked
Context: FACILITY DATA WAYPOINT does not resolve for some cases
Attachments: N/A, but can be provided upon request
Bug description:
FACILITY DATA WAYPOINT does not resolve for some cases
Testcase:
For the Route L153 / PIS/LI … ARLES/LF
where PIS is a VOR located in Pisa Italy
I request the WAYPOINT PIS/LI with SimConnect_RequestFacilityData_EX1(PIS,LI,W)
Expected:
to get the WAYPOINT PIS of type VOR incl ROUTE element for L153
with Prev=empty and Next=OLKIS
SimConnect does not return the WAYPOINT and the ROUTE element but
answers with a MINIMAL_LIST and gives the choice of
PIS/LI as VOR and PIS/LI as NDB (both exist but the NDB is not part of any route)
While I can ask for the VOR and NDB records - there is no way to get the ROUTE element for this airway is this situation.
There are also no means to ask for a WAYPOINT of a given type to resolve the MINIMAL_LIST.
SDK Doc says:
‘… However, if there is a conflict between multiple ICAO’s, the function will return only those that correspond to the given “Type”.’
The call for a WAYPOINT however does not reply a WAYPOINT but does propose a VOR and NDB in the MINIMAL_LIST which should not happen when using the EX1 version of this request.
It happens in other cases where a VOR and NDB in the same region with the same name exists.
For most cases SimConnect returns the correct WAYPOINT with the FIX TYPE