Fspackagetool error - duplicate START with dual-runways at an new airport

Version: 1.2.8.0 - SDK 1.1.2

Frequency: Consistently

Severity: Blocker

Bug description:
When you try to add a new airport with parallel runways (L/R), you can´t set the START tag for all runways due to an error from the fspackagetool.

Example OKKK (Kuwait) - which has 4 runways 15L/R and 33L/R - when I try to parse it, I get these error messages from the fspackagetool:

ERROR: #C2533  ***** Duplicate Start *****
ERROR: #C2031 Failed element parse <Start>
ERROR: XML Parse Error!  Element tree follows: <FSData version = 9.0timestamp = 22/12/2024 - 08:43:57 UTCsource = Jeppesen Sanderson, Inc.>     <Airport country = KUWAITstate = city = Kuwaitname = Kuwait Intlregion = Asialat = 29.22676667lon = 47.97995278alt = 205Fmagvar = -3.0ident = OKKKairportTestRadius = 22965.88trafficScalar = 0.7isOnTIN = FALSEonlyAddIfReplace = FALSEapplyFlatten = FALSEstarAirport = FALSEclosed = FALSE>          <Start number = 15designator = RIGHTlat = 29.24011471lon = 47.96173735alt = 133Fheading = 155.00212type = RUNWAY>
ERROR: #C2533  ***** Duplicate Start *****
ERROR: #C2031 Failed element parse <Start>
ERROR: XML Parse Error!  Element tree follows: <FSData version = 9.0timestamp = 22/12/2024 - 08:43:57 UTCsource = Jeppesen Sanderson, Inc.>     <Airport country = KUWAITstate = city = Kuwaitname = Kuwait Intlregion = Asialat = 29.22676667lon = 47.97995278alt = 205Fmagvar = -3.0ident = OKKKairportTestRadius = 22965.88trafficScalar = 0.7isOnTIN = FALSEonlyAddIfReplace = FALSEapplyFlatten = FALSEstarAirport = FALSEclosed = FALSE>          <Start number = 33designator = LEFTlat = 29.21311348lon = 47.97608528alt = 169Fheading = 335.00934type = RUNWAY>
ERROR: #C2607 Compilation errors detected, compilation failed!

Attachments:
Here is the raw XML-file to reproduce this issue:

<FSData version="9.0" timestamp="22/12/2024 - 08:43:57 UTC" source="Jeppesen Sanderson, Inc." xsi:noNamespaceSchemaLocation="file:///D:/Simulation/Tools/SDKs/MSFS2024/Tools/bin/bglcomp.xsd" >
<Airport country="KUWAIT" state="" city="Kuwait" name="Kuwait Intl" region="Asia" lat="29.22676667" lon="47.97995278" alt="205F" magvar="-3.0" ident="OKKK" airportTestRadius="22965.88" trafficScalar="0.7" isOnTIN="FALSE" onlyAddIfReplace="FALSE" applyFlatten="FALSE" starAirport="FALSE" closed="FALSE" >
<Services>
 <Fuel type="100" availability="YES" />
 </Services>
<Runway lat="29.22695421" lon="47.99101251" alt="205F" surface="ASPHALT" transparent="FALSE" heading="155.01712" length="11483F" width="148F" number="15" designator="LEFT" primaryDesignator="LEFT" secondaryDesignator="RIGHT" patternAltitude="1000.0F" falloff="0" primaryTakeoff="TRUE" primaryLanding="TRUE" secondaryTakeoff="TRUE" secondaryLanding="TRUE" primaryPattern="LEFT" secondaryPattern="LEFT" primaryMarkingBias="0.0" secondaryMarkingBias="0.0" groundMerging="TRUE" excludeVegetationAround="TRUE" >
 <Markings alternateThreshold="FALSE" alternateTouchdown="FALSE" alternateFixedDistance="FALSE" alternatePrecision="TRUE" leadingZeroIdent="TRUE" noThresholdEndArrows="TRUE" edges="TRUE" threshold="TRUE" fixedDistance="TRUE" dashes="TRUE" ident="TRUE" primaryClosed="FALSE" secondaryClosed="FALSE" touchdown="TRUE" precision="TRUE" edgePavement="TRUE" singleEnd="FALSE" primaryStol="FALSE" secondaryStol="FALSE" />
 <Lights center="HIGH" edge="HIGH" centerRed="TRUE" />
 <ApproachLights end="PRIMARY" system="ALSF2" strobes="15" reil="FALSE" touchdown="TRUE" endLights="TRUE" />
 <ApproachLights end="SECONDARY" system="ALSF2" strobes="15" reil="FALSE" touchdown="TRUE" endLights="TRUE" />
 <Vasi end="PRIMARY" type="PAPI4" side="LEFT" biasX="174.00F" biasZ="4882.32F" spacing="300.0F" pitch="3.00" />
 <Vasi end="SECONDARY" type="PAPI4" side="LEFT" biasX="174.00F" biasZ="4639.53F" spacing="300.0F" pitch="3.00" />
 </Runway>
<Runway lat="29.22664944" lon="47.96893142" alt="205F" surface="CONCRETE" transparent="FALSE" heading="155.00212" length="11155F" width="148F" number="15" designator="RIGHT" primaryDesignator="RIGHT" secondaryDesignator="LEFT" patternAltitude="1000.0F" falloff="0" primaryTakeoff="TRUE" primaryLanding="TRUE" secondaryTakeoff="TRUE" secondaryLanding="TRUE" primaryPattern="LEFT" secondaryPattern="LEFT" primaryMarkingBias="0.0" secondaryMarkingBias="0.0" groundMerging="TRUE" excludeVegetationAround="TRUE" >
 <Markings alternateThreshold="FALSE" alternateTouchdown="FALSE" alternateFixedDistance="FALSE" alternatePrecision="TRUE" leadingZeroIdent="TRUE" noThresholdEndArrows="TRUE" edges="TRUE" threshold="TRUE" fixedDistance="TRUE" dashes="TRUE" ident="TRUE" primaryClosed="FALSE" secondaryClosed="FALSE" touchdown="TRUE" precision="TRUE" edgePavement="TRUE" singleEnd="FALSE" primaryStol="FALSE" secondaryStol="FALSE" />
 <Lights center="HIGH" edge="HIGH" centerRed="TRUE" />
 <ApproachLights end="PRIMARY" system="ALSF2" strobes="15" reil="FALSE" touchdown="TRUE" endLights="TRUE" />
 <ApproachLights end="SECONDARY" system="ALSF2" strobes="15" reil="FALSE" touchdown="TRUE" endLights="TRUE" />
 <Vasi end="PRIMARY" type="PAPI4" side="LEFT" biasX="174.00F" biasZ="4536.64F" spacing="300.0F" pitch="3.00" />
 <Vasi end="SECONDARY" type="PAPI4" side="LEFT" biasX="174.00F" biasZ="4415.98F" spacing="300.0F" pitch="3.00" />
 </Runway>
 <Start number="15" designator="LEFT" lat="29.24082570" lon="47.98360645" alt="160F" heading="155.01712" type="RUNWAY" />
 <Start number="33" designator="RIGHT" lat="29.21301040" lon="47.99837690" alt="204F" heading="335.02457" type="RUNWAY" />
 <Start number="15" designator="RIGHT" lat="29.24011471" lon="47.96173735" alt="133F" heading="155.00212" type="RUNWAY" />
 <Start number="33" designator="LEFT" lat="29.21311348" lon="47.97608528" alt="169F" heading="335.00934" type="RUNWAY" />
 </Airport>
 </FSData>

I assume there is a bug in the validation. The fspackagetool looks only at the “number” attribute but not at the “designator”; therefore, the message has the duplicate “START” tag.

You see the same error message in this posting (last line of the posted error screenshot - that´s due the double number NORTH:

Please let me know if I have done something wrong. Thank you!

Cheers,
Richard

1 Like

Hello @NAVData

We have a regression on the handling of <Start> elements for runways.
For runways, our own workflow only relies on <RunwayStart> elements instead.
(This is a bit confusing, we’ll add notes in the documentation)
We will fix that regression but feel free to switch to RunwayStart as a workaround.

Regards,
Sylvain

Hello @NAVData

This should no longer be an issue with Sim Update 1

Regards,
Sylvain

2 Likes

Hi Sylvain,
I can confirm it - issue solved with SU1.

Thank you very much
Richard

1 Like

This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.

If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.