AI Traffic: Difference between revisions

Jump to navigation Jump to search

AI Traffic (view source)

Revision as of 00:27, 17 July 2020

324 bytes removed ,  17 July 2020
no edit summary
No edit summary
No edit summary
Line 10: Line 10:


== Traffic Files Location ==
== Traffic Files Location ==
Traffic patterns are stored in data files in extended markup language (.xml) format. The actual location of these files are version dependent.
Traffic patterns are stored as data files in extended markup language (.xml) format. The actual location of these files are version dependent.
* FlightGear 0.9.x : <tt>[[$FG ROOT]]/Traffic/</tt>
* FlightGear 0.9.x : <tt>[[$FG ROOT]]/Traffic/</tt>
* FlightGear 1.0 : <tt>[[$FG ROOT]]/AI/Aircraft/</tt>
* FlightGear 1.0 : <tt>[[$FG ROOT]]/AI/Aircraft/</tt>
Line 17: Line 17:
Traffic is organised by Operator in subfolders, using the initial of the operator's ICAO designator. For example, traffic for United Airlines is stored under <tt>[[$FG ROOT]]/AI/Traffic/U/UAL.xml</tt>
Traffic is organised by Operator in subfolders, using the initial of the operator's ICAO designator. For example, traffic for United Airlines is stored under <tt>[[$FG ROOT]]/AI/Traffic/U/UAL.xml</tt>


== TrafficManager, Aircraft, and Flights ==
A new traffic file format was introduced with FlightGear 1.9.0, referred to as "Traffic Manager II" format (TM-II), in which aircraft and flights are no longer directly coupled, leading to more flexibility.  
A new traffic file format was introduced with FlightGear 1.9.0, referred to as "Traffic Manager II" format (TM-II), in which aircraft and flights are no longer directly coupled, leading to more flexibility.  
Each traffic pattern is built around two entities: Aircraft and Flights. Before discussing the details, lets start by exploring these two concepts a little further.


== Some Details: TrafficManager, Aircraft, and Flights ==
Traffic pattern are built around two separate entities: Aircraft and Operated Flights.
As in real life, AI traffic in FlightGear is centered around aircraft. In real life, a commercial airliner is put to use by operating on a series of scheduled flights, on a daily or weekly basis. Take for example the long haul routes that are flown by [[McDonnell Douglas MD11]] aircraft. For instance, the MD11's operated by KLM fly regularly between Amsterdam and various distant destinations, such as San Fransisco or Minneapolis in the United States, Vancouver or Montreal in Canada, Accra and Lagos in Africa, or New Delhi in India. Some of these routes are too long to complete a return flight in one day, such as the trip between Amsterdam and San Fransisco, which is basically an 11-hour flight one-way. So it would take 22 hours of just the flying time, and at least an additional two hour turn-around time at each airport. Therefore, in real-life, it is necessary to operate this aircraft on a series of routes, because other routes are considerably shorter than the trip to San Fransisco. Therefore, the time lost on one route can be gained on another, averaging out to approximately one round-trip a day.  
Commercial aviation, in FlightGear and in real life is centered around aircrafts with commercial airliners being used to operate a series of scheduled flights, on a daily or weekly basis. For example, the [[McDonnell Douglas MD11]] operated by KLM flies regularly between Amsterdam and various distant destinations, such as San Francisco or Minneapolis in the United States, Vancouver or Montreal in Canada, Accra and Lagos in Africa, or New Delhi in India. Some of these routes are too long for a return flight to be achieved within a 24h00 day when you account for the turn around time at each airport. As a result, in real-life, this aircraft will be operating a series of flights on multiple routes; given some routes in the series are shorter than the trip to San Francisco, the time lost on one route can be gained on another, averaging the aircraft use to one round-trip a day.


In FlightGear, we wouldn't have to be so strictly considerate about the turnaround times as a real-world airline would, but in the not-so distant future, we also want to be able to see realisticly crowded terminals at our simulated airports, so considering the turnaround time in the schedules is a good thing. Therefore, most of the long-haul aircraft will need to be scheduled to fly more than one route. Hence, each AI aircraft has one or more routes assigned to it, which repeat on a weekly, daily, or hourly basis.  
In FlightGear, we wouldn't have to be so strictly considerate about the turnaround times as a real-world airline would, but in the not-so distant future, we also want to be able to see realisticly crowded terminals at our simulated airports, so considering the turnaround time in the schedules is a good thing. Therefore, most of the long-haul aircraft will need to be scheduled to fly more than one route. Hence, each AI aircraft has one or more routes assigned to it, which repeat on a weekly, daily, or hourly basis.  
BecOzIcan
86

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/126380"

Navigation menu