We are agreed -- FS does stange things.
Here's a screenshot showing an aircraft with a complete AFCAD2 Tools/Aircraft Editor datasheet which parks AI aircraft where they're assigned (it was created by Flight-1).
If an offending aircraft (the one not parking where we think it should) is accessed in AF2's Aircraft Editor, and any of these fields are blank or contain incorrect information; i.e., an incorrect parking code, then the offending plane's datafields must be edited and saved from this screen (in order to get the AI aircraft to park at the assigned location).
Using this AFCAD2 Aircraft Editor method, is not idiotproof but does get the aircraft to park where one wants them and is not subject to the inherent errors associated with a user-edited aircraft.cfg file.
AFCAD2 Tools/Aircraft Editor will also add the requisite parking type and codes where none exist, e.g.,
atc_parking_types=GATE,RAMP
atc_parking_codes=VIV
After all, this is why Lee included the Tools/Aircraft Editor in AFCAD2. But, as always, " . . . your call captain."
