AI Traffic: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Warnings and Limitations to creating a groundnet)
No edit summary
Line 364: Line 364:
=== Warnings and Limitations ===
=== Warnings and Limitations ===
The complexity of building a fully functional groundnet (and the time spent on it) grows exponentially with the size of the airport but very small airports, on Pacific Islands for example, pose even larger challenges. An ideal project to start with is a Metropolitan airport with one or two runways, and two dozen of parking positions.  
The complexity of building a fully functional groundnet (and the time spent on it) grows exponentially with the size of the airport but very small airports, on Pacific Islands for example, pose even larger challenges. An ideal project to start with is a Metropolitan airport with one or two runways, and two dozen of parking positions.  
 
[[File:Multi Radii ParkPos.png|200px|thumb|eAIP showing a Parking Stand accommodating more than one aircraft category]]
Traffic manager has its limitations and not all features are yet implemented, creating specific challenges of their own. For example:
FG Scenery and Traffic manager have their limitations and create specific challenges of their own. For example:
* TM does not handle the spacing of arriving aircraft and you will most likely see packs of aircrafts landing at once on your runways, sometimes from both ends.  
* TM does not handle the spacing of arriving aircraft and you will most likely see packs of aircrafts landing at once on your runways, sometimes from both ends.  
* TM does not understand Holding Points so you cannot prevent an AI aircraft to cross an active runway of you have placed a route across it.  
* TM does not understand Holding Points so you cannot prevent an AI aircraft to cross an active runway if you have placed a route across it.  
* TM cannot handle the conditional usage of gates accommodating more than one aircraft type (One large only or 2 small side by side) so you should always assume that all the Parking position you set will be occupied.  
* TM cannot handle the conditional usage of gates which accommodate more than one aircraft type (See Image on the right) so you should always assume that all the Parking position you set will be occupied.  
* AI Aircrafts cannot "pivot" on their parking positions so the route followed to reach a parking position must have the same heading than the parking position itself (Park Straight)  
* AI Aircrafts cannot "pivot" on their parking positions so the route followed to reach a parking position must have the same heading than the parking position itself (Park Straight)  
* Groundnets, terrain and scenery objects are not technically interdependent and you may see your aircrafts rolling on grass or sitting on buildings. Before blaming your groundnet work, consider that the airport terrain/layout may be outdated or misplaced. Similarly, Building/Object may have been placed at certain Lat/Lon but since demolished to make space for a new taxiway as airports expand and change layout regularly.


Your candidate groundnet will need to be tested thoroughly by running it in FG, at different time of the day as wind conditions and traffic patterns will impact which runways are used and how many AI aircrafts are handled.  
Your candidate groundnet will need to be tested thoroughly by running it in FG, at different time of the day as wind conditions and traffic patterns will impact which runways are used and how many AI aircrafts are handled.  
86

edits

Navigation menu