Garysb wrote:Firebird wrote:
Are you saying that all of those uncoded parking slots are full, or that it ignores them and parks in the QF4 spots anyway?
James as far as I'm aware AI only uses the first code in the aircraft cfg !
AFAIK, this is one of the advantages of FSX over FS9. In FS9, Reggie Fields and others seemed to confirm that, while the MS FS9 development gurus originally
planned for FS9 to recognize and use 3 parking codes, only the first IS used.
OTOH, this was extended in FSX and FSX ai_flightplanners can actually use 4, count 'em - 4, atc_parking_codes in the aircraft.cfg.
Consequently, for FS9, if the first parking code in the aircraft.cfg file is M001, a fighter basically parks wherever the h*** it chooses (okay, slight exaggeration there). This is partially because I've found most people don't realize that the combination of atc_parking_types=MIL_COMBAT and atc_parking_codes=M001 is essentially just duplication and therefore a waste of coding and program execution cycles. I used to use atc_parking_codes=M001
by itself but atc_parking_types=MIL_COMBAT will often suffice
provided the wing span/parking radius measurement is adjusted accordingly.
[[[atc_parking_types=MIL_CARGO used
in conjunction with atc_parking_codes=M001 is a completely different discussion in my experience.]]]
But that's just me, I guess, and I am definitely not the brightest bulb in the lot. YMMV
Added-----
My highly-personalized(not-real-world-assignment-wise) FSX-only KPAM afcad uses no atc_parking_types entries for those places I have dedicated to the QF4's. Once I added enough parking spaces to match exactly the observable parking spaces in Google Earth satellite photos, I have QF4's parking only where I want and other fighters/planes staying away from them. Yes, I did stick a few additional spots inside buildings/hangars.
((Try the freeware update on avsim.com for the Alphasim scenery package... far from perfect, but, hey, it's free and can be decompiled/recompiled for one's own use.)) And of course, as discussed in another KPAM thread, I have separated the QF4/auxiliary airfield into its own afcad - with even more QF4 parking. The routing/assignments in traffic files needs to reflect this... Definitely worth the effort if I do say so.
(My KPAM setup is, unfortunately, not publicly sharable because of a unique integration (including some deconstruction) of multiple freeware and payware products (including but not limited to Scenery Tech, FSGenesis AND SBuilderX) resulting in some unique landclassing and the de-/re-construction of someone else's scenery bgls to make the base work. Without the rest of the scenery/mods for KPAM, the afcad doesn't "make sense" and isn't "complete" - for example, some roads/taxiways/hardstands/other airport features are not represented "within the afcad" but in photoscenery/SbuilderX/landclass tiles. Sorry,
I tried for 6 months to get permission and a couple people won't give it. I finally just gave up and accept it.)
Edited to add:
atc_parking_codes=M001,F16,179F
Unless someone can prove otherwise, this is the WORST entry you could have. Assuming all 3 entries were recognized and used in FS9, which I dealt with above as not being the case in my experience, this prioritization goes from general to specific rather than the other direction. One would theoretically want to be as specific as possible when assigning parking spaces (especially for a home base), right? So, the 179F assignment should come first, then the fighter-model type (F16), and finally the most generic type (fighter) (M001). If a space allocated to the squadron is not available, then look for an F16 one, and only if neither is available should one look for a generic fighter space....right? In the case of a transient aircraft at a "foreign" base, the aircraft only looks for a spot with either F16 or M001 coding, essentially "falling through" the allocation seive quickly as no 179F-coded spots exist. If all of those fail, only then the aircraft will look for an appropriately sized MIL_COMBAT or MIL_CARGO spot.... but that's further dependent upon the plane's atc_parking_types definition.
