On April 7, 2005 03:09 am, Melchior FRANZ wrote:
Your standard Nasal
key binding skeleton with one commented out line would do (literally)
nothing to solve this problem. But maybe I just didn't understand your
performance enhancement!? Are you suggesting that we replace all nasal
key bindings
Melchior FRANZ wrote:
whereby the stop() method isn't in CVS yet.
Which reminded me, now it is.
Erik
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Melchior FRANZ wrote:
Normally, the g key turns on /controls/gear/gear-down, and YASim
watches this property and moves /gear/gear[n]/position-norm
accordingly. You just need to override the g/G key bindings in your
*-set.xml file:
Since this is obviously going to be a common issue, maybe it's
Melchior FRANZ wrote:
Yes, we want motion over time. slew sets the property only once. So we
are again back at interpolate()? That's what aircraft.nas does already.
Or would you suggest to write a loop that runs as long as the key
is held down? Would be slower, wouldn't it? And doesn't
Melchior FRANZ wrote:
* Josh Babcock -- Wednesday 06 April 2005 04:23:
The Superfort's flaps and gear are electrically powered, and the controls for
both are instantaneous switches. ie. you have to hold the switch the whole cycle
to keep the motor running. Can anyone think of a way to do this?
Andy Ross wrote:
Melchior FRANZ wrote:
Normally, the g key turns on /controls/gear/gear-down, and YASim
watches this property and moves /gear/gear[n]/position-norm
accordingly. You just need to override the g/G key bindings in your
*-set.xml file:
Since this is obviously going to be a common
On April 6, 2005 05:18 am, Melchior FRANZ wrote:
Here is an improved version. It initializes gear with settimer,
because otherwise using /controls/gear could lead to collisions with
other parts that messed with it at startup. You can instead use a
different property path. And then, we keep
