FACILITY DATA VOR wrong TYPE field

[MSFS 2024] Bug Reports SimConnect
1

Version: SDK V1.1.2 MSFS2024 V 1.2.11

Frequency: Always

Severity: High

Similar MSFS 2020 issue: not checked

Context: FACILITY DATA VOR wrong TYPE field

Attachments: N/A, but can be provided upon request

Bug description:

FACILITY DATA VOR returns wrong TYPE field for ILSs
at least one, did not checked further so far but likely the problem persists …

also the requested data differs when using Navigraph content
-as I don’t know where the errors are getting in I start with raising the issue here.

Request for FACILITY DATA for VOR(ILS) INE@LS an Ils RW04 of LSGG returns:

ILS:  INE / LS  @LSGG plain MSFS2024

Enums:
TYPE            4: HIGH_ALTITUDE  SHOULD BE: 6: ILS
LS_CATEGORY:    1: CAT1           OK

        DME_ALTITUDE    445.00802612304688  double
        DME_AT_GLIDE_SLOPE  0   int
        DME_AT_NAV  0   int
        DME_BIAS    0   float
        DME_LATITUDE    46.230555586516857  double
        DME_LONGITUDE   6.0955001413822174  double
        FREQUENCY   110900000   uint
        GS_ALTITUDE 430.072021484375    double
        GLIDE_SLOPE 3   float
        GS_LATITUDE 46.230555586516857  double
        GS_LONGITUDE    6.0954442620277405  double
        HAS_BACK_COURSE 1   int
        HAS_GLIDE_SLOPE 1   int
        IS_DME  1   int
        IS_NAV  1   int
        IS_TACAN    0   int
        IS_TRUE_REFERENCED  0   int
        LS_CATEGORY 1   int
        TACAN_ALTITUDE  445.00802612304688  double
        TACAN_LATITUDE  46.230555586516857  double
        TACAN_LONGITUDE 6.0955001413822174  double
-->     TYPE    4   int
        VOR_ALTITUDE    430.072021484375    double
        VOR_LATITUDE    46.253555528819561  double
        VOR_LONGITUDE   6.1316943168640137  double
        NAME    "ILS RW04"  string

ILS:  INE / LS  @LSGG  + Navigraph

Enums:
TYPE            4: HIGH_ALTITUDE  SHOULD BE: 6: ILS
LS_CATEGORY:    0: NONE           SHOULD BE: 1: CAT1

        DME_ALTITUDE    445.00802612304688  double
        DME_AT_GLIDE_SLOPE  0   int
        DME_AT_NAV  0   int
        DME_BIAS    0   float
        DME_LATITUDE    46.230555586516857  double
        DME_LONGITUDE   6.0955001413822174  double
        FREQUENCY   110900000   uint
        GS_ALTITUDE 430.072021484375    double
        GLIDE_SLOPE 3   float
        GS_LATITUDE 46.230555586516857  double
        GS_LONGITUDE    6.0954442620277405  double
        HAS_BACK_COURSE 1   int
        HAS_GLIDE_SLOPE 1   int
        IS_DME  1   int
        IS_NAV  1   int
        IS_TACAN    0   int
        IS_TRUE_REFERENCED  0   int
-->     LS_CATEGORY 0   int
        TACAN_ALTITUDE  445.00802612304688  double
        TACAN_LATITUDE  46.230555586516857  double
        TACAN_LONGITUDE 6.0955001413822174  double
-->     TYPE    4   int
        VOR_ALTITUDE    430.072021484375    double
        VOR_LATITUDE    46.253563240170479  double
        VOR_LONGITUDE   6.1318302154541016  double
        NAME    "ILS/GS CAT I RW04" string

Impact: High, as the main TYPE field does not report the facility as ILS
one has to guess whether or not it is an ILS from other data which
makes the process error prone.
With Navigraph inlcuded there is only a poor way to discern using
the NAME and/or GS content to figure out if it is an ILS or other means of
Landing system or non at all.

2

I believe you can use the frequency to determine this as ILS uses specific frequencies only.

This code should help:

bool isFrequencyILS(UINT32 uiFreq)
{
	bool bRetVal = false;
	if (uiFreq > 10800 && uiFreq <= 11195)
	{
		uiFreq /= 10;
		uiFreq = uiFreq % 10;

		if ( (uiFreq % 2) != 0)
			bRetVal = true;
	}

	return bRetVal;
}
3

I think there’s a documentation issue here. The enum is actually:

	0: UNKNOWN
	1: TERMINAL
	2: LOW_ALTITUDE
	3: HIGH_ALTITUDE
	4: ILS
	5: VOT

You could use the XVOR_TYPE enum in MSFS 2024 SDK\WASM\include\MSFS\Legacy\gauges.h

@FlyingRaccoon so you can direct the bug to the right place.

1 Like
4

If only the Enum Description in Facilities SDK doc is wrong (which is very likely given the enum names where the two VOR types really don’t differ in type but only in value)…

Would it then leave the LS_CATEGORY issue to be resolved by Navigraph in their database?! I think…

5

That’s correct. The category is a new attribute with MSFS2024.