86
edits
AI Traffic: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 367: | Line 367: | ||
FG Scenery and Traffic manager have their limitations and dependencies which create specific challenges of their own. For example: | FG Scenery and Traffic manager have their limitations and dependencies which create specific challenges of their own. For example: | ||
[[File:AI Traffic at KJFK former Terminal 3.jpg|300px|thumb|AI Traffic sitting on top of KJFK former Terminal 3]] | [[File:AI Traffic at KJFK former Terminal 3.jpg|300px|thumb|AI Traffic sitting on top of KJFK former Terminal 3]] | ||
* TM does not space landing aircrafts. You will most likely see packs of aircrafts hitting your runways at once, sometimes from both ends. | * TM does not space landing aircrafts. You will most likely see packs of landing aircrafts hitting your runways at once, sometimes from both ends. Departures are spaced properly though | ||
* TM does not yet use Regular/Cat III Holding points data and so you cannot force an AI aircraft to pause/hold on a route. | * TM does not yet use Regular/Cat III Holding points data and so you cannot force an AI aircraft to pause/hold on a route. | ||
* TM does not support the conditional use of gates (Do not use A if B is occupied); Always assume all the Parking position you set will be occupied. | * TM does not support the conditional use of gates (Do not use A if B is occupied); Always assume all the Parking position you set will be occupied. | ||