atav757

It is so bizarre! It happened suddenly, and it's literally EVERY custom airport I have. Again, for years AI traffic were parking perfectly at assigned gates. I removed and reinstalled traffic controller and that did nothing. Using an app like AI Companion and its airport analyzer, I can see that those spots' parking codes are being read properly, and AI Companion is also reading the atc_parking_codes from aircraft.cfgs properly as well as seen below.

I'm pretty sure that column I circled is only read from the aircraft.cfg, as is wingspan, parking types, etc. I've changed nothing in my ADEs as far as parking codes, they're all assigned. This happened suddenly, after years of having AI Traffic park exactly as expected.

Since I updated to 5.3 months ago, and now 5.4, I noticed all my AI suddenly park in random locations. I opened up traffic explorer and noticed Al aircraft including my own don't show anything for parking codes, like P3D isn't reading it from any aircraft.cfg. Has anyone ever seen this before? I use AIGFP + some BGL, but realized this probably isn't the issue, in the aircraft.cfg every livery has a parking codes entry, so that's not the issue.

Thank you! Is there also a list of al possible runway parameters out there? I saw some recently that weren't in any samples, like: <ATCModel>!A321,!B739,!B77W,!A359,!A35K,!A388,!B744,!B748</ATCModel> <EmptyWeightLimit>200000</EmptyWeightLimit> Are there any that have to do with callsign? Thanks!

1st post doesn't have the latest version. The first post link is 1.0.0.1 I agree can we have a constant link or something to always have the latest?