1
0
Fork 0
Commit graph

9 commits

Author SHA1 Message Date
ehofman
bebf0c0096 Reorganize the demo scenario's and FlightPlans to get to a better default scenario for KSFO. 2004-07-01 14:15:09 +00:00
ehofman
b68fc03f68 Add a Thermal and a Refualling scenario 2004-06-25 11:14:57 +00:00
ehofman
957cd9a0b8 Add the AIModel based air traffic subsystem from Durk Talsma. 2004-06-03 17:59:05 +00:00
ehofman
9601588447 Add the matching scenario file. 2004-05-29 12:09:54 +00:00
ehofman
706a64041a David Culp:
1.  Removed aircraft roll on ground.
2.  Decreased descent pitch angle.
3.  Updated flightplans to include <on-ground>
4.  Fixed property indexing, so all AI aircraft have their own property branch


The default value of <on-ground> is false, so you only need to specify it when
on the ground.  For takeoff you need to specify <on-ground>true</on-ground>
for the first waypoint, and for the acceleration waypoint.  For landing you
need to specify it for the touchdown point and any taxi points.
2004-05-21 16:51:05 +00:00
ehofman
2afaa933e3 David Culp:
First, preferences.xml will define the scenario filename.

For now, the other way of defining ai objects still works, so the sailboat
stays in preferences.xml.  Later, I'll move the sailboat into the demo
scenario.  If no scenario filename is given, then no scenario will be
processed.

I changed the demo scenario to create two 737's, one takes off on runway 01L,
and the other takes off on runway 01R.  This will make a good demo for the ai
system.  One problem, if you takeoff on 28L/R right away, you might run into
the taking-off 737's, or be scared.
2004-05-17 08:46:34 +00:00
ehofman
e70eef10ac Remove two more capital tags. 2004-05-15 13:01:26 +00:00
ehofman
54a870d14b Use lower case letters instead. 2004-05-15 12:46:42 +00:00
ehofman
ef5748a00e David Culp:
Here's the newest AI stuff.

The AIManager at init() creates a new scenario.  Right now the
default_scenario is hard coded in, but eventually the AIManager should get
the scenario filename from preferences.xml.

The scenario defines which AI objects will be created.  Right now it only
creates AIAircraft, but this is easily extended.  The scenario also defines
which flightplan will be assigned to the airplane.  Scenario config files go
in data/Data/AI.

The Airplane gets a pointer to a FlightPlan object.  Each airplane should get
its own flightplan object, even if two airplanes have the same flight plan.
This is because  the flightplan maintains the iterator pointing to the
current waypoint, and two airplanes might be at different locations (for
instance if they were created at different times).  The flight plan files go
in data/Data/AI/FlightPlans.

When the airplane gets to the waypoint named "END" it vanishes.  The
AIAircraft destructor deletes its flight plan (if it has one).

The last waypoint is a place holder only.  I called mine
<WPT><NAME>"EOF"</NAME></WPT>.
2004-05-15 09:07:56 +00:00