Currently experimenting with setting up a proper apron control setup, including airlines for each gate. The SDK is a but unclear on this. Quote:
“After adding the code, click on Add to have it registered with Apron Control. Note that the parking spot object requires at least one airline code to be assigned to it, but you can add multiple airline codes and then switch between them if required, although only one of them will be used at any time.”
Source: TaxiwayParking Objects
Does that mean that only one single airline PER GATE can be assigned at the same time? I have tried multiple approaches through the GUI and XML code but this actually seems to be the case. Unfortunately the SDK Sample Airports do not contain any apron control setups for orientation.
This would be a serious limitation most gates share asignments for a large number of different airlines, see this example of a single gate in my scenario:
EZY,EJU,EZS,EWG,EWL,EIN,MSC,AMC,ASL,BAW,LZB,DAL,MSR,ELY,FIN,FIA,CHH,ISR,KLM,KLC,MGL,LBT,SXS,TWI,TAR,THY
In MSFS2020 and before you can/could have as many airlines as you want and I believe it would be the same with FS24. There is currently a bug in FS24 where it appears that a gate with assigned airline(s) is not honoured but Asobo is working on this.
I assume you refer to the “airlineCodes” in the XML properties, but those it seems are entirely different thing to “apron control” that controls GSE at the gates.
To a the assignment of an airline code is now possible in two locations for each stand:
Yes, I was referring to the airline codes and I saw the two different parameters, and, like you, I understand that I don’t understand exactly what it means. Misobo complicates things with additional parameters that seem redundant because they are not explicit and detailed enough.
I eventually removed all apron control values from my taxiway parkings again (apronControlIndex and passengerAccessType) as frustratingly they seem to cause CTDs and non-working jetways with the Inibuilds A320neo and other Inibuild default aircraft.
After removing those values I haven’t seen anymore CTDs with those and both custom and “ASO_Jetway” (default jetway) work again.