Hello everyone, I'm new to the forum.

I am encountering a little problem with one of my AI planes and AFCAD.

The problem is at EGCC, my Monarch A321 seems to always park on Terminal 3.

 

I am using UK2000 EGCC scenery, but this should have no effect as all my other AI planes act normally.

I have assigned all the Parking Codes in AFCAD221, so all my MON aircraft should park in Terminal 2.

All my other aircraft parked as assigned.

 

 

I am using the DJC A321 IAE model, and I have no other AI liveries in this model, so I cannot compare.

Is there something I am doing wrong in the .CFG file, or is the parking size not correct. Maybe the DJC A321 IAE is not properly configured in the .CFG file, but I am unsure how to change this?

Maybe there is a radius problem, but I don't know how to check.

 

Any help would be greatly appreciated.

 

Many Thanks,

Alan

The devil as they say is in the detail:

 

atc_parking_codes=GATE ...this should read MON

atc_parking_types=MON......this should read GATE

 

simples

 

Peter

 

Also, I advise against using AFCAD2.2.1 to edit modern payware scenery. You "might" lose scenery detail. Use Airport design editor instead.

As Peter stated use the freeware Airport Design Editor. It is similar to AFCAD in operation for the functions you use in AFCAD but can handle additional scenery elements that might be in the afd type file whereas AFCAD might drop elements or corrupt the file.

 

AFCAD was designed prior to release of the MS software development kit with details of scenery design rules. It was very good for its time.

 

Airport Design Editor is located here:

http://www.airportdesigneditor.co.uk/

 

To open an afcad type file use File/Open Direct From BGL.

 

If you are going to make changes it is best to save the file as a project first. That saves internal data for ADE. When satisfied with those changes you the compile then project to a bgl file using its new name placing it in the same UK2K EGCC scenery folder. Then you change the extension of the original file to make it ineffective. The next time you start FS it will reindex your scenery.

 

The Fault Finder in ADE is much more comprehensive and stricter in regard to the FS scenery rules. You'll get cautions or fatal error warning, the latter aborting compilation.

 

I use it to examine AFX_ type files and some designers have switched to the ADE type files.

 

The only caution I can think of with editing AFX type files is that unlike AF2_ files they do not include frequencies and ADE has a statement as do afcad produced files to delete all frequencies. AF2_ has copied the necessary frequencies in starting its edit of default airports. If this is the case, there is a simple code change in the XML file produced by ADE to nullify that behavior.