20,741
edits
Implementing VNAV support in FlightGear: Difference between revisions
Jump to navigation
Jump to search
m
Implementing VNAV support in FlightGear (view source)
Revision as of 00:55, 4 December 2013
, 4 December 2013→Open Questions
(→VNAV) |
m (→Open Questions) |
||
| Line 422: | Line 422: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
=== Parent & Child FDMs === | |||
{{cquote|One feature in JSBSim that I began and have not yet finished (pending other things) is a parent/child capability. You can (for instance) load a Mk82 on | |||
an F-16 and the physical effects of the Mk82 will affect the F-16. The position is based on the position of the parent, and so is the orientation. | |||
However, the Mk82 position is not integrated, it always has a position based on the parent, UNTIL it is released. Then, the EOM begins integrating and | |||
the flyout is physics based. | |||
The child objects are each their own individual JSBSim objects in their own right, and each could be loaded and flown by itself. The JSBSim executive is | |||
sort of recursive in this way. Each would be addressable in a way that I think Tony set up with Properties, but I can't recall what it is. | |||
Technically, it is also possible for each droppable piece to have its own propulsion and flight control system, too. The possiblities there are quite | |||
broad.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg21162.html |title=Eye Candy |author=Jon S. Berndt |date= Sat, 14 Feb 2004 13:43:55 -0800}}</ref>|Jon S. Berndt}} | |||
{{cquote|Of course we would like a parent/child FDM system, and from all these postings is seems as if we nearly have. In the order of things, I don't think it is very high on the todo list.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg21164.html |title=Eye Candy |author=Vivian Meazza |date= Sat, 14 Feb 2004 13:43:55 -0800}}</ref>|Vivian Meazza}} | |||
{{cquote|One thing I've been playing around with (OK, _played_ around with - about a year ago) in JSBSim was the ability to add "child" objects to the main aircraft. Each child would be a separate instance of a JSBSim FDM. The idea would be to provide a way to model an aircraft with attached stores. Each store would transmit forces and moments to the parent aircraft (for example a Mirage) until it was released, at which time the FDM for that child object (for example a Mk-82 or AIM-9) would start integrating and do its own flyout - the parent aircraft now free of the effects of the store. Additionally, each store would have its own config file - and its own flight control system/autopilot/guidance. In theory, the possibilities are limitless for game playing, where one might <PC> set up a food drop tank to be released from an aircraft and make a mid-air "connection" to another aircraft, mid-flight</PC>, or <PC> a water delivery tank could be guided by homing device to a precision landing extremely close to a hostile anti-aircraft battery or needy family (in some cases these are coincident)</PC>. I've been threatening to complete this for a long time, but one day we'll allwake up and I'll announce that it is finished. <ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18114.html |title=Multiplayer Server RFC |author=Jon S. Berndt |date=Wed, 05 Nov 2003 13:01:44 -0800}}</ref>|Jon S. Berndt}} | |||
<references/> | |||
=== Open Questions === | === Open Questions === | ||