• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

msfsbglxml - convert MSFS (2020) BGL files to XML

rhumbaflappy said:
I used the latest version of CVXExtractor to extract the poly.bgl as a KML file, then used QGis to save as a shapefile. It works, but you'll loose your DBF definitions... Its about as far as I could go with it.
Click to expand...
Hi rumbaflappy,
This is a big wow. I reintroduced the files you provided in the source folder and got all the poly drawn in MSFS. As you said, the definition (properties) are not there but this is nothing compared to the time to redraw all the lines.
Big thanks for your help. Much much appreciated.

Attached for you are the images of the poly recovered. A lot are imbricated which have been complex to draw.
 

Attachments

  • Poly 1.PNG
    Poly 1.PNG
    2.4 MB · Views: 385
  • Poly 2.PNG
    Poly 2.PNG
    2.7 MB · Views: 375
Carmelo, your bgl is totally messed up. You' be better off starting from scratch. Did this start as am ADE MSFS project decompiled from the stock MSFS airport?
 
Check to see if you still have a useable XML from ADE, and consider starting from there.
 
Hi everyone:

The first post of this thread now contains msfsbglxml v1.1, which includes updates required in order to support format changes made in SU6. This new version requires a .NET 6.0 runtime, the link to which is also provided.

Enjoy!
 
Hi Matt.

I found some problems with the new release.

1) TaxiwaySign sizes are off by +1 and Size="5" is not valid...it needs to be size="SIZE5"

2) In <Runway> surface is required even if it is surface="{00000000-0000-0000-0000-000000000000}"

3) In <Runway>
<Material> type is required and missing. (This <Material> is optional, and A2P handles this by just not using it at all.) This entry seems to allow the developer to use more than one material for the runway

Here are the types:

Base tiled
Base and tire marks
Border
Center
Patch
Tire gum

4) There is also some discrepency between floating point numbers in DevMode saved XML and a msfsbglxml saved XML. That could be rounding errors or the number type used in your calculations. I think there were some problems in earlier Airport2Project versions like this.

5) And some lengths are feet, but it might be better to use meters consistently. Just a suggestion.

From DevMode:
XML: 
<?xml version="1.0"?>
<FSData version="9.0">
    <Airport country="USA" state="Idaho" city="Challis" name="Lower Loon Creek" ident="C53" lat="44.80824586004020" lon="-114.80925768613800" alt="1246.93599999999992" magvar="343.000000" airportTestRadius="10000.00000000000000" applyFlatten="FALSE" isOnTIN="FALSE" starAirport="TRUE" groundMergingTransfertBright="1.000000" groundMergingTransfertDark="1.000000">
        <TaxiName index="0" name=""/>
        <Runway lat="44.80861969292160" lon="-114.80878964066500" alt="1244.80300000000011" heading="172.53700256347656" length="367.14999389648438" width="7.61999988555908" patternAltitude="304.79998779296875" surface="{C955D525-3829-4241-AC23-86C92DCC446B}" transparent="FALSE" number="16" designator="NONE" primaryLanding="TRUE" primaryTakeoff="TRUE" primaryPattern="LEFT" secondaryLanding="TRUE" secondaryTakeoff="TRUE" secondaryPattern="LEFT" primaryMarkingBias="0.00000000000000" secondaryMarkingBias="0.00000000000000" groundMerging="TRUE" excludeVegetationAround="TRUE">
            <RunwayDeformation alt="1244.802979" ratio="0.000000" controlPointBefore="0.000000" controlPointAfter="0.000000"/>
            <RunwayDeformation alt="1249.069946" ratio="1.000000" controlPointBefore="0.000000" controlPointAfter="0.000000"/>
            <Markings edges="FALSE" threshold="FALSE" alternateThreshold="FALSE" fixedDistance="FALSE" alternateFixedDistance="FALSE" touchdown="FALSE" alternateTouchdown="FALSE" dashes="FALSE" ident="FALSE" leadingZeroIdent="FALSE" precision="FALSE" alternatePrecision="FALSE" edgePavement="FALSE" singleEnd="FALSE" primaryClosed="FALSE" secondaryClosed="FALSE" primaryStol="FALSE" secondaryStol="FALSE" noThresholdEndArrows="FALSE"/>
            <Lights center="NONE" edge="NONE"/>
            <RunwayStart end="PRIMARY" lat="44.80998996645210" lon="-114.80904266238200" alt="1244.80300000000011" heading="172.53700256347656"/>
            <RunwayStart end="SECONDARY" lat="44.80724975466730" lon="-114.80853617191300" alt="1244.80300000000011" heading="352.53698730468750"/>
            <Material guid="{C955D525-3829-4241-AC23-86C92DCC446B}" type="Base and tire marks" tilingU="1.000000" tilingV="1.000000" width="1.000000" falloff="0.000000" opacity="255"/>
            <Material guid="{CE3084FE-57A3-4BE5-AC34-2A2F8F6DF85D}" type="Base tiled" tilingU="1.000000" tilingV="1.000000" width="1.000000" falloff="0.000000" opacity="255"/>
        </Runway>
        <Aprons/>
        <PaintedElements/>
        <ApronEdgeLights/>
        <DeleteAirport deleteAllApproaches="FALSE" deleteAllApronLights="FALSE" deleteAllAprons="FALSE" deleteAllFrequencies="FALSE" deleteAllHelipads="FALSE" deleteAllRunways="TRUE" deleteAllStarts="TRUE" deleteAllTaxiways="TRUE" deleteAllBlastFences="FALSE" deleteAllBoundaryFences="FALSE" deleteAllJetways="TRUE" deleteAllControlTowers="FALSE" deleteAllDepartures="FALSE" deleteAllArrivals="FALSE" deleteAllPaintedElements="TRUE" deleteAllLightSupports="FALSE" deleteAllTaxiwaySigns="TRUE" deleteAllILSs="FALSE" deleteAllTerminalWaypoints="FALSE" deleteAllTerminalNDBs="FALSE"/>
    </Airport>
</FSData>

From msfsbglxml (fails to compile due to missing type):
XML: 
<?xml version="1.0" encoding="utf-8"?>
<FSData version="9.0" timestamp="1/1/1601 12:00:00 AM">
  <Airport country="USA" state="Idaho" city="Challis" name="Lower Loon Creek" lat="44.80824586004019" lon="-114.80925768613815" alt="4091.0F" magvar="343" ident="C53" trafficScalar="1" isOnTIN="FALSE" onlyAddIfReplace="FALSE" applyFlatten="FALSE" starAirport="TRUE" closed="FALSE" groundMergingTransfertBright="1" groundMergingTransfertDark="1">
    <Runway lat="44.80861969292164" lon="-114.80878964066505" alt="4084.0F" heading="172.537" length="367.15M" width="25.0F" patternAltitude="1000.0F" surface="{c955d525-3829-4241-ac23-86c92dcc446b}" transparent="FALSE" number="16" designator="NONE" falloff="-1" primaryLanding="TRUE" primaryTakeoff="TRUE" primaryPattern="LEFT" secondaryLanding="TRUE" secondaryTakeoff="TRUE" secondaryPattern="LEFT" groundMerging="TRUE" excludeVegetationAround="TRUE">
      <RunwayDeformation alt="4084.0F" ratio="0" />
      <RunwayDeformation alt="4098.0F" ratio="1" />
      <Coloration red="0" green="0" blue="0" alpha="0" />
      <Markings edges="FALSE" threshold="FALSE" alternateThreshold="FALSE" fixedDistance="FALSE" alternateFixedDistance="FALSE" touchdown="FALSE" alternateTouchdown="FALSE" dashes="FALSE" ident="FALSE" leadingZeroIdent="FALSE" precision="FALSE" alternatePrecision="FALSE" edgePavement="FALSE" singleEnd="FALSE" primaryClosed="FALSE" secondaryClosed="FALSE" primaryStol="FALSE" secondaryStol="FALSE" noThresholdEndArrows="FALSE" />
      <Lights edge="NONE" center="NONE" centerRed="FALSE" />
      <RunwayStart end="PRIMARY" lat="44.80998996645212" lon="-114.80904266238213" alt="4084.0F" heading="172.537" />
      <RunwayStart end="SECONDARY" lat="44.80724975466728" lon="-114.80853617191315" alt="4084.0F" heading="352.537" />
      <Material guid="{c955d525-3829-4241-ac23-86c92dcc446b}" tilingU="1" tilingV="1" width="1.0M" opacity="255" />
      <Material guid="{ce3084fe-57a3-4be5-ac34-2a2f8f6df85d}" tilingU="1" tilingV="1" width="1.0M" opacity="255" />
    </Runway>
    <TaxiName index="0" name="" />
    <DeleteAirport deleteAllApproaches="FALSE" deleteAllApronLights="FALSE" deleteAllAprons="FALSE" deleteAllFrequencies="FALSE" deleteAllHelipads="FALSE" deleteAllRunways="TRUE" deleteAllStarts="TRUE" deleteAllTaxiways="TRUE" deleteAllBlastFences="FALSE" deleteAllBoundaryFences="FALSE" deleteAllControlTowers="FALSE" deleteAllJetways="TRUE" deleteAllDepartures="FALSE" deleteAllArrivals="FALSE" deleteAllPaintedElements="TRUE" deleteAllLightSupports="FALSE" deleteAllTaxiwaySigns="TRUE" deleteAllILSs="FALSE" deleteAllTerminalWaypoints="FALSE" deleteAllTerminalNDBs="FALSE" />
  </Airport>
</FSData>


Also, the SDK may be wrong, but there is supposed to be an order to the Runway sub-elements:
"This element is allowed to contain the following sub-elements, which must occur in the following order
<Markings />, <Lights />, <OffsetThreshold />, <BlastPad />, <Overrun />, <ApproachLights />, <Vasi />, <Ils>,
<IlsReference />, <RunwayStart />, <RunwayDeformation />, <RunwayColoration />, <Material /> and <Coloration />."
 
Last edited:
Hi rhumbaflappy, thanks for the feedback.
rhumbaflappy said:
1) TaxiwaySign sizes are off by +1 and Size="5" is not valid...it needs to be size="SIZE5"
Click to expand...

Fixed in next build.

rhumbaflappy said:
2) In <Runway> surface is required even if it is surface="{00000000-0000-0000-0000-000000000000}"
Click to expand...
Fixed in next build.

rhumbaflappy said:
3) In <Runway>
<Material> type is required and missing. (This <Material> is optional, and A2P handles this by just not using it at all.) This entry seems to allow the developer to use more than one material for the runway

Here are the types:

Base tiles
Base and tire marks
Border
Center
Patch
Tire gum
Click to expand...
Any idea how/where these are derived? Are they relative to the Material GUID, or is there something I'm missing?

rhumbaflappy said:
4) There is also some discrepency between floating point numbers in DevMode saved XML and a msfsbglxml saved XML. That could be rounding errors or the number type used in your calculations. I think there were some problems in earlier Airport2Project versions like this.

5) And some lengths are feet, but it might be better to use meters consistently. Just a suggestion.
Click to expand...
These discrepancies are in practice not noticeable in MSFS and are likely due to different floating point implementations.

msfsbglxml has always cast meter values which are within a single precision floating point number's plausible rounding error of a precise number of feet or nautical miles to that precise ft/nm length; there is no change in this behaviour between 1.0 and 1.1.

rhumbaflappy said:
Also, the SDK may be wrong, but there is supposed to be an order to the Runway sub-elements:
"This element is allowed to contain the following sub-elements, which must occur in the following order
<Markings />, <Lights />, <OffsetThreshold />, <BlastPad />, <Overrun />, <ApproachLights />, <Vasi />, <Ils>,
<IlsReference />, <RunwayStart />, <RunwayDeformation />, <RunwayColoration />, <Material /> and <Coloration />."
Click to expand...
Fixed in next build.

Thanks!
 
I got the Runway Material types from the DevMode. The SDK doesn't even mention <Runway><Material> in the Docs.
 
This is surface as an attribute

1643718753279.png


These appear to be the children of a runway in the schema

1643718932658.png



I am pretty sure that I did look at Material as a child of Runway. Maybe its a custom surface material that is then used with the surface attribute,
 
Looking at KDFW (which is a problem for ADE, due to TaxiPaths), I can get a good decompilation... if I correct the Runway surface and Material properties:

Default decompilation:
XML: 
    <Runway lat="32.90377210825682" lon="-97.01121792197227" alt="172.973M" heading="135.39322" length="2743.436M" width="59.176M" patternAltitude="1000.0F" transparent="FALSE" number="13" designator="LEFT" falloff="-1" primaryLanding="TRUE" primaryTakeoff="TRUE" primaryPattern="LEFT" secondaryLanding="TRUE" secondaryTakeoff="TRUE" secondaryPattern="LEFT" groundMerging="TRUE" excludeVegetationAround="TRUE">
      <RunwayDeformation alt="168.596M" ratio="0" />
      <RunwayDeformation alt="508.0F" ratio="1" />
      <Coloration red="154" green="154" blue="154" alpha="255" />
      <Markings edges="FALSE" threshold="TRUE" alternateThreshold="FALSE" fixedDistance="TRUE" alternateFixedDistance="FALSE" touchdown="TRUE" alternateTouchdown="TRUE" dashes="TRUE" ident="TRUE" leadingZeroIdent="FALSE" precision="FALSE" alternatePrecision="FALSE" edgePavement="FALSE" singleEnd="FALSE" primaryClosed="FALSE" secondaryClosed="FALSE" primaryStol="FALSE" secondaryStol="FALSE" noThresholdEndArrows="FALSE" />
      <Lights edge="HIGH" center="LOW" centerRed="TRUE" />
      <OffsetThreshold end="PRIMARY" length="192.261M" width="59.176M" surface="{2e0de83f-b79a-4435-905c-dcbbeac55c59}" />
      <BlastPad end="PRIMARY" length="92.544M" width="59.176M" surface="{2e0de83f-b79a-4435-905c-dcbbeac55c59}" />
      <BlastPad end="SECONDARY" length="91.096M" width="59.176M" surface="{2e0de83f-b79a-4435-905c-dcbbeac55c59}" />
      <ApproachLights end="PRIMARY" system="NONE" reil="TRUE" strobes="0" endLights="FALSE" touchdown="FALSE" snapToGround="FALSE" spacing="100.0F" offset="100.0F" />
      <ApproachLights end="SECONDARY" system="MALSR" reil="TRUE" strobes="0" endLights="TRUE" touchdown="TRUE" snapToGround="FALSE" spacing="100.0F" offset="100.0F" />
      <Vasi end="PRIMARY" type="PAPI4" side="LEFT" biasX="46.669M" biasZ="654.877M" spacing="0.0F" pitch="3" />
      <Vasi end="SECONDARY" type="PAPI4" side="LEFT" biasX="49.033M" biasZ="1001.661M" spacing="0.0F" pitch="3" />
      <RunwayStart end="PRIMARY" lat="32.91113141924143" lon="-97.01986938714981" alt="172.973M" heading="135.39322" />
      <RunwayStart end="SECONDARY" lat="32.89517864584923" lon="-97.00112298130989" alt="172.973M" heading="315.39322" />
      <Material guid="{00000000-0000-0000-0000-000000000000}" tilingU="1" tilingV="1" width="1.0M" opacity="255" />
    </Runway>
Corrected Compilation:
XML: 
    <Runway lat="32.90377210825682" lon="-97.01121792197227" alt="172.973M" heading="135.39322" length="2743.436M" width="59.176M" patternAltitude="1000.0F" surface="{00000000-0000-0000-0000-000000000000}" transparent="FALSE" number="13" designator="LEFT" falloff="-1" primaryLanding="TRUE" primaryTakeoff="TRUE" primaryPattern="LEFT" secondaryLanding="TRUE" secondaryTakeoff="TRUE" secondaryPattern="LEFT" groundMerging="TRUE" excludeVegetationAround="TRUE">
      <RunwayDeformation alt="168.596M" ratio="0" />
      <RunwayDeformation alt="508.0F" ratio="1" />
      <Coloration red="154" green="154" blue="154" alpha="255" />
      <Markings edges="FALSE" threshold="TRUE" alternateThreshold="FALSE" fixedDistance="TRUE" alternateFixedDistance="FALSE" touchdown="TRUE" alternateTouchdown="TRUE" dashes="TRUE" ident="TRUE" leadingZeroIdent="FALSE" precision="FALSE" alternatePrecision="FALSE" edgePavement="FALSE" singleEnd="FALSE" primaryClosed="FALSE" secondaryClosed="FALSE" primaryStol="FALSE" secondaryStol="FALSE" noThresholdEndArrows="FALSE" />
      <Lights edge="HIGH" center="LOW" centerRed="TRUE" />
      <OffsetThreshold end="PRIMARY" length="192.261M" width="59.176M" surface="{2e0de83f-b79a-4435-905c-dcbbeac55c59}" />
      <BlastPad end="PRIMARY" length="92.544M" width="59.176M" surface="{2e0de83f-b79a-4435-905c-dcbbeac55c59}" />
      <BlastPad end="SECONDARY" length="91.096M" width="59.176M" surface="{2e0de83f-b79a-4435-905c-dcbbeac55c59}" />
      <ApproachLights end="PRIMARY" system="NONE" reil="TRUE" strobes="0" endLights="FALSE" touchdown="FALSE" snapToGround="FALSE" spacing="100.0F" offset="100.0F" />
      <ApproachLights end="SECONDARY" system="MALSR" reil="TRUE" strobes="0" endLights="TRUE" touchdown="TRUE" snapToGround="FALSE" spacing="100.0F" offset="100.0F" />
      <Vasi end="PRIMARY" type="PAPI4" side="LEFT" biasX="46.669M" biasZ="654.877M" spacing="0.0F" pitch="3" />
      <Vasi end="SECONDARY" type="PAPI4" side="LEFT" biasX="49.033M" biasZ="1001.661M" spacing="0.0F" pitch="3" />
      <RunwayStart end="PRIMARY" lat="32.91113141924143" lon="-97.01986938714981" alt="172.973M" heading="135.39322" />
      <RunwayStart end="SECONDARY" lat="32.89517864584923" lon="-97.00112298130989" alt="172.973M" heading="315.39322" />
      <Material guid="{00000000-0000-0000-0000-000000000000}" type="Base tiled" tilingU="1" tilingV="1" width="1.0M" opacity="255" />
    </Runway>

Note the addition of surface="{00000000-0000-0000-0000-000000000000}" to <Runway, and the addition of type="Base tiled to the <Material
That needed to be done for each Runway element, and then DevMode likes the code. Without the additions, the sim crashes in DevMode.

I also see you have <BlastPad entries, whereas A2P and ADE miss them. Very nice.
 
Hello,

Just wanted to make a report of an error I'm getting:


* Warning: UNIMP: Airport subsection: type 88 is unimplemented * Warning: UNIMP: Airport subsection: type 89 is unimplemented System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index') at BglLib.BglObject.AirportChild.ApronEdgeLights..ctor(Byte[] buffer, FSAirportChildType aptChildType, UInt32 recSz, Int32 lBO, BglTreeNode parentTree) at BglLib.BglObject.Airport.processSubEntry(Byte[] buffer, Int32 bufferPos) at BglLib.BglObject.Airport..ctor(Byte[] buffer, Int32 lBO, BglTreeNode parentTree) at BglLib.BglFile.readThisSection(SectPtr thisSectPtr, SectHdr thisSectHdr) at BglLib.BglFile.readSections() at BglLib.BglFile.readBgl() at MSFSBglXml.Program.processBgl()

Thank you for the program though. I've used it in countless airports since first discovering it. Cheers
 
Ryanosaurus13 said:
Hello,

Just wanted to make a report of an error I'm getting:


* Warning: UNIMP: Airport subsection: type 88 is unimplemented * Warning: UNIMP: Airport subsection: type 89 is unimplemented System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index') at BglLib.BglObject.AirportChild.ApronEdgeLights..ctor(Byte[] buffer, FSAirportChildType aptChildType, UInt32 recSz, Int32 lBO, BglTreeNode parentTree) at BglLib.BglObject.Airport.processSubEntry(Byte[] buffer, Int32 bufferPos) at BglLib.BglObject.Airport..ctor(Byte[] buffer, Int32 lBO, BglTreeNode parentTree) at BglLib.BglFile.readThisSection(SectPtr thisSectPtr, SectHdr thisSectHdr) at BglLib.BglFile.readSections() at BglLib.BglFile.readBgl() at MSFSBglXml.Program.processBgl()

Thank you for the program though. I've used it in countless airports since first discovering it. Cheers
Click to expand...
Hi
Do you have a BGL file where this occurs ?
Is it with an official one ?
 
I found a problem with the msfsbglxml-1.1.20220130 build. All the Coloration values are messed up. for example:

<Coloration red="85" green="93" blue="101" alpha="255" /> should be <Coloration red="101" green="93" blue="85" alpha="255" />

red and blue channels are switched.
 
Getting an error when trying to work with a scenery file. Tried with different syntax same message. This is a user created airport that I'm trying to fix so I don't have double runway issues with Navigraph. Author has been unresponsive to emails.
error.jpg
 
Hello, I used the 1.1.20220130 build to extract an .xml file from a freeware MSFS airport that I would like to remove the static aircraft from (EGSS). If I try to open the resulting .xml file in Dev Mode, I get an error "The Project could not be loaded".
Any ideas or tips on what I am doing wrong? I have used the scenery editor in FSX and WED in XPlane11 so I have a rough idea of what to do once I get the XML file open. Do I need to open it in a separate program to edit it?
 
toby23 said:
Hello, I used the 1.1.20220130 build to extract an .xml file from a freeware MSFS airport that I would like to remove the static aircraft from (EGSS). If I try to open the resulting .xml file in Dev Mode, I get an error "The Project could not be loaded".
Any ideas or tips on what I am doing wrong? I have used the scenery editor in FSX and WED in XPlane11 so I have a rough idea of what to do once I get the XML file open. Do I need to open it in a separate program to edit it?
Click to expand...
Hello:

You may need to use this utility instead of MSFSBGLXML:

https://www.fsdeveloper.com/forum/t...here-is-a-small-app-to-help-you-draft.450344/


Rather than editing the airport XML, you might need to create a Exclude for the unwanted static aircraft (scenery) object.

You may also benefit from a review of the MSFS SDK Docs:

https://docs.flightsimulator.com/html/Introduction/SDK_Overview.htm

GaryGB
 
Last edited:
Hi All,

I've used this tool to extract a 3rd partys .BGL into .XML in the hope that I can manually add parking codes and then recompile. I've been able to extract the .XML but editing and building in ADE is useless due to the lack of model/scenery data that ADE also compiles.

As such I was hoping to simply be able to manually edit the XML and then recompile to it to .BGL format. What program does one use to convert a .XML to a MSFS .BGL?

Thanks
 
Airbumps said:
Hi All,

I've used this tool to extract a 3rd partys .BGL into .XML in the hope that I can manually add parking codes and then recompile. I've been able to extract the .XML but editing and building in ADE is useless due to the lack of model/scenery data that ADE also compiles.

As such I was hoping to simply be able to manually edit the XML and then recompile to it to .BGL format. What program does one use to convert a .XML to a MSFS .BGL?

Thanks
Click to expand...
Here's what you can do (and what I do with high success):
1. Convert desired airport from bgl to xml.
2. Duplicate the created xml.
3. Load one xml into ADE and add parking codes, then save and close ADE.
4. Copy all the "<TaxiwayParking" entries in the newly saved ADE xml,
5. Paste and replace all the "<TaxiwayParking" entries in the duplicated XML.
6. Replace with the ADE xml with the duplicated XML
7. Load the ADE project in FS2020's scenery editor and compile with the SDK. (ADE formats projects such that you can easily load it into FS2020 scenery editor)

Alternatively, you can compile the edited original xml in ADE provided you don't hit the save button after replacing the ADE xml. I just find it easier to load the ADE project in FS20's built-in scenery editor as it has a better fault detection system.

Limitations: You can't change the gate names or else you'd need to change the jetways section as well, and a bit of the "taxiwaypoint" and "taxiwaypath" sections.

Patrick Germain said:
Hi
Do you have a BGL file where this occurs ?
Is it with an official one ?
Click to expand...
I believe the payware RCTP has this issue. I haven't checked in awhile though
 
Ryanosaurus13 said:
Here's what you can do (and what I do with high success):
1. Convert desired airport from bgl to xml.
2. Duplicate the created xml.
3. Load one xml into ADE and add parking codes, then save and close ADE.
4. Copy all the "<TaxiwayParking" entries in the newly saved ADE xml,
5. Paste and replace all the "<TaxiwayParking" entries in the duplicated XML.
6. Replace with the ADE xml with the duplicated XML
7. Load the ADE project in FS2020's scenery editor and compile with the SDK. (ADE formats projects such that you can easily load it into FS2020 scenery editor)

Alternatively, you can compile the edited original xml in ADE provided you don't hit the save button after replacing the ADE xml. I just find it easier to load the ADE project in FS20's built-in scenery editor as it has a better fault detection system.

Limitations: You can't change the gate names or else you'd need to change the jetways section as well, and a bit of the "taxiwaypoint" and "taxiwaypath" sections.


I believe the payware RCTP has this issue. I haven't checked in awhile though
Click to expand...
Thanks Ryan,

I follow you with steps 1-5. I've updated modified a copy of the original .XML and it now has the new parking position data in it. How exactly do I re-compile this newly updated .XML file into a .BGL though?
 
You must log in or register to reply here.
Back
Top