AI traffic, how does it work?

[ctesc356]

Hello,
I am trying to understand how the AI traffic works.
I see a lot of AI / Traffic scheduled flights, but not all of them seem to be running?
Watching the traffic at EGLL, I saw departures but no arrival.
Is there a way to easily know the daily movements for a given airport?

[BecOzIcan]

Watching the traffic at EGLL, I saw departures but no arrival.

Normally arrivals tale a bit more time to kick in. First movements you should observe are pushbacks. No schedule per airport AFAIK.
For any particular aircraft on screen turn on the Map to identify the Flight number (Tick "Data") then search the traffic file for this airline to know the details of this flight

Cheers
Ian

[Gijs]

Hello,
thanks for your reply. Or whatever, I do not see very few arrivals

As the reading in the AI / Traffic folders is quite painful, I have written this little python script.
It goes through the Traffic folder, counts and ouput the movements for a given airport per time.
for example: short extract from result for LFBZ

Code: Select all

Mouvements pour  LFBZ  jour  1

Easy4311               Arr 06:25    de    LFLL  05:10 
Easy4312               Dep 06:55  pour LFLL  08:10 
AIRFRANS7497       Dep 08:10  pour LFPG  09:30 
AIRFRANS7480       Arr 09:25    de    LFPG  08:10 


in the console it's better aligned

The instructions are in the file.
Tested with linux, if a brave wants to test under windows ...
http://www.mediafire.com/file/4n33p0c23 ... _en.py.zip

[BecOzIcan]

I have never spent enough time a EGLL to confirm incoming traffic works. The one place where I know for sure incoming AI traffic happens is LFPG using my custom scenery. See viewtopic.php?f=5&t=32559&hilit=+lfpg#p314553

Cheers
Ian

[wkitty42]

For any particular aircraft on screen turn on the Map to identify the Flight number (Tick "Data") then search the traffic file for this airline to know the details of this flight

psst... one of the things i'm working on is to hopefully have the AI craft's schedule written to the log... that way it'll be easier to see when that craft is due to depart and arrive from which airports... right now i'm looking at having this be either a debug or info level...

eg:

Code: Select all

AIFlightPlan::createPushBack: aircraft '0x18f132f0' firstflight 'TRUE' departure 'EDDM' radius '17' type 'gate' craft '321' airline 'DLH'
AIFlightPlan::createPushBack: aircraft '0x18b0e1d0' firstflight 'FALSE' departure 'EDDM' radius '17' type 'gate' craft '737-700' airline 'BER'
AIFlightPlan::createPushBack: aircraft '0x18cc70d0' firstflight 'TRUE' departure 'EDDM' radius '14' type 'gate' craft '735' airline 'BTI'
AIFlightPlan::createPushBack: aircraft '0x18f22800' firstflight 'TRUE' departure 'EDNY' radius '17' type 'gate' craft '320' airline 'WZZ'
AIFlightPlan::createPushBack: aircraft '0x19300df0' firstflight 'TRUE' departure 'LIME' radius '17' type 'gate' craft '320' airline 'WZZ'
AIFlightPlan::createPushBack: aircraft '0x18cada10' firstflight 'TRUE' departure 'EDDM' radius '17' type 'gate' craft '320' airline 'DLH'


what i need to break out further is contained in the "aircraft '0xXXXXXXXX'" section... i'm just working through the code to see what i can pull out and how to get it into a format that humans can easily read... this is definitely a WIP and not available outside my local system

[wkitty42]

i've been hanging out (hovering actually) at EGLL and EGKK for a month or two, now... arrivals and departures definitely work... the biggest problem i see is AI craft getting stuck and one getting in front of another when it should be behind... this mainly at ground net intersections... it is very bad at startup when all AI are loaded instead of just the ones that are leaving in an hour or two... that is also one of the reasons why there are duplicate callsigns at times...