• 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 MSFS Airline Parking Codes

Messages
1,025
Country
us-florida
Back in the day FS2004, FSX, P3D at Project AI and other AI groups we all used the ICAO codes for airline parking.

Back then the limit for the "airlineCodes=" entry was limited to 4 characters per airline code...

Our work around for stuff like QANTAS and other airline regional feeders was to add an X to the end of the code...

e.g.

QFA <- Main QANTAS
QFAX <- QANTAS Regional Subsidiary like Sunstate flying in QANTAS' scheme etc

We did this system as we could only use 4 characters for the parking code.

I haven't experimented with MSFS yet, but I'm wondering if anyone knows if that airline parking code limit is still 4 characters?

I'm assuming it is as the path for the FSX code went -> ACES FSX code -> Dovetail FSX code -> Dovetail 64bit FSX code conversion -> Asobo inherits 64bit FSW/FSX code -> Asobo MSFS code.

It seems that Asobo hasn't likely changed anything as they didn't include the "airlineCodes" tag in DevMode but it still exists in the XML code and MSFS SDK under the "Taxiway Definitions Properties" section of the SDK (https://docs.flightsimulator.com/ht..._Facilities/Taxiway_Definition_Properties.htm)

Just curious if anyone has taken a deep dive on parking codes as yet?
 
I haveI have made a quick test with ADE to see what happens with more than 4 characters for a given gate with "UNITED" and here is the result :

INTERNAL COMPILER ERROR: #C2542: Airline Codes can have a maximum of 4 characters
INTERNAL COMPILER ERROR: #C2031: Failed element parse <TaxiwayParking>
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:
ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = france
ERROR: state = NO STATE
ERROR: city = Paris
ERROR: name = Charles-de-Gaulle
ERROR: lat = 49.009810947
ERROR: lon = 2.547777593
ERROR: alt = 108.127M
ERROR: magvar = 2
ERROR: trafficScalar = 1
ERROR: airportTestRadius = 10000.0M
ERROR: altType = GEOID
ERROR: isOnTIN = FALSE
ERROR: onlyAddIfReplace = FALSE
ERROR: applyFlatten = FALSE
ERROR: starAirport = FALSE
ERROR: closed = FALSE
ERROR: groundMergingTransfertBright = 0
ERROR: groundMergingTransfertDark = 0
ERROR: ident = LFPG
ERROR: >
ERROR: <TaxiwayParking
ERROR: index = 71
ERROR: lat = 49.0022996732694
ERROR: lon = 2.55802522385197
ERROR: heading = 102.4
ERROR: radius = 33.0M
ERROR: type = GATE_HEAVY
ERROR: name = GATE_A
ERROR: number = 30
ERROR: suffix = NONE
ERROR: airlineCodes = UNITED
ERROR: numberMarking = TRUE
ERROR: numberBiasX = -55
ERROR: numberBiasZ = -85
ERROR: numberHeading = 341
ERROR: has3DMesh = TRUE
ERROR: pushBack = NONE
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2589: Did not find end Parking Spot #71 needed for Taxi path #4214 at airport LFPG.
INTERNAL COMPILER ERROR: #C2032: XML Parse Error! Element tree follows:
ERROR: <FSData
ERROR: version = 9.0
ERROR: >
ERROR: <Airport
ERROR: country = france
ERROR: state = NO STATE
ERROR: city = Paris
ERROR: name = Charles-de-Gaulle
ERROR: lat = 49.009810947
ERROR: lon = 2.547777593
ERROR: alt = 108.127M
ERROR: magvar = 2
ERROR: trafficScalar = 1
ERROR: airportTestRadius = 10000.0M
ERROR: altType = GEOID
ERROR: isOnTIN = FALSE
ERROR: onlyAddIfReplace = FALSE
ERROR: applyFlatten = FALSE
ERROR: starAirport = FALSE
ERROR: closed = FALSE
ERROR: groundMergingTransfertBright = 0
ERROR: groundMergingTransfertDark = 0
ERROR: ident = LFPG
ERROR: >
ERROR:
INTERNAL COMPILER ERROR: #C2024: Failed to process closing element tag <Airport> near line 396507!
INTERNAL COMPILER ERROR: #C2607: Compilation errors detected, compilation failed!
INTERNAL COMPILER ERROR: #C2006: Parse failed (0x 0)
Compiling Package Metadata...
Compiling Package Metadata...
PackageBuilder | Skip mirroring due to command failures.
PackageBuilder | Skip generation of package information due to command failures.
PackageBuilder | Finished, 0 skipped, 2 done and 1 failed, took 3s058ms. Failed: [lfpg-charles-de-gaulle/lfpg-airport](15407726393528552466) - Command 1═}♦úCÈø4Ðe♥û>®p ú2┘j é▬▒~↓ÑOÀà¶▒D▀ç´è

Everything back to normal with Code "UNIT"
Xavier
 
I haveI have made a quick test with ADE to see what happens with more than 4 characters for a given gate with "UNITED" and here is the result :



Everything back to normal with Code "UNIT"
Xavier
Hi Xavier,

Thanks for the test. Just so you know, the standard for Airline parking codes in FS since FS2002 is based on the ICAO airline codes.

For United Airlines it's UAL

Wikipedia has a comprehensive list for all the IATA airline codes for free..."

 
Parking Codes are still supported in the BGL format and are used by the Game, but the ingame SDk Scenery Editor does not support them for no obvious reason... You have to add them in the XML yourself or use ADE.
 
I think you mean ICAO ;) IATA is two characters ^^
You're absolutely correct, I even have my database as ICAO, edited my post lol. Thanks for correcting me, I appreciate it. :D

Parking Codes are still supported in the BGL format and are used by the Game, but the ingame SDk Scenery Editor does not support them for no obvious reason... You have to add them in the XML yourself or use ADE.

Yeah that's the most annoying part, all they'd have to do is take 10 mins with the code and turn it on and add a menu entry...
 
already requested ;)

I'm hoping you requested also for Aircraft Type for parking... I put that in the Game Design Docs for FSW Asobo inherited. Suggested encoded parking T's that can have aircraft type visually on the T. With the location of the T being a known factor from the nose of the aircraft to the nosewheel.

It's actually fun looking at all the stuff I wrote that was needed for FSW and seeing almost all of it in MSFS...
 
Just so you know, the standard for Airline parking codes in FS since FS2002 is based on the ICAO airline codes.
Yes I do know that but it was for test purposes. ADE and MSFS seems not to care about the ICAO airline code as far as it is four characters maximum. That's the Airline code inside the .cfg that matters ; MSFS via ADE directs the plane to the good gate(s) whether available. I have put in my favorite airports (LFPG/LFPO) strings of "XXX" airlines code before the proper ones to chase-out some (real) airlines according to preferences (jetway or not). It works not too badly.
 
<TaxiwayParking
index="99"
lat="49.0053213403536"
lon="2.56151314840767"
heading="197.09420673945"
radius="33.0M"
type="GATE_HEAVY"
name="GATE_B"
number="14"
suffix="NONE"
airlineCodes="AAL, REU, THT, DAH, REU, JBU, ELY, TGZ, ASL, RAM, UZB, MNE"
numberMarking="TRUE"
numberBiasX="0"
numberBiasZ="0"
numberHeading="0"
has3DMesh="TRUE"
pushBack="NONE"/>

That's from MSFS2020 and it's the same architecture with FSX. It's slightly different with MSFS2024 but I imported my 2020 project in MS2024 ; it's compiled and airlines go where they are assigned.
 
<TaxiwayParking
index="99"
lat="49.0053213403536"
lon="2.56151314840767"
heading="197.09420673945"
radius="33.0M"
type="GATE_HEAVY"
name="GATE_B"
number="14"
suffix="NONE"
airlineCodes="AAL, REU, THT, DAH, REU, JBU, ELY, TGZ, ASL, RAM, UZB, MNE"
numberMarking="TRUE"
numberBiasX="0"
numberBiasZ="0"
numberHeading="0"
has3DMesh="TRUE"
pushBack="NONE"/>

That's from MSFS2020 and it's the same architecture with FSX. It's slightly different with MSFS2024 but I imported my 2020 project in MS2024 ; it's compiled and airlines go where they are assigned.
Tried the airlineCodes but it did compile but not properly. I was unable to edit the bgl/scenery inside the sim. All objects were not in the scenery editor list
 
@skullhd
In your project structure folders you have « Package source » and inside the « data » one. Everything is inside the « airportname.xml ». You can search for « airlinecodes » and see what’s in there... The correct format is written above in the example. Don’t forget the space after the comma...When the xml is modified (or not) the file must be saved. When the project is loaded in the Editor, saved and built, the only way to check if it’s good is to load FSLTL or equivalent and observe if the parameters are taken in account.
The big problem is that the airlinecode criteria is not visible in the SDK tools « taxiwayParking » object Properties, and it seems impossible to enter the airline code directly in there, though it’s described in the SDK documentation. I have reported this problem in the Devsupport forum and no reply until now.
If you don’t see errors in the console while building the project, then the syntax is OK.
I’m away from my FS « base » and I may not have been very clear...
 
@skullhd
In your project structure folders you have « Package source » and inside the « data » one. Everything is inside the « airportname.xml ». You can search for « airlinecodes » and see what’s in there... The correct format is written above in the example. Don’t forget the space after the comma...When the xml is modified (or not) the file must be saved. When the project is loaded in the Editor, saved and built, the only way to check if it’s good is to load FSLTL or equivalent and observe if the parameters are taken in account.
The big problem is that the airlinecode criteria is not visible in the SDK tools « taxiwayParking » object Properties, and it seems impossible to enter the airline code directly in there, though it’s described in the SDK documentation. I have reported this problem in the Devsupport forum and no reply until now.
If you don’t see errors in the console while building the project, then the syntax is OK.
I’m away from my FS « base » and I may not have been very clear...
Thanks for the update got the codes into the xml and it compile with no errors. Now its the sim issue where the AI still parks at wrong gates although in their cfg its the correct code. So working on sorting that now.
 
Back
Top