[Flightgear-devel] The bouncing plane
Hello, I´m trying to make the plane crash... I mean, as much fun as it is when you hit the ground and the plane simply bounces back into the air, this is not very realistic :-) I made the program go to a crash scene when the plane hits the ground, but that also mean that the plane can´t land, since I use the scenery altitude for that. Is there any way to know the location of the runway on the map? Or a function that returns that value to me? I would also need to know the inclination of the plane, so that if the guy lands on the runway at a 90 degree angle, the plane crashes... I tried looking for these things on the code, but I only find their declaration, I couldn´t find any values being passed to them. Thanks in advance for any help you can give me. All the best Thales Ferreira [EMAIL PROTECTED] www.staridia.com _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] The bouncing plane
Thales de Lima Ferreira writes: Hello, I´m trying to make the plane crash... I mean, as much fun as it is when you hit the ground and the plane simply bounces back into the air, this is not very realistic :-) I made the program go to a crash scene when the plane hits the ground, but that also mean that the plane can´t land, since I use the scenery altitude for that. Is there any way to know the location of the runway on the map? Or a function that returns that value to me? I would also need to know the inclination of the plane, so that if the guy lands on the runway at a 90 degree angle, the plane crashes... I tried looking for these things on the code, but I only find their declaration, I couldn´t find any values being passed to them. Thanks in advance for any help you can give me. All the best Thales, The latest development version in cvs does a much better job of crash detection. I'd suggest you grab the latest code from cvs: http://www.simgear.org/cvs.html (simgear) http://www.flightgear.org/cvsResources/anoncvs.html (fgfs) http://rockfish.net/fg/ (base package) Right now when flight gear detects a crash it simply freezes the sim. The idea is that if we have motion hardware connected up, we don't want to overdrive the hardware beyond it's capabilities. But, a nice crash scene could be an interesting option. Regards, Curt. -- Curtis Olson Intelligent Vehicles Lab FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] The bouncing plane
David Megginson writes: Curtis L. Olson writes: Right now when flight gear detects a crash it simply freezes the sim. The idea is that if we have motion hardware connected up, we don't want to overdrive the hardware beyond it's capabilities. But, a nice crash scene could be an interesting option. Right. One of us needs to get around to writing a pop-up dialog box when that happens, to let the user know what's going on. #include GUI/gui.h if( crashed ) mkDialog(Ooops Crashed\nto restart sim\nSelect FileMenu::Reset) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] The bouncing plane
On Thursday 03 January 2002 02:18 pm, you wrote: David Megginson writes: Curtis L. Olson writes: Right now when flight gear detects a crash it simply freezes the sim. The idea is that if we have motion hardware connected up, we don't want to overdrive the hardware beyond it's capabilities. But, a nice crash scene could be an interesting option. Right. One of us needs to get around to writing a pop-up dialog box when that happens, to let the user know what's going on. #include GUI/gui.h if( crashed ) mkDialog(Ooops Crashed\nto restart sim\nSelect FileMenu::Reset) Maybe Collision might be a better term. Crashed might be taken to mean the program crashed ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] The bouncing plane
John Check writes: Right. One of us needs to get around to writing a pop-up dialog box when that happens, to let the user know what's going on. #include GUI/gui.h if( crashed ) mkDialog(Ooops Crashed\nto restart sim\nSelect FileMenu::Reset) Maybe Collision might be a better term. Crashed might be taken to mean the program crashed Ooops My Bad . if (crashed) mkDialog(fgGetString(/sim/crashed_string).c_str()); ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] The bouncing plane
Norman Vine writes: John Check writes: Right. One of us needs to get around to writing a pop-up dialog box when that happens, to let the user know what's going on. #include GUI/gui.h if( crashed ) mkDialog(Ooops Crashed\nto restart sim\nSelect FileMenu::Reset) Maybe Collision might be a better term. Crashed might be taken to mean the program crashed Ooops My Bad . if (crashed) mkDialog(fgGetString(/sim/crashed_string).c_str()); Hey, can we embed html tags in /sim/crashed_string? :-) Curt. -- Curtis Olson Intelligent Vehicles Lab FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] The bouncing plane
* [EMAIL PROTECTED] (John Check) [2002.01.03 13:30]: On Thursday 03 January 2002 02:18 pm, you wrote: #include GUI/gui.h if( crashed ) mkDialog(Ooops Crashed\nto restart sim\nSelect FileMenu::Reset) Maybe Collision might be a better term. Crashed might be taken to mean the program crashed This happened to me a while back when I ran a YASim plane into the ground. YASim just cout's CRASHED or something like that. :-) -- Cameron Moore [ Whose cruel idea was it for the word lisp to have an s in it? ] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] The bouncing plane
BERNDT, JON writes:
Right. One of us needs to get around to writing a pop-up dialog box
when that happens, to let the user know what's going on.
Could I use what Norman suggested within JSBSim.cxx:
...
...
for ( i=0; i multiloop; i++ ) {
fdmex-Run();
}
FGJSBBase::Message* msg;
while (fdmex-ReadMessage()) {
msg = fdmex-ProcessMessage();
switch (msg-type) {
case FGJSBBase::Message::eText:
SG_LOG( SG_FLIGHT, SG_INFO, msg-messageId :
msg-text );
mkDialog(msg-text.c_str()); // -- Can this be called here in
JSBSim.cxx?
I don't see why not as long as you #include GUI/gui.h
Note
This Dialog Box requires the user to click a button for it to go away
Also note that in this case, ie the plane has crashed, I would prefer
to see a data member in FGInterface that was set appropriately by the
current FDM. Then in fgMainLoop() we could check this variable
ie
fgMainLoop() {
if ( current_fdm-crashed )
mkDialog(fgGetString(/sim/crashed_string).c_str());
...
}
Then this would work for all FDM's :-)
Also If you just want to blast some text to the screen it is probably
best to add a vector fgText member to FGInterface that would
get displayed along with the other HUD Text.
then in fgUpdateHUD we could do something like
for text in FDMTextList:
HUD_TextList.add( text )
This way you could conceivably have live readouts on any thing that
you wanted to monitor.
Cheers
Norman
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] The bouncing plane
I don't see why not as long as you #include GUI/gui.h Note This Dialog Box requires the user to click a button for it to go away Also note that in this case, ie the plane has crashed, I would prefer to see a data member in FGInterface that was set appropriately by the current FDM. Then in fgMainLoop() we could check this variable I like what I read, here. I'll have to read it again when I get home and have some time to really digest it. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Flight.hxx accessors
Hi Regards phrasing for crashes - some refer to that as lawn-darting (remenber that pic on AWST of the Mig-29 at Paris) To the topic. some of the accessors for alpha-dot, beta_dot and temps and pressures are commented out. Would like to (need to) use the data for the OpenGC Flight Management Computer and autopilots. Can they be uncommented? Or is there another way to get the values. Also can't find where the baro/altimeter setting is to correct for density altitude. Tried searching on barometric, kollsman, etc nada. (I'd like to but a vowel) ;-) Regards John W. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] The bouncing plane
For some reason I always envisioned flying through the ground like it wasn't even there, except once you arrive underneath it's all fire, and molten lava, and pitchforks, and screaming, and stuff, and it's all dark and you aren't allowed to climb back above the surface That's a good idea; and some of that scenery would be dual use in the Hilo (Hawaii) area ... on the surface. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
