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

Altitude change in SDE

jvile

jvile

Messages
8,893
Jon

When ever TestApp (GUI) version 0.81 decompiles a stock airport with Approach code in the GPS, RNAV, etc legtypes it is inadvertantly changing the altitude2 to Altitude2 (capital letter see code below

<Leg
type="TF"
fixType="TERMINAL_WAYPOINT"
fixRegion="EH"
fixIdent="EH635"
recommendedType="TERMINAL_WAYPOINT"
recommendedIdent="EH635"
magneticCourse="5.3"
altitudeDescriptor="+"
altitude1="609.6M"
Altitude2="384.048M"

Altitude2= must always be lower case "a"

Just do a search in any stock FSX bgl that has approach code after decompiling with TestApp (GUI) version 0.81 and you will find all the Upper case "A" 's in the attribute Altitude2=
 
Last edited:
Thanks Jim

I will take a look at this
 
Unfortunately I am unable to provide a fix at the moment. As you know I am away from my main computer until January. The source that I have with me for SDE is not the latest so I cannot supply and update.

What I can say, having checked the code I do have, is that this affects only TF. All other approach types should be fine.

I will provide a proper update in January.

In the meantime my only suggestion is that the xml concerned would need to be hand corrected.
 
What I can say, having checked the code I do have, is that this affects only TF. All other approach types should be fine
Click to expand...

Yes that is correct. I did not go into detail on which legtypes was being affected because I knew you would be able to see it. All the other element/attributes passed through the schema just fine. I tested SDE on my EHAM approach code which probably has every single legtype written with all the airport Facility Data, exclusions, scenery and GUIDS.

No problem with the Jan date. I did not know if you carried the SDE code with you. Want mine? :D:D
 
Last edited:
You must log in or register to reply here.
Back
Top