fly/fgdata
1
0
Fork 0
Code Activity
fgdata/Data/AI/aircraft_demo.xml

35 lines
972 B
XML
Raw Normal View History

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
<?xml version="1.0"?>
Reorganize the demo scenario's and FlightPlans to get to a better default scenario for KSFO.
2004-07-01 14:15:09 +00:00
David Culp: I was going through the Ai scenarios and see that some of them are not necessary. Also, I've added some documentation to the other scenarios. And I moved the thunderstorm over San Francisco, so you don't have to take off to see it. The files are attached.
2005-04-29 07:57:24 +00:00
<!-- Notes:
This scenario has a 737 takeoff from runway 28L at KSFO
and fly the Porte Departure to the south. You can change
the aircraft type by substituting another model in the
<model> tag, and you can also change the "flight plan" by
changing the <flightplan> tag. Look in the subdirectory
FlightPlans to find some that I've already defined, including
David Culp: just add the new <repeat> capability.
2005-10-27 08:29:07 +00:00
some arrivals. Normally, when an AI aircraft gets to the end
of its flight plan it deletes itself, however the
<repeat>1</repeat> tag will cause the AI aircraft to start again
indefinitely.
David Culp: I was going through the Ai scenarios and see that some of them are not necessary. Also, I've added some documentation to the other scenarios. And I moved the thunderstorm over San Francisco, so you don't have to take off to see it. The files are attached.
2005-04-29 07:57:24 +00:00
Dave Culp, davidculp2@comcast.net
-->
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
<PropertyList>
Use lower case letters instead.
2004-05-15 12:46:42 +00:00
<scenario>
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
Use lower case letters instead.
2004-05-15 12:46:42 +00:00
<entry>
Reorganize the demo scenario's and FlightPlans to get to a better default scenario for KSFO.
2004-07-01 14:15:09 +00:00
<callsign>United 720</callsign>
<type>aircraft</type>
<class>jet_transport</class>
Use lower case letters instead.
2004-05-15 12:46:42 +00:00
<model>Aircraft/737/Models/boeing733.xml</model>
Reorganize the demo scenario's and FlightPlans to get to a better default scenario for KSFO.
2004-07-01 14:15:09 +00:00
<flightplan>KSFO_depart_south_28L.xml</flightplan>
David Culp: just add the new <repeat> capability.
2005-10-27 08:29:07 +00:00
<repeat>1</repeat>
Use lower case letters instead.
2004-05-15 12:46:42 +00:00
</entry>
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
Use lower case letters instead.
2004-05-15 12:46:42 +00:00
</scenario>
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
</PropertyList>
Copy permalink