Man I had the same problem Give me a day or two and I will give you my easy step on this
dy

Lets try B733 UAL.

I have about 25 PAI airline packages. it sounds like a loooong process of going into each .CFG and making changes.
Thanks for your help on this DYFLY. I really apreciate you taking the time and effort to help me out.

Let's go to the B737 UAL file in your FS folder.
Click on my computer
Click c:
click on program file
click on microsoft games
FS folder
click aircraft folder
click on your B737 UAL folder
click on aircraft cfg file now you will see something like this:


[fltsim.0]
title=Boeing 737-400
sim=Boeing737-400
model=
panel=
sound=
texture=
kb_checklists=Boeing737-400_check
kb_reference=Boeing737-400_ref
atc_id=N737Z
atc_airline=American Pacific
atc_flight_number=1123
ui_manufacturer=Boeing
ui_type="737-400"
ui_variation="American Pacific Airways"
atc_parking_types_=Gate Medium      <..........type this
atc_parking_Codes=UAL                <.........type this




click on file at the top save as
click save
click yes
that's it
let me know when you do this

dy

look like this


atc_parking_type=Gate Medium
atc_parking_Codes=UAL


dy

next step will be to click on AFCAD  open up airport and make a parking spot for UAL we will have to slow down for this proc. 250kts lolol
dy

Ok DYFLY.. Thanks. Does it matter if the text is in caps? I don't think so, but you never know with .CFG files.

I allready have AFCAD airports that use the RAFCAD system. Thats what brought up this question. The planes were parking all over the place, but never where they were suposed to acording to RAFCAD.

What about the model.ual folder? Do I have to create one? Does it also matter what order I type the two "ATC" lines in?

Do you have 2folders and 2 files? in your UAL folder

Now it should look like this

[fltsim.1]
title=PAI B733 UAL
sim=pai733v5
model=UAL 
panel=
sound=
texture=UAL
kb_checklists=
kb_reference=
atc_parking_type=Gate Medium
atc_parking_Codes=UAL
atc_id=
atc_id_color=0xffffffff
atc_airline=United
atc_flight_number=
ui_manufacturer=Project AI
ui_type=BOEING 737-300
ui_variation=United Airlines
atc_heavy=0
description=Project AI B733 Only for use with AI Traffic!

LIKE THIS

OK do you have the parking spot at the airport?
We want to make sure the radius is correct for that spot.
And in the parking properties it should have UAL in it
SO at the airport you should have the name beside the spot (UAL)

dy

OK do this,open up AFCAD
File and the airport open it up
At the top click on tools
Click on aircraft editor
look for your b737 and click on this to see what the radius is set at

now when you find this info you will need to go to the list
parking
click on the spot you made for UAL
Double click on this you will see parking properties
change the parking type to Gate Medium,change radius to your B737 radius,and in the parking code make sure you have UAL if not then put it in there type in UALor click on the selection list box look for United airlines click this on and you are on your way

dy

OK this is what Iam working on now I know this is long but hang in there .Igot to think this one out.

Parking Radius:

Each of the eleven standard parking types has a default radius (size). For example, "Ramp GA small" is 10 m (32.8 ft), "Gate Medium" is 38 m (124.7 ft), and so on. AFCAD will assign the default radius when you first create a parking spot, and you can keep that value or you can change it to any radius you want. You can also change the default radiuses (see Standard Parking Types).

The parking radius is normally used by FS2002 to direct various sized AI aircraft to the appropriate sized parking spot. An AI aircraft will park at the smallest empty parking spot that is big enough to hold that aircraft (they will park at bigger spots if none of the 'right sized' spots are available). The required parking spot radius for a particular model of aircraft is specified in the .mdl (model) file for that aircraft. That radius is typically 75% of the wingspan, rounded off to the nearest metre. This means you can make parking spots that are matches for most individual aircraft models (737, MD83 etc.) and get those models to park in only those spaces, unless they are all full. Here is a list of minimum parking sizes for some FS stock aircraft.

     Dash8      15 m (50 ft)
     737      22 m (73 ft)
     MD83      24 m (79 ft)
     747      47 m (155 ft)
     777      46 m (151 ft)
Note that the parking radius appears to only be encoded in the .mdl files for FS2002-built aircraft (stock aircraft and GMAX-built aircraft). The parking radius is specified in the header of the .mdl file. Aircraft not built with GMAX, which includes virtually all older add-on aircraft, use a different type of .mdl file which does not have the parking radius encoded. For those aircraft, Flight Simulator applies a default parking radius of 16 metres (52.1 feet). This can result in many add-on aircraft parking in inappropriate sized spots. At this time there does not appear to be anything that can be done about this. Note that even some GMAX built aircraft can have the radius incorrectly encoded, but this can be fixed by modifying the .mdl file radius entry with one of the features of the following third party utility:

AITM by Thomas Molitor. Available at www.molitor-home.de/fs/aitm/

Parking List Window:

The Parking List window, called from the Lists menu, shows all the parking spots for the current airport as they will appear in the start locations list that you call from the Flight Simulator Create a Flight window, with the addition of the radius for each spot.

Parking Order:

Parking is assigned to AI aircraft in the order the parking spots appear in the Parking List window. When you start a flight at an airport, Flight Simulator will place the AI aircraft in the appropriately sized parking spots in sequence, down the list.

It may look more orderly to put all gates in the list in sequential order, for example Gate 1, Gate 2, Gate 3 … etc., but it will result in AI aircraft bunching up in one area, or one terminal, when you start a flight. This will eventually randomise as AI comes and goes, but it will look more realistic if you mix up the parking order in the list, and cause the aircraft to be more evenly distributed around the terminal(s). You may notice that Microsoft mixed up the parking in this way in many stock airports. Aircraft don't usually cross over between gate and ramp parking because they have different size ranges, so you can keep gate and ramp parking together as separate groups without having to worry about aircraft bunching up, unless you have not used the default sizes for these types of parking.

You can reorder the parking list in two ways. You can grab list entries with the mouse and drag them to different locations in the list, or you can use the Randomize button.

The Randomise button will keep parking grouped by type (gate, ramp, cargo), but will mix-up the order of the parking spots within each type-group.

You can also click on the column headings of the parking list to sort the list by area, type, or size. This makes it easier to locate parking spots in a large group, or to inventory parking. Keep in mind that when you close the window the order you see in the list will be the order the parking will appear in Flight Simulator, so if you sorted parking by area, type, or size you should randomize the parking again before you exit. Alternatively, you can click the Original Order button, which will return the parking list to the order it was in when the window was opened.
Will get it!!!! I had to down load 1.4 try to work with it.I have 2.21

Yep, looking around on info 1.4, Radius may have to be put into your Aircraft CFG File,and like you said may have to create a model folder.  Well Off to  work I go  now I'll keep looking on this see what I can come up with. Rollerball or some of the others guys may have had this problem before.just have to check with them to see. Reading back in some of the forums talk about installers and Help+Tutorial.


dy