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

169 lines
4.4 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>
Make use of a pointer to a structure to pass multiple parameters around.
2004-09-07 09:53:23 +00:00
#include <AIModel/AIBase.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
Vivian MEAZZA: """ "Flight plans" which can start at a given time (gmt) WAITUNTIL tokens which pause the flight plans until a given time (gmt) Submodels can now be attached to any AI objects (except submodels - it can be done, but in my experimental code it's too expensive in frame rate atm) "No-roll" attribute added to Ballistic objects - useful for wakes and the like "Random" attribute added to Ballistic objects (adds =- 5% to the Cd) - useful for smoke, exhausts If the <trigger> tag is not specified the Ballistic object/s will be released at start-up (cannot be stopped) Submodels are not released from AI Objects if the AI Object is more than 15 miles away. """ mf: minor code and formatting fixes; submodels.?xx were FUBAR and are thus astyle formatted; NOTE that <name> tags END, EOF, WAIT, WAITUNTIL are *depreciated*. Don't get too used to them. This will have to be moved from the "name" to regular engries.
2007-03-30 22:51:52 +00:00
class FGAIBase;
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
Move the submodels code from the Systems manager into it's own Subsystem manager.
2004-10-22 09:58:24 +00:00
class FGSubmodelMgr : public SGSubsystem
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
{
public:
Vivian MEAZZA: """ "Flight plans" which can start at a given time (gmt) WAITUNTIL tokens which pause the flight plans until a given time (gmt) Submodels can now be attached to any AI objects (except submodels - it can be done, but in my experimental code it's too expensive in frame rate atm) "No-roll" attribute added to Ballistic objects - useful for wakes and the like "Random" attribute added to Ballistic objects (adds =- 5% to the Cd) - useful for smoke, exhausts If the <trigger> tag is not specified the Ballistic object/s will be released at start-up (cannot be stopped) Submodels are not released from AI Objects if the AI Object is more than 15 miles away. """ mf: minor code and formatting fixes; submodels.?xx were FUBAR and are thus astyle formatted; NOTE that <name> tags END, EOF, WAIT, WAITUNTIL are *depreciated*. Don't get too used to them. This will have to be moved from the "name" to regular engries.
2007-03-30 22:51:52 +00:00
typedef struct
{
SGPropertyNode_ptr trigger_node;
SGPropertyNode_ptr prop;
SGPropertyNode_ptr contents_node;
SGPropertyNode_ptr submodel_node;
SGPropertyNode_ptr speed_node;
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;
double drag_area;
double life;
double buoyancy;
bool wind;
bool first_time;
double cd;
double weight;
double contents;
bool aero_stabilised;
int id;
bool no_roll;
bool serviceable;
}
submodel;
typedef struct
{
double lat;
double lon;
double alt;
double roll;
double azimuth;
double elevation;
double speed;
double wind_from_east;
double wind_from_north;
double speed_down_fps;
double speed_east_fps;
double speed_north_fps;
double total_speed_down;
double total_speed_east;
double total_speed_north;
double mass;
int id;
bool no_roll;
}
IC_struct;
FGSubmodelMgr();
~FGSubmodelMgr();
void load();
void init();
Vivian MEAZZA: "BUGFIX - fix initiation order - make sure that the AI Model list is populated before we attempt to attach submodels."
2007-04-27 11:02:39 +00:00
void postinit();
Vivian MEAZZA: """ "Flight plans" which can start at a given time (gmt) WAITUNTIL tokens which pause the flight plans until a given time (gmt) Submodels can now be attached to any AI objects (except submodels - it can be done, but in my experimental code it's too expensive in frame rate atm) "No-roll" attribute added to Ballistic objects - useful for wakes and the like "Random" attribute added to Ballistic objects (adds =- 5% to the Cd) - useful for smoke, exhausts If the <trigger> tag is not specified the Ballistic object/s will be released at start-up (cannot be stopped) Submodels are not released from AI Objects if the AI Object is more than 15 miles away. """ mf: minor code and formatting fixes; submodels.?xx were FUBAR and are thus astyle formatted; NOTE that <name> tags END, EOF, WAIT, WAITUNTIL are *depreciated*. Don't get too used to them. This will have to be moved from the "name" to regular engries.
2007-03-30 22:51:52 +00:00
void bind();
void unbind();
void update(double dt);
bool release(submodel* sm, double dt);
void transform(submodel* sm);
void updatelat(double lat);
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;
Alex Romosan: I tried to make sure accessor functions which return by reference act on const objects. also replaced some iterators with const_iterator and a few return/pass by reference that were missed the first time around.
2005-10-26 09:03:49 +00:00
typedef submodel_vector_type::const_iterator submodel_vector_iterator;
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_vector_type submodels;
submodel_vector_iterator submodel_iterator;
Vivian Meazza: Testing revealed that the code was not reading y-offset - a typo in the original code, and roll was in the wrong sense. All readily fixable, and it now works.
2004-09-07 19:10:10 +00:00
float trans[3][3];
float in[3];
float out[3];
double Rx, Ry, Rz;
double Sx, Sy, Sz;
double Tx, Ty, Tz;
float cosRx, sinRx;
float cosRy, sinRy;
float cosRz, sinRz;
Vivian MEAZZA: """ "Flight plans" which can start at a given time (gmt) WAITUNTIL tokens which pause the flight plans until a given time (gmt) Submodels can now be attached to any AI objects (except submodels - it can be done, but in my experimental code it's too expensive in frame rate atm) "No-roll" attribute added to Ballistic objects - useful for wakes and the like "Random" attribute added to Ballistic objects (adds =- 5% to the Cd) - useful for smoke, exhausts If the <trigger> tag is not specified the Ballistic object/s will be released at start-up (cannot be stopped) Submodels are not released from AI Objects if the AI Object is more than 15 miles away. """ mf: minor code and formatting fixes; submodels.?xx were FUBAR and are thus astyle formatted; NOTE that <name> tags END, EOF, WAIT, WAITUNTIL are *depreciated*. Don't get too used to them. This will have to be moved from the "name" to regular engries.
2007-03-30 22:51:52 +00:00
int index;
Vivian Meazza: Testing revealed that the code was not reading y-offset - a typo in the original code, and roll was in the wrong sense. All readily fixable, and it now works.
2004-09-07 19:10:10 +00:00
double ft_per_deg_longitude;
double ft_per_deg_latitude;
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
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;
Vivian Meazza: I have added <Cd> and <weight> to the input parameters in the submodels.xml script. Raw data may be used, thus avoiding the need to guestimate <eda>. Eda remains, but should now be used to enter the proper cross-sectional area.
2004-09-22 08:47:05 +00:00
static const double lbs_to_slugs; //conversion factor
David Culp: Here are files to get automated contrails working. I've set up contrails for the 737, using my simple, untextured contrail model. Vivian has made another contrail model, but I'm still trying to get his to work. I'm hoping others will try to make contrail models also. Here's some code that defines a top to thermals. When the top of a thermal is reached the strength is phased-out linearly over the next 100 feet of altitude. At first I tried just capping the thermal at the top, but the change in thermal strength was too fast for the FDM to handle well. Included is a new version of the thermal scenario that includes a top (height-msl) to the thermal. The default value is 5000 feet.
2004-11-07 14:46:21 +00:00
double contrail_altitude;
fix another crash on exit by finally converting the rest of unguarded SGPropertyNode to guarded ones. This is also done for JSBSim/JSBSim.hxx, for which JSB had given explicit permission a while ago. I postponed that back then, but now is the time.
2006-06-11 10:21:10 +00:00
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_alpha_node;
SGPropertyNode_ptr _user_speed_node;
SGPropertyNode_ptr _user_wind_from_east_node;
SGPropertyNode_ptr _user_wind_from_north_node;
SGPropertyNode_ptr _user_speed_down_fps_node;
SGPropertyNode_ptr _user_speed_east_fps_node;
SGPropertyNode_ptr _user_speed_north_fps_node;
SGPropertyNode_ptr _contrail_altitude_node;
SGPropertyNode_ptr _contrail_trigger;
Vivian Meazza: I have added <Cd> and <weight> to the input parameters in the submodels.xml script. Raw data may be used, thus avoiding the need to guestimate <eda>. Eda remains, but should now be used to enter the proper cross-sectional area.
2004-09-22 08:47:05 +00:00
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
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: Here are some things I've added to the submodel code. First, I added a first_time value that is true when the trigger is pressed and false when the trigger is released. The true value is also made false after the first pass through release(). Release() then uses this to force the first dt (per salvo) to be zero. I was hoping this would make the submodel appear closer to the airplane, but I don't notice a difference with the tracers. In a prior test I found that the first dt is about 2.5 times larger than subsequent ones. Maybe this will be effective with slower submodels, like smoke, contrails, etc. Secondly, I updated the IC.elevation and IC.azimuth calcs to correctly add in the yaw and pitch offsets, corrected for bank angle. Actually this is still an estimation. A proper calculation will sum the submodels vector with the airplane's vector. Until that's done only models which are fired forward will have proper IC.
2004-09-09 08:40:08 +00:00
Vivian MEAZZA: """ "Flight plans" which can start at a given time (gmt) WAITUNTIL tokens which pause the flight plans until a given time (gmt) Submodels can now be attached to any AI objects (except submodels - it can be done, but in my experimental code it's too expensive in frame rate atm) "No-roll" attribute added to Ballistic objects - useful for wakes and the like "Random" attribute added to Ballistic objects (adds =- 5% to the Cd) - useful for smoke, exhausts If the <trigger> tag is not specified the Ballistic object/s will be released at start-up (cannot be stopped) Submodels are not released from AI Objects if the AI Object is more than 15 miles away. """ mf: minor code and formatting fixes; submodels.?xx were FUBAR and are thus astyle formatted; NOTE that <name> tags END, EOF, WAIT, WAITUNTIL are *depreciated*. Don't get too used to them. This will have to be moved from the "name" to regular engries.
2007-03-30 22:51:52 +00:00
// A list of pointers to AI objects
typedef list <SGSharedPtr<FGAIBase> > sm_list_type;
typedef sm_list_type::iterator sm_list_iterator;
typedef sm_list_type::const_iterator sm_list_const_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
Vivian MEAZZA: """ "Flight plans" which can start at a given time (gmt) WAITUNTIL tokens which pause the flight plans until a given time (gmt) Submodels can now be attached to any AI objects (except submodels - it can be done, but in my experimental code it's too expensive in frame rate atm) "No-roll" attribute added to Ballistic objects - useful for wakes and the like "Random" attribute added to Ballistic objects (adds =- 5% to the Cd) - useful for smoke, exhausts If the <trigger> tag is not specified the Ballistic object/s will be released at start-up (cannot be stopped) Submodels are not released from AI Objects if the AI Object is more than 15 miles away. """ mf: minor code and formatting fixes; submodels.?xx were FUBAR and are thus astyle formatted; NOTE that <name> tags END, EOF, WAIT, WAITUNTIL are *depreciated*. Don't get too used to them. This will have to be moved from the "name" to regular engries.
2007-03-30 22:51:52 +00:00
sm_list_type sm_list;
Vivian Meazza: I had to reverse a number of signs to get it right. I took the opportunity to add roll to the submodel so that droptanks will come off with the right orientation. I have neither added the rotational speed to the submodel, nor yaw, so if you release droptanks with significant roll rate or yaw angle on the aircraft the submodel will not be quite right. Straight and level, or nearly so, is fine.
2004-09-17 16:32:58 +00:00
Vivian MEAZZA: """ "Flight plans" which can start at a given time (gmt) WAITUNTIL tokens which pause the flight plans until a given time (gmt) Submodels can now be attached to any AI objects (except submodels - it can be done, but in my experimental code it's too expensive in frame rate atm) "No-roll" attribute added to Ballistic objects - useful for wakes and the like "Random" attribute added to Ballistic objects (adds =- 5% to the Cd) - useful for smoke, exhausts If the <trigger> tag is not specified the Ballistic object/s will be released at start-up (cannot be stopped) Submodels are not released from AI Objects if the AI Object is more than 15 miles away. """ mf: minor code and formatting fixes; submodels.?xx were FUBAR and are thus astyle formatted; NOTE that <name> tags END, EOF, WAIT, WAITUNTIL are *depreciated*. Don't get too used to them. This will have to be moved from the "name" to regular engries.
2007-03-30 22:51:52 +00:00
void loadAI();
void loadSubmodels();
Vivian MEAZZA: - extract common parts of load() and loadAI() into setData() - fix trigger handling for aircraft that set a not yet existing property
2007-05-12 10:39:56 +00:00
void setData(int id, string& path, bool serviceable);
Vivian MEAZZA: """ "Flight plans" which can start at a given time (gmt) WAITUNTIL tokens which pause the flight plans until a given time (gmt) Submodels can now be attached to any AI objects (except submodels - it can be done, but in my experimental code it's too expensive in frame rate atm) "No-roll" attribute added to Ballistic objects - useful for wakes and the like "Random" attribute added to Ballistic objects (adds =- 5% to the Cd) - useful for smoke, exhausts If the <trigger> tag is not specified the Ballistic object/s will be released at start-up (cannot be stopped) Submodels are not released from AI Objects if the AI Object is more than 15 miles away. """ mf: minor code and formatting fixes; submodels.?xx were FUBAR and are thus astyle formatted; NOTE that <name> tags END, EOF, WAIT, WAITUNTIL are *depreciated*. Don't get too used to them. This will have to be moved from the "name" to regular engries.
2007-03-30 22:51:52 +00:00
double getRange(double lat, double lon, double lat2, double lon2) const;
Vivian Meazza: I have added <Cd> and <weight> to the input parameters in the submodels.xml script. Raw data may be used, thus avoiding the need to guestimate <eda>. Eda remains, but should now be used to enter the proper cross-sectional area.
2004-09-22 08:47:05 +00:00
Vivian MEAZZA: """ "Flight plans" which can start at a given time (gmt) WAITUNTIL tokens which pause the flight plans until a given time (gmt) Submodels can now be attached to any AI objects (except submodels - it can be done, but in my experimental code it's too expensive in frame rate atm) "No-roll" attribute added to Ballistic objects - useful for wakes and the like "Random" attribute added to Ballistic objects (adds =- 5% to the Cd) - useful for smoke, exhausts If the <trigger> tag is not specified the Ballistic object/s will be released at start-up (cannot be stopped) Submodels are not released from AI Objects if the AI Object is more than 15 miles away. """ mf: minor code and formatting fixes; submodels.?xx were FUBAR and are thus astyle formatted; NOTE that <name> tags END, EOF, WAIT, WAITUNTIL are *depreciated*. Don't get too used to them. This will have to be moved from the "name" to regular engries.
2007-03-30 22:51:52 +00:00
};
Vivian Meazza: The calculation of submodel mass from weight has been moved from AIBallistic to Submodel so that it is calculated only once, rather than on every iteration as a present. The parameter <contents> has been added, primarily so that droptanks will have the proper mass. It is the path to an appropriate property containing a weight in lbs. Care has to be taken with the use of <contents> because after a reset there appears to be a delay in submodel instantiation (dt not properly reset???) and the weight property is not always picked up before it is set to zero in the key bindings. Slightly hard to explain. It works fine if FGFS has not been reset though. There is a partial solution which involves the rejigging of the fuel and gui nasal scripts, but there is still the visible delay in instantiation to be resolved. I've nearly done the nasal fixes, which will form part of an update to the Hunter only. I'll probably complete those later today.
2004-09-27 14:24:20 +00:00
Vivian MEAZZA: """ "Flight plans" which can start at a given time (gmt) WAITUNTIL tokens which pause the flight plans until a given time (gmt) Submodels can now be attached to any AI objects (except submodels - it can be done, but in my experimental code it's too expensive in frame rate atm) "No-roll" attribute added to Ballistic objects - useful for wakes and the like "Random" attribute added to Ballistic objects (adds =- 5% to the Cd) - useful for smoke, exhausts If the <trigger> tag is not specified the Ballistic object/s will be released at start-up (cannot be stopped) Submodels are not released from AI Objects if the AI Object is more than 15 miles away. """ mf: minor code and formatting fixes; submodels.?xx were FUBAR and are thus astyle formatted; NOTE that <name> tags END, EOF, WAIT, WAITUNTIL are *depreciated*. Don't get too used to them. This will have to be moved from the "name" to regular engries.
2007-03-30 22:51:52 +00:00
#endif // __SYSTEMS_SUBMODEL_HXX
Copy permalink