• 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.

MSFS20 Airport Elevation issues [SOLVED]

Messages
121
Country
iran
Hello friends
Sorry about my Broken English.
I have been trying to correct and fix some errors of an airport in MSFS2020 , I was able to de compile the BGL file using the MSFSBglXml tool. As a result after the end of this process, two files in XML format were output.
Later, I found out that one of the files marked with .CVX is related to Elevation Data and they are probably vector shp(s) and eventually without these codes the airport will have problems with Elevation. But unfortunately I couldn't find a way to transfer the codes directly into main BGL of the airport because every time I get an unknown code error during compile , I even tried to fix these problems by using Terraforming method inside sim but after doing this, the PAPI lights have problems and do not work exactly according to Glide Slope. upload these 2 files for better understanding I hope someone have some advise to fix this problem.

Best
 

Attachments

Just a few quick questions before I must depart for a while today.

IIUC, this is a real world airport with a sloped RWY; do you want the RWY to be sloped in your mod scenery for MSFS ?

This terrain 'ground' property is not to be confused of course, with the "glide slope" for navigation.


What is the MSFS airport ICAO ?


Is this a generic airport everyone can open / edit, or is it a semi-restricted "World Hub" aiport ?


What is the default Altitude for this MSFS airport in the MSFS project XML properties ?


What do you want a 'corrected' Altitude to be for this airport in MSFS' project XML properties if made "flat" (non-sloped) ?

GaryGB
 
Last edited:
Just a few quick questions before I must depart for a while today.

IIUC, this is a real world airport with a sloped RWY; do you want the RWY to be sloped in your mod scenery for MSFS ?
Yes, there is a slope in reality, If it is a slope in the scenery it is better.
This terrain 'ground' property is not to be confused of course, with the "glide slope" for navigation.


What is the MSFS airport ICAO ?
OIII Mehrabad Intl airport\Iran
Is this a generic airport everyone can open / edit, or is it a semi-restricted "World Hub" aiport ?
Yes it's the generic airport , I just opened it using ADE before ، But this project which I intend to fix was made by 3rd party Developer.
What is the default Altitude for this MSFS airport in the MSFS project XML properties ?
1179.042 Meters , Its 1181.861 Meters in 3rd party Product.
What do you want a 'corrected' Altitude to be for this airport in MSFS' project XML properties if made "flat" (non-sloped) ?
Because I want to modify this project, it is better if the height is related to the developer.
 
Just have a minute on the road.

So, is the 3rd party airport 'sloped' ?

Remembering that the ARP is the center of the RWY axis, what do you want the ARP Altitude to be if that 3rd party airport is modded to be 'sloped' ?

GaryGB
 
The content of .cvx has nothing to do with terraforming. It's the attributes of exclusion polygons... Go to the SDK documentation and it will be clearer.


1739641686417.png
 
Just have a minute on the road.

So, is the 3rd party airport 'sloped' ?

Remembering that the ARP is the center of the RWY axis, what do you want the ARP Altitude to be if that 3rd party airport is modded to be 'sloped' ?

GaryGB
Yes it has , here its the sloped codes in AP's XML :

<Runway lat="35.6900572031736" lon="51.3147675991058" alt="1181.865" heading="109.650" length="3644.000" width="45.000" patternAltitude="304.800" surface="{2E0DE83F-B79A-4435-905C-DCBBEAC55C59}" transparent="TRUE" number="11" designator="LEFT" primaryTakeoff="TRUE" primaryPattern="LEFT" secondaryTakeoff="TRUE" secondaryPattern="LEFT" primaryMarkingBias="0.0000" secondaryMarkingBias="0.0000" groundMerging="FALSE" excludeVegetationAround="TRUE">
<RunwayDeformation alt="1204.400" ratio="0.0000" />
<RunwayDeformation alt="1198.700" ratio="0.2042" />
<RunwayDeformation alt="1185.000" ratio="0.4997" />
<RunwayDeformation alt="1178.000" ratio="0.6035" />
<RunwayDeformation alt="1158.500" ratio="1.0000" />
<Markings edges="FALSE" threshold="FALSE" alternateThreshold="FALSE" fixedDistance="FALSE" alternateFixedDistance="FALSE" touchdown="FALSE" alternateTouchdown="FALSE" dashes="TRUE" 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" centerRed="FALSE" edge="HIGH" />
<OffsetThreshold end="PRIMARY" length="850.000" width="45.000" surface="{00000000-0000-0000-0000-000000000000}" />
<ApproachLights end="PRIMARY" system="NONE" reil="FALSE" endLights="TRUE" touchdown="FALSE" snapToGround="FALSE" spacing="30.400" offset="30.480" slope="0.000" />
<ApproachLights end="SECONDARY" system="CALVERT" reil="FALSE" strobes="215" endLights="TRUE" touchdown="FALSE" snapToGround="FALSE" spacing="27.500" offset="30.480" slope="359.600" />
<Vasi end="SECONDARY" type="PAPI4" side="LEFT" spacing="90.000" pitch="3.100" biasX="35.369" biasZ="1403.244" />
<RunwayStart end="PRIMARY" lat="35.6929117441177" lon="51.3048514723778" alt="1181.605" heading="109.670" />
<RunwayStart end="SECONDARY" lat="35.6846287474036" lon="51.3336324691772" alt="1181.482" heading="289.670" />
</Runway>
<Runway lat="35.6885511428118" lon="51.3126562535763" alt="1181.860" heading="109.680" length="4041.000" width="60.000" patternAltitude="304.800" surface="{2E0DE83F-B79A-4435-905C-DCBBEAC55C59}" transparent="TRUE" number="11" designator="RIGHT" primaryLanding="TRUE" primaryTakeoff="TRUE" primaryPattern="LEFT" secondaryLanding="TRUE" secondaryPattern="LEFT" primaryMarkingBias="0.0000" secondaryMarkingBias="0.0000" groundMerging="FALSE" excludeVegetationAround="TRUE">
<RunwayDeformation alt="1204.000" ratio="0.0000" />
<RunwayDeformation alt="1195.700" ratio="0.1423" />
<RunwayDeformation alt="1187.600" ratio="0.3690" />
<RunwayDeformation alt="1173.300" ratio="0.6248" />
<RunwayDeformation alt="1156.000" ratio="1.0000" />
<Markings edges="FALSE" threshold="FALSE" alternateThreshold="FALSE" fixedDistance="FALSE" alternateFixedDistance="FALSE" touchdown="FALSE" alternateTouchdown="FALSE" dashes="TRUE" 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" centerRed="FALSE" edge="HIGH" />
<ApproachLights end="PRIMARY" system="SSALS" reil="FALSE" endLights="TRUE" touchdown="FALSE" snapToGround="FALSE" spacing="30.400" offset="30.480" slope="0.800" />
<ApproachLights end="SECONDARY" system="CALVERT" reil="FALSE" endLights="TRUE" touchdown="FALSE" snapToGround="FALSE" spacing="30.400" offset="30.480" slope="359.800" />
<Vasi end="PRIMARY" type="PAPI4" side="LEFT" spacing="90.000" pitch="3.400" biasX="46.474" biasZ="1617.877" />
<Vasi end="SECONDARY" type="PAPI4" side="LEFT" spacing="90.000" pitch="3.300" biasX="45.276" biasZ="1707.838" />
<RunwayStart end="PRIMARY" lat="35.694535151124" lon="51.2921065092087" alt="1181.480" heading="109.766" />
<RunwayStart end="SECONDARY" lat="35.6825724989176" lon="51.3331045210361" alt="1181.479" heading="289.766" />
</Runway>
 
Last edited:
The content of .cvx has nothing to do with terraforming. It's the attributes of exclusion polygons... Go to the SDK documentation and it will be clearer.


View attachment 95716
Yes, I know this, but when I compile the main airport XML, all the airport's elevation gets messed up, I don't know why ?! and I don't know what that QMID file is.
 
Hi Majid:

I believe some of us here may require more info in order to offer feedback on this thread.


Are you attempting to work on this airport scenery ? (ex: for use on your own installation of MSFS)

https://flightsim.to/file/14930/msfs-2020-mehrabad-intl-airport-rebuilt


If not, which 3rd party airport are you referring to.

Also, please tell us where we can find it.

GaryGB
This link is related to the free version of this airport which most likely does not have any specific problems, the problem is with the paid version of this airport which I am posting the link for you, considering that the developer is not responsible for fixing the problems (check users review about product please) , therefore I decided to fix the problems of this airport myself.

 
Last edited:
HI again:

Thanks for clarifying the actual airport you are working with.

The MSFS default terrain is within 2 Meters of IRL Altitudes at OIII RWY Start Locations.

It certainly may be indicated to see what is impacting the Glide Slope aside from any local sloped terrain XML terra-forming code.

GaryGB
 
HI again:

Thanks for clarifying the actual airport you are working with.

The MSFS default terrain is within 2 Meters of IRL Altitudes at OIII RWY Start Locations.

It certainly may be indicated to see what is impacting the Glide Slope aside from any local sloped terrain XML terra-forming code.

GaryGB
Thank you for following up and answering, I will check and let you know about the result.
 

Bavarello

GaryGB

Patrick Germain

Hi guys
Well, I finally found the problem, the problem was from the msfsbglxml side, probably a series of codes or lines are missing during de-compile, maybe that's why it outputs two XML files, I used MSFS2project instead to de-compile and the airport elevation problem was completely solved (Thanks to Patrick Germain to develop such nice tool ) on the other hand, the output file was loaded in the editor without any errors. Anyway, I thank all friends for their help and answers.
 
Last edited:

Bavarello

GaryGB

Patrick Germain

Hi guys
Well, I finally found the problem, the problem was from the msfsbglxml side, probably a series of codes or lines are missing during de-compile, maybe that's why it outputs two XML files, I used MSFS2project instead to de-compile and the airport elevation problem was completely solved (Thanks to Patrick Germain to develop such nice tool ) on the other hand, the output file was loaded in the editor without any errors. Anyway, I thank all friends for their help and answers.
Indeed, Airport2Project is a great utility (I have seen it retrieve info from FSX airports if there was no MSFS default to be found): :wizard:

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

GaryGB
 
Last edited:
Back
Top