Page 1 of 1

AI not using propper gates

PostPosted: Sun Oct 16, 2005 6:32 pm
by VVM
I have used Google Earth to try and place gates at EWR as close to the real thing as possible.  I have also assigned parking codes to all the gates.  However, AI still go to the wrong gates even if there are plenty of spare gates for that airline that are big enough to accomodate that aircraft.  Any idead why this is.  Thanks again!!!

Re: AI not using propper gates

PostPosted: Sun Oct 16, 2005 7:30 pm
by JBaymore
The quality of AI pilots they are hiring these days is slipping?   ;)


best,

....john

Re: AI not using propper gates

PostPosted: Tue Oct 18, 2005 6:52 am
by dave3cu
Did you also enter or check for the appropriate parking codes in  the  respective 'aircraft.cfg' files?

Dave

Re: AI not using propper gates

PostPosted: Sun Oct 23, 2005 10:36 am
by wji
The best way to assign parking codes to AI planes in FS9 is by using the Aircraft Editor in AFCAD2.

I've assigned what I thought was the correct code by opening and editing the respective aircraft.cfg file only to find the crates park somewhere else.

AF2 Aircraft Editor is not idiotproof but it is a foolproof method to get AI planes to park where you assign them.

Re: AI not using propper gates

PostPosted: Mon Oct 24, 2005 5:46 am
by RobertVdb
I've assigned what I thought was the correct code by opening and editing the respective aircraft.cfg file only to find the crates park somewhere else.


That's very strange. The AFCAD Editor does the same thing, just changing the code in the .cfg file. The problem can be that the radius isn't adjusted. That you can only do with the AFCAD Editor because this is a change in the .mdl file, which cannot be done in a simple editor.
Rob

Re: AI not using propper gates

PostPosted: Mon Oct 24, 2005 10:12 am
by wji
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."

Image