AI Traffic: Difference between revisions

Jump to navigation Jump to search

AI Traffic (view source)

Revision as of 10:28, 25 January 2009

2,132 bytes removed ,  25 January 2009
no edit summary
(Major update of Taxidraw's groundnetwork editing capabilities part 2.)
No edit summary
Line 414: Line 414:
and runway, it will list which nodes are not connected and exit.
and runway, it will list which nodes are not connected and exit.


== Appendix: ==
== Appendix: Special Notes ==
An below is an example section from <tt>data/Airports/AI/EHAM/parking.xml</tt>


<?xml version="1.0"?>
=== Realism ===
<groundnet>
With [[FGFS 1.0.0]] Interactive Traffic also responds to other Non-AI aicraft.
  <parkinglist>
    <Parking index="0"
        type="cargo"
        name="R02"
        number="1"
        lat="N52 17.664"
        lon="E04 44.527"
        heading="328.8"
        radius="43"
        airlineCodes="NONE"
        pushBack="left"/>
    <Parking index="1"
        type="cargo"
        name="R04"
        number="1"
        lat="N52 17.682"
        lon="E04 44.572"
        heading="328.8"
        radius="43"
        airlineCodes="NONE"
        pushBack="left"/>
[SNIP]
    <Parking index="198"
        type="gate"
        name="J80"
        number="1"
        lat="N52 18.678"
        lon="E04 44.659"
        heading="0"
        radius="15"
        airlineCodes="NONE"
        pushBack="left"/>
  </parkinglist>
  <TaxiNodes>
    <node index="199" lat="N52 20.778" lon="E04 42.626" name="AI waypointnode"/>
    <node index="200" lat="N52 20.622" lon="E04 42.771" name="AI waypointnode"/>
    <node index="201" lat="N52 20.478" lon="E04 42.592" name="AI waypointnode"/>
    <node index="202" lat="N52 20.394" lon="E04 42.685" name="AI waypointnode"/>
    <node index="203" lat="N52 20.406" lon="E04 42.754" name="AI waypointnode"/>
    <node index="204" lat="N52 20.310" lon="E04 42.740" name="AI waypointnode"/>
    <node index="205" lat="N52 20.148" lon="E04 42.565" name="AI waypointnode"/>
[SNIP]...
    <node index="597" lat="N52 18.666" lon="E04 45.372" name="AI waypointnode"/>
    <node index="598" lat="N52 18.678" lon="E04 45.358" name="AI waypointnode"/>
    <node index="599" lat="N52 18.678" lon="E04 45.377" name="AI waypointnode"/>
  </TaxiNodes>
  <TaxiWaySegments>
    <arc begin="237" end="234" name="Route"/>
    <arc begin="234" end="239" name="Route"/>
    <arc begin="239" end="242" name="Route"/>
    <arc begin="242" end="245" name="Route"/>
    <arc begin="369" end="374" name="Route"/>
    <arc begin="374" end="369" name="Route"/>
    <arc begin="370" end="373" name="Route"/>
    <arc begin="373" end="370" name="Route"/>
  </TaxiWaySegments>
</groundnet>
 
== Realistic ==
With [[FGFS 1.0.0]] Interactive Traffic also reacts on other Non-AI Aicrafts.
The [[Airbus A320|A320]] ( and maybe some others) has working flaps and gears.
The [[Airbus A320|A320]] ( and maybe some others) has working flaps and gears.


==Perfomance==
===Perfomance===
With FGFS 1.0.0, the AI Interactive Traffic needs a lot of CPU-power. With the current CVS-versions, however, we now have much better performance so realistic density of traffic is currently possible, even for slower computers.
With FGFS 1.0.0, the AI Interactive Traffic needs a lot of CPU-power. With the current CVS-versions, however, we now have much better performance so realistic density of traffic is currently possible, even for slower computers.
For those who are still afraid, there is an, as of yet, unpublished feature:
For those who are still afraid, there is an, as of yet, unpublished feature:
Line 488: Line 427:
specified in /sim/traffic-manager/proportion, the aircraft is added, otherwise it is discarded. In essence, only the specified proportion of aircraft will be loaded.  
specified in /sim/traffic-manager/proportion, the aircraft is added, otherwise it is discarded. In essence, only the specified proportion of aircraft will be loaded.  


Unfortunately you can't change this at runtime yet, so you need a little bit trial and error! However, it should allow the combination of slower computers and dense traffic files. ;-)
Unfortunately you can't change this at runtime yet, so you need a little bit trial and error! However, it should allow the combination of slower computers and dense traffic files.


==External links==
==External links==
* [http://www.xs4all.nl/~dtalsma/flightgear.html The FlightGear AI aircraft download page]
* [http://www.xs4all.nl/~dtalsma/flightgear.html The FlightGear AI aircraft download page]
* [http://www.ilovelinux.de/svn/fgfs-ffm/user/data/AI/  Created  a dense AI traffic for EDDF, LSZH and a lot of other airports depending on real timetables. More to come!]
* [http://www.ilovelinux.de/svn/fgfs-ffm/user/data/AI/  Created  a dense AI traffic for EDDF, LSZH and a lot of other airports depending on real timetables. More to come!]
Durk
117

edits

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

Navigation menu