I think we could concentrate our effort to evaluate some parameters in way
to verify a good or bad landing and so we can also generate a sort of damage
relatory acording to situation.
Sergio Roth
- Original Message -
From: Thales de Lima Ferreira <[EMAIL PROTECTED]>
To: <[EMAIL PROTECT
Gene Buckle wrote:
>>Maybe "Collision" might be a better term. "Crashed" might be taken to mean
>>the program crashed
> ...for sound card users...
>
> "WHOOP! WHOOP! PULL UP! WHOOP! *pause* Oh. Never mind."
Or, "Dady, you just hit the ground! Hi hi hi."
> *grin*
_
> 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;
On Thursday 03 January 2002 05:08 pm, you wrote:
> > Gene Buckle wrote:
> > > How about:
> > >
> > > ...for sound card users...
> > >
> > > "WHOOP! WHOOP! PULL UP! WHOOP! *pause* Oh. Never mind."
> >
> > Hey, I like that!
>
> I'm going to be using that for the F-15. I've got the GPWS sound an
> I don't see why not as long as you #include
>
> 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. Th
Curtis L. Olson writes:
> 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
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();
>}
Curtis L. Olson writes:
> Hey, can we embed tags in "/sim/crashed_string"? :-)
Sure, if you won't mind escaping them in any XML property file, i.e.
You are
The escaping wouldn't be necessary on the command line:
fgfs --prop:/sim/messages/collision='Yo
> Gene Buckle wrote:
> >
> > How about:
> >
> > ...for sound card users...
> >
> > "WHOOP! WHOOP! PULL UP! WHOOP! *pause* Oh. Never mind."
> >
>
> Hey, I like that!
>
I'm going to be using that for the F-15. I've got the GPWS sound and it
would be trivial to edit in the speech on the e
> 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.
Right now, when JSBSim crashes, it freezes the FDM. It also puts
a message onto the message queue that says: "Crash Detected". The
message queue is read in JSBSim.cxx.
Gene Buckle wrote:
>
> How about:
>
> ...for sound card users...
>
> "WHOOP! WHOOP! PULL UP! WHOOP! *pause* Oh. Never mind."
>
Hey, I like that!
CU,
Christian
--
The idea is to die young as late as possible.-- Ashley Montague
Whoever that is/was; (c) by Douglas Adams would have
Gene Buckle writes:
> >
> > Maybe "Collision" might be a better term. "Crashed" might be taken to mean
> > the program crashed
> >
>
> How about:
>
> "Congratulations! You're going home in a Hefty Cinch-Sak(tm)!"
>
> ..or maybe...
>
> "Error.
> Altitude = 0
> Airspeed = 0
> Ideas = NULL"
Curtis L. Olson writes:
>
>Norman Vine writes:
>>
>> Ooops My Bad .
>>
>> if (crashed)
>> mkDialog(fgGetString("/sim/crashed_string").c_str());
>
>Hey, can we embed tags in "/sim/crashed_string"? :-)
Sure,
but PUI won't interpret them as anything special.
___
>
> Maybe "Collision" might be a better term. "Crashed" might be taken to mean
> the program crashed
>
How about:
"Congratulations! You're going home in a Hefty Cinch-Sak(tm)!"
..or maybe...
"Error.
Altitude = 0
Airspeed = 0
Ideas = NULL"
...for sound card users...
"WHOOP! WHOOP! PULL
* [EMAIL PROTECTED] (John Check) [2002.01.03 13:30]:
> On Thursday 03 January 2002 02:18 pm, you wrote:
> > #include
> >
> > if( crashed )
> >mkDialog("Ooops Crashed\nto restart sim\nSelect FileMenu::Reset")
>
> Maybe "Collision" might be a better term. "Crashed" might be taken to mean
> th
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
> >>
> >> if( crashed )
> >>mkDialog("Ooops Crashed\nto restart sim\nSelect FileMenu::R
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
>>
>> if( crashed )
>>mkDialog("Ooops Crashed\nto restart sim\nSelect FileMenu::Reset")
>>
>Maybe "Collision" might be
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
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
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. O
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,
21 matches
Mail list logo
