fly/flightgear
1
0
Fork 0
Code Activity
flightgear/src/AIModel/Makefile.am

20 lines
560 B
Text
Raw Normal View History

Add David Culp's AI model manager code which is derived from David Luff's AI/ATC code.
2003-11-28 15:48:05 +00:00
noinst_LIBRARIES = libAIModel.a
Code cleanup of AIModels (mainly AIAircraft), by Thomas Foerster
2007-06-09 11:49:16 +00:00
libAIModel_a_SOURCES = submodel.cxx submodel.hxx \
Add David Culp's AI model manager code which is derived from David Luff's AI/ATC code.
2003-11-28 15:48:05 +00:00
AIManager.hxx AIManager.cxx \
AIBase.hxx AIBase.cxx \
Code cleanup of AIModels (mainly AIAircraft), by Thomas Foerster
2007-06-09 11:49:16 +00:00
AIAircraft.hxx AIAircraft.cxx AIMultiplayer.hxx \
AIMultiplayer.cxx \
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:55 +00:00
AIShip.hxx AIShip.cxx \
AIBallistic.hxx AIBallistic.cxx \
Put the AIStorm and AIThermal classes back in
2004-03-03 20:26:06 +00:00
AIStorm.hxx AIStorm.cxx \
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:55 +00:00
AIThermal.hxx AIThermal.cxx \
AI Modifications: 1) Added a patch that takes ground speed into consideration using Curt's new speed adjustment code. 2) Separated the function FlightPlanCreateCruise() into a new source file in preparation of a more elaborate airway following scheme.
2006-07-27 14:42:15 +00:00
AIFlightPlan.hxx AIFlightPlan.cxx \
Code cleanup of AIModels (mainly AIAircraft), by Thomas Foerster
2007-06-09 11:49:16 +00:00
AIFlightPlanCreate.cxx \
AIFlightPlanCreateCruise.cxx \
AICarrier.hxx AICarrier.cxx \
AIStatic.hxx AIStatic.cxx \
AITanker.cxx AITanker.hxx
Add David Culp's AI model manager code which is derived from David Luff's AI/ATC code.
2003-11-28 15:48:05 +00:00
INCLUDES = -I$(top_srcdir) -I$(top_srcdir)/src
Copy permalink