LFTH overlapping runways

[SwiTzer]

Hello there,

I’ve bought LFTH by https://azurpolygroup.com/. It’s a wonderful rendered scenery, which is missing (by default) in MSFS 2020. Although beautiful the scenery is missing the navaids. They claim they have set them in, but i can’t tune them and littlenavmap also doesn’t show them. Apparently I am not alone with this and they are also looking for a solution.

With navgraph beta, the Navaids would be there, but I also get overlapping runways.

Is there a way to fix this?

Thank you very much
Pascal

[NAVData]

Hi Pascal,
with the client app beta 16, we set our packages on a very low order in the sim, that all addon sceneries have higher priorities as our packages. So on the technical point of view we have done all what we can do. All other things should be checked with ASOBO/MS because we haven´t any knowledge about scenery design.

Normally, addon sceneries should NOT include any navdata records (like navaids, ILS, waypoints, terminal procedures, …). There one major reason for that:

As I wrote before, our package is placed on a very low priority - means, when a sceneries have included such data, it will be used by the scenery and not by the monthly AIRAC updates. So when the addon scenery designer doesn´t update their data also monthly, you as customer get outdated data even when you use our service.

So, this is a very bad design because scenery and navdata should be strictly separated.

To the other questions about the “double runways”, it would be the best when you report this to the developer and the developer contact us that we can look together if and how we can handle this. I´m not a scenery designer but there are a few things in the SDK available which should be consider and I don´t know, if they have consider it or not.

Only as an example from the SDK, very technical I know but important for us and all scenery designer:

<xs:complexType name="ctDeleteAirport">
    <xs:sequence>
        <xs:group ref="grpDeleteAirportChildren" minOccurs="0" maxOccurs="unbounded" />
    </xs:sequence>
    <xs:attribute name="deleteAllApproaches" form="unqualified" type="stBool" />
    <xs:attribute name="deleteAllApronLights" form="unqualified" type="stBool" />
    <xs:attribute name="deleteAllAprons" form="unqualified" type="stBool" />
    <xs:attribute name="deleteAllFrequencies" form="unqualified" type="stBool" />
    <xs:attribute name="deleteAllHelipads" form="unqualified" type="stBool" />
    <xs:attribute name="deleteAllRunways" form="unqualified" type="stBool" />
    <xs:attribute name="deleteAllStarts" form="unqualified" type="stBool" />
    <xs:attribute name="deleteAllTaxiways" form="unqualified" type="stBool" />
    <xs:attribute name="deleteAllBlastFences" form="unqualified" type="stBool" />
    <xs:attribute name="deleteAllBoundaryFences" form="unqualified" type="stBool" />
    <xs:attribute name="deleteAllControlTowers" form="unqualified" type="stBool" />
    <xs:attribute name="deleteAllJetways" form="unqualified" type="stBool" />
	<xs:attribute name="deleteAllDepartures" form="unqualified" type="stBool" />
	<xs:attribute name="deleteAllArrivals" form="unqualified" type="stBool" />
	<xs:attribute name="deleteAllPaintedElements" form="unqualified" type="stBool" />
	<xs:attribute name="deleteAllLightSupports" form="unqualified" type="stBool" />
	<xs:attribute name="deleteAllTaxiwaySigns" form="unqualified" type="stBool" />
	<xs:attribute name="deleteAllILSs" form="unqualified" type="stBool" />
	<xs:attribute name="deleteAllTerminalWaypoints" form="unqualified" type="stBool" />
	<xs:attribute name="deleteAllTerminalNDBs" form="unqualified" type="stBool" />
</xs:complexType>

<xs:complexType name="ctDeleteRunway">
    <xs:attribute name="surface" form="unqualified" type="stSurface" use="required" />
    <xs:attribute name="number" form="unqualified" type="stRunwayNumber" use="required" />
    <xs:attribute name="designator" form="unqualified" type="stDesignator" />
</xs:complexType>

Cheers,
Richard