fly/flightgear
1
0
Fork 0
Code Activity
flightgear/src/Systems/submodel.hxx

95 lines
2.2 KiB
C++
Raw Normal View History

David Culp: Right now the code is not very configurable, and there is only one submodel per airplane possible. It is implemented as an SGSubSystem, just like the electrics, vacuum, etc. systems. To make it work you need to make a release binding like this (for my joystick trigger): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then, each airplane that uses the system should have something like this added to its *-set.xml file (note that this does *not* go within the <sim></sim> tags): <systems> <submodel> <serviceable type="bool">true</serviceable> <amount type="int">70</amount> </submodel> </systems> Future improvements will include: 1) more configurability, so the user can create multiple submodels, and can assign them different locations, and pitch and yaw adjustments, and nitial velocity. 2) sound? 3) a more accurate calculation of the submodels location at any pitch/roll/yaw. 4) a way to pre-load the model, so the AI code doesn't have to parse the model every time it creates an instance. I think that's all of it.
2004-08-22 16:22:18 +00:00
// submodel.hxx - models a releasable submodel.
// Written by Dave Culp, started Aug 2004
//
// This file is in the Public Domain and comes with no warranty.
#ifndef __SYSTEMS_SUBMODEL_HXX
#define __SYSTEMS_SUBMODEL_HXX 1
#ifndef __cplusplus
# error This library requires C++
#endif
#include <simgear/props/props.hxx>
#include <simgear/structure/subsystem_mgr.hxx>
#include <AIModel/AIManager.hxx>
David Culp: Here is an update for the submodel system. This will allow submodels to be defined for any aircraft, and there are no default submodels. To use this submodel system you need to set up a binding (slight change in property name from last one, but you can use any property name you like, as long as it matches the name in the submodels.xml file, see below): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then in your *-set.xml file you need to define a path to the configuration file (similar to the way the electrical system is now done): <sim> ... <systems> <electrical> <path>Aircraft/Generic/generic-electrical.xml</path> </electrical> <submodels> <serviceable type="bool">true</serviceable> <path>Aircraft/FW190/submodels.xml</path> </submodels> </systems> ... </sim> Then you put the submodel configuration file in your aircraft's directory. I've attached a file, submodels.xml, that can be used to define a gun that works just like the former one did. There are two things remaining to be done. One is to change the function SubmodelSystem::transform() to properly position the submodel. This will require some complicated matrix code that I might borrow from Yasim.
2004-08-26 08:38:43 +00:00
#include <vector>
#include <string>
SG_USING_STD(vector);
SG_USING_STD(string);
David Culp: Right now the code is not very configurable, and there is only one submodel per airplane possible. It is implemented as an SGSubSystem, just like the electrics, vacuum, etc. systems. To make it work you need to make a release binding like this (for my joystick trigger): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then, each airplane that uses the system should have something like this added to its *-set.xml file (note that this does *not* go within the <sim></sim> tags): <systems> <submodel> <serviceable type="bool">true</serviceable> <amount type="int">70</amount> </submodel> </systems> Future improvements will include: 1) more configurability, so the user can create multiple submodels, and can assign them different locations, and pitch and yaw adjustments, and nitial velocity. 2) sound? 3) a more accurate calculation of the submodels location at any pitch/roll/yaw. 4) a way to pre-load the model, so the AI code doesn't have to parse the model every time it creates an instance. I think that's all of it.
2004-08-22 16:22:18 +00:00
class SubmodelSystem : public SGSubsystem
{
public:
David Culp: Here is an update for the submodel system. This will allow submodels to be defined for any aircraft, and there are no default submodels. To use this submodel system you need to set up a binding (slight change in property name from last one, but you can use any property name you like, as long as it matches the name in the submodels.xml file, see below): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then in your *-set.xml file you need to define a path to the configuration file (similar to the way the electrical system is now done): <sim> ... <systems> <electrical> <path>Aircraft/Generic/generic-electrical.xml</path> </electrical> <submodels> <serviceable type="bool">true</serviceable> <path>Aircraft/FW190/submodels.xml</path> </submodels> </systems> ... </sim> Then you put the submodel configuration file in your aircraft's directory. I've attached a file, submodels.xml, that can be used to define a gun that works just like the former one did. There are two things remaining to be done. One is to change the function SubmodelSystem::transform() to properly position the submodel. This will require some complicated matrix code that I might borrow from Yasim.
2004-08-26 08:38:43 +00:00
typedef struct {
SGPropertyNode_ptr trigger;
Tie the count into the property tree instead of using snprintf every frame. Add the life-timer to the property tree under sim/time/elapsed-sec for AI object animation (blending and/or scaling).
2004-08-30 11:13:29 +00:00
SGPropertyNode_ptr prop;
David Culp: Here is an update for the submodel system. This will allow submodels to be defined for any aircraft, and there are no default submodels. To use this submodel system you need to set up a binding (slight change in property name from last one, but you can use any property name you like, as long as it matches the name in the submodels.xml file, see below): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then in your *-set.xml file you need to define a path to the configuration file (similar to the way the electrical system is now done): <sim> ... <systems> <electrical> <path>Aircraft/Generic/generic-electrical.xml</path> </electrical> <submodels> <serviceable type="bool">true</serviceable> <path>Aircraft/FW190/submodels.xml</path> </submodels> </systems> ... </sim> Then you put the submodel configuration file in your aircraft's directory. I've attached a file, submodels.xml, that can be used to define a gun that works just like the former one did. There are two things remaining to be done. One is to change the function SubmodelSystem::transform() to properly position the submodel. This will require some complicated matrix code that I might borrow from Yasim.
2004-08-26 08:38:43 +00:00
string name;
string model;
double speed;
bool slaved;
bool repeat;
double delay;
double timer;
int count;
double x_offset;
double y_offset;
double z_offset;
double yaw_offset;
double pitch_offset;
David Culp: Silly me. I was starting the timer at zero, so the first tracer didn't fly until 0.25 seconds after pulling the trigger. Now the timer starts at the same value as "delay", so the first round comes out immediately. Also, I've added an optional configuration attribute that allows you to change the ballistics of the submodel. This allows parachutes, or anything else that has ballistics different from a bullet. The attribute is called "eda", which is the equivalent drag area. Default value is 0.007, which gives the same ballistics as the current tracers. Increasing this value gives more drag. A value of 2.0 looks good for a parachute. math stuff ######################################################################## The deceleration of the ballictic object is now given by: [ (rho) (Cd) ] / [ (1/2) (m) ] * A * (V * V) where rho is sea-level air density, and Cd and m are fixed, bullet-like values. So the calculation is: 0.0116918 * A * (V * V) The value "A" is what I'm calling the "eda" (equivalent drag area). ######################################################################## A parachute model will have to be built so that the parachutist's feet are in the forward x-direction. Here is the submodel.xml config I use for "parachutes": <submodel> <name>flares</name> <model>Models/Geometry/flare.ac</model> <trigger>systems/submodels/submodel[0]/trigger</trigger> <speed>0.0</speed> <repeat>true</repeat> <delay>0.85</delay> <count>4</count> <x-offset>0.0</x-offset> <y-offset>0.0</y-offset> <z-offset>-4.0</z-offset> <yaw-offset>0.0</yaw-offset> <pitch-offset>0.0</pitch-offset> <eda>2.0</eda> </submodel>
2004-08-26 16:25:54 +00:00
double drag_area;
David Culp: Here are small changes that allow one to set a life-span for submodels.
2004-08-30 09:11:59 +00:00
double life;
David Culp: Here is an update for the submodel system. This will allow submodels to be defined for any aircraft, and there are no default submodels. To use this submodel system you need to set up a binding (slight change in property name from last one, but you can use any property name you like, as long as it matches the name in the submodels.xml file, see below): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then in your *-set.xml file you need to define a path to the configuration file (similar to the way the electrical system is now done): <sim> ... <systems> <electrical> <path>Aircraft/Generic/generic-electrical.xml</path> </electrical> <submodels> <serviceable type="bool">true</serviceable> <path>Aircraft/FW190/submodels.xml</path> </submodels> </systems> ... </sim> Then you put the submodel configuration file in your aircraft's directory. I've attached a file, submodels.xml, that can be used to define a gun that works just like the former one did. There are two things remaining to be done. One is to change the function SubmodelSystem::transform() to properly position the submodel. This will require some complicated matrix code that I might borrow from Yasim.
2004-08-26 08:38:43 +00:00
} submodel;
typedef struct {
double lat;
double lon;
double alt;
double azimuth;
double elevation;
double speed;
} IC_struct;
David Culp: Right now the code is not very configurable, and there is only one submodel per airplane possible. It is implemented as an SGSubSystem, just like the electrics, vacuum, etc. systems. To make it work you need to make a release binding like this (for my joystick trigger): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then, each airplane that uses the system should have something like this added to its *-set.xml file (note that this does *not* go within the <sim></sim> tags): <systems> <submodel> <serviceable type="bool">true</serviceable> <amount type="int">70</amount> </submodel> </systems> Future improvements will include: 1) more configurability, so the user can create multiple submodels, and can assign them different locations, and pitch and yaw adjustments, and nitial velocity. 2) sound? 3) a more accurate calculation of the submodels location at any pitch/roll/yaw. 4) a way to pre-load the model, so the AI code doesn't have to parse the model every time it creates an instance. I think that's all of it.
2004-08-22 16:22:18 +00:00
SubmodelSystem ();
~SubmodelSystem ();
David Culp: Here is an update for the submodel system. This will allow submodels to be defined for any aircraft, and there are no default submodels. To use this submodel system you need to set up a binding (slight change in property name from last one, but you can use any property name you like, as long as it matches the name in the submodels.xml file, see below): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then in your *-set.xml file you need to define a path to the configuration file (similar to the way the electrical system is now done): <sim> ... <systems> <electrical> <path>Aircraft/Generic/generic-electrical.xml</path> </electrical> <submodels> <serviceable type="bool">true</serviceable> <path>Aircraft/FW190/submodels.xml</path> </submodels> </systems> ... </sim> Then you put the submodel configuration file in your aircraft's directory. I've attached a file, submodels.xml, that can be used to define a gun that works just like the former one did. There are two things remaining to be done. One is to change the function SubmodelSystem::transform() to properly position the submodel. This will require some complicated matrix code that I might borrow from Yasim.
2004-08-26 08:38:43 +00:00
void load ();
David Culp: Right now the code is not very configurable, and there is only one submodel per airplane possible. It is implemented as an SGSubSystem, just like the electrics, vacuum, etc. systems. To make it work you need to make a release binding like this (for my joystick trigger): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then, each airplane that uses the system should have something like this added to its *-set.xml file (note that this does *not* go within the <sim></sim> tags): <systems> <submodel> <serviceable type="bool">true</serviceable> <amount type="int">70</amount> </submodel> </systems> Future improvements will include: 1) more configurability, so the user can create multiple submodels, and can assign them different locations, and pitch and yaw adjustments, and nitial velocity. 2) sound? 3) a more accurate calculation of the submodels location at any pitch/roll/yaw. 4) a way to pre-load the model, so the AI code doesn't have to parse the model every time it creates an instance. I think that's all of it.
2004-08-22 16:22:18 +00:00
void init ();
void bind ();
void unbind ();
void update (double dt);
David Culp: Here is an update for the submodel system. This will allow submodels to be defined for any aircraft, and there are no default submodels. To use this submodel system you need to set up a binding (slight change in property name from last one, but you can use any property name you like, as long as it matches the name in the submodels.xml file, see below): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then in your *-set.xml file you need to define a path to the configuration file (similar to the way the electrical system is now done): <sim> ... <systems> <electrical> <path>Aircraft/Generic/generic-electrical.xml</path> </electrical> <submodels> <serviceable type="bool">true</serviceable> <path>Aircraft/FW190/submodels.xml</path> </submodels> </systems> ... </sim> Then you put the submodel configuration file in your aircraft's directory. I've attached a file, submodels.xml, that can be used to define a gun that works just like the former one did. There are two things remaining to be done. One is to change the function SubmodelSystem::transform() to properly position the submodel. This will require some complicated matrix code that I might borrow from Yasim.
2004-08-26 08:38:43 +00:00
bool release (submodel* sm, double dt);
void transform (submodel* sm);
David Culp: Right now the code is not very configurable, and there is only one submodel per airplane possible. It is implemented as an SGSubSystem, just like the electrics, vacuum, etc. systems. To make it work you need to make a release binding like this (for my joystick trigger): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then, each airplane that uses the system should have something like this added to its *-set.xml file (note that this does *not* go within the <sim></sim> tags): <systems> <submodel> <serviceable type="bool">true</serviceable> <amount type="int">70</amount> </submodel> </systems> Future improvements will include: 1) more configurability, so the user can create multiple submodels, and can assign them different locations, and pitch and yaw adjustments, and nitial velocity. 2) sound? 3) a more accurate calculation of the submodels location at any pitch/roll/yaw. 4) a way to pre-load the model, so the AI code doesn't have to parse the model every time it creates an instance. I think that's all of it.
2004-08-22 16:22:18 +00:00
private:
David Culp: Here is an update for the submodel system. This will allow submodels to be defined for any aircraft, and there are no default submodels. To use this submodel system you need to set up a binding (slight change in property name from last one, but you can use any property name you like, as long as it matches the name in the submodels.xml file, see below): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then in your *-set.xml file you need to define a path to the configuration file (similar to the way the electrical system is now done): <sim> ... <systems> <electrical> <path>Aircraft/Generic/generic-electrical.xml</path> </electrical> <submodels> <serviceable type="bool">true</serviceable> <path>Aircraft/FW190/submodels.xml</path> </submodels> </systems> ... </sim> Then you put the submodel configuration file in your aircraft's directory. I've attached a file, submodels.xml, that can be used to define a gun that works just like the former one did. There are two things remaining to be done. One is to change the function SubmodelSystem::transform() to properly position the submodel. This will require some complicated matrix code that I might borrow from Yasim.
2004-08-26 08:38:43 +00:00
typedef vector <submodel*> submodel_vector_type;
typedef submodel_vector_type::iterator submodel_vector_iterator;
submodel_vector_type submodels;
submodel_vector_iterator submodel_iterator;
David Culp: Right now the code is not very configurable, and there is only one submodel per airplane possible. It is implemented as an SGSubSystem, just like the electrics, vacuum, etc. systems. To make it work you need to make a release binding like this (for my joystick trigger): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then, each airplane that uses the system should have something like this added to its *-set.xml file (note that this does *not* go within the <sim></sim> tags): <systems> <submodel> <serviceable type="bool">true</serviceable> <amount type="int">70</amount> </submodel> </systems> Future improvements will include: 1) more configurability, so the user can create multiple submodels, and can assign them different locations, and pitch and yaw adjustments, and nitial velocity. 2) sound? 3) a more accurate calculation of the submodels location at any pitch/roll/yaw. 4) a way to pre-load the model, so the AI code doesn't have to parse the model every time it creates an instance. I think that's all of it.
2004-08-22 16:22:18 +00:00
double x_offset, y_offset, z_offset;
double pitch_offset, yaw_offset;
SGPropertyNode_ptr _serviceable_node;
SGPropertyNode_ptr _user_lat_node;
SGPropertyNode_ptr _user_lon_node;
SGPropertyNode_ptr _user_heading_node;
SGPropertyNode_ptr _user_alt_node;
SGPropertyNode_ptr _user_pitch_node;
SGPropertyNode_ptr _user_roll_node;
SGPropertyNode_ptr _user_yaw_node;
SGPropertyNode_ptr _user_speed_node;
FGAIManager* ai;
David Culp: Here is an update for the submodel system. This will allow submodels to be defined for any aircraft, and there are no default submodels. To use this submodel system you need to set up a binding (slight change in property name from last one, but you can use any property name you like, as long as it matches the name in the submodels.xml file, see below): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodels/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then in your *-set.xml file you need to define a path to the configuration file (similar to the way the electrical system is now done): <sim> ... <systems> <electrical> <path>Aircraft/Generic/generic-electrical.xml</path> </electrical> <submodels> <serviceable type="bool">true</serviceable> <path>Aircraft/FW190/submodels.xml</path> </submodels> </systems> ... </sim> Then you put the submodel configuration file in your aircraft's directory. I've attached a file, submodels.xml, that can be used to define a gun that works just like the former one did. There are two things remaining to be done. One is to change the function SubmodelSystem::transform() to properly position the submodel. This will require some complicated matrix code that I might borrow from Yasim.
2004-08-26 08:38:43 +00:00
IC_struct IC;
David Culp: Right now the code is not very configurable, and there is only one submodel per airplane possible. It is implemented as an SGSubSystem, just like the electrics, vacuum, etc. systems. To make it work you need to make a release binding like this (for my joystick trigger): <button n="0"> <desc>Trigger</desc> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">true</value> </binding> <mod-up> <binding> <command>property-assign</command> <property>/systems/submodel/trigger</property> <value type="bool">false</value> </binding> </mod-up> </button> Then, each airplane that uses the system should have something like this added to its *-set.xml file (note that this does *not* go within the <sim></sim> tags): <systems> <submodel> <serviceable type="bool">true</serviceable> <amount type="int">70</amount> </submodel> </systems> Future improvements will include: 1) more configurability, so the user can create multiple submodels, and can assign them different locations, and pitch and yaw adjustments, and nitial velocity. 2) sound? 3) a more accurate calculation of the submodels location at any pitch/roll/yaw. 4) a way to pre-load the model, so the AI code doesn't have to parse the model every time it creates an instance. I think that's all of it.
2004-08-22 16:22:18 +00:00
};
#endif // __SYSTEMS_SUBMODEL_HXX
Copy permalink