On Tue, Jul 5, 2011 at 10:05 PM, Torsten Dreyer wrote:
There is a bias element to add an offset to the property value just before
step and scroll are applied. If you pick it small enough, It gets cut off by
the step element but gets you past the roundoff error.
Thanks Torsten. I should have
Thanks!
No idea how it could have worked before. I've committed an update as
described above.
However, I'm still seeing some strangeness:
1) Sometimes I'm seeing 99 rather than 100
2) Even with these changes, the -1000 value is incorrect.
I suspect that there's some floating point issue
Thanks!
No idea how it could have worked before. I've committed an update as
described above.
However, I'm still seeing some strangeness:
1) Sometimes I'm seeing 99 rather than 100
2) Even with these changes, the -1000 value is incorrect.
I suspect that there's some floating point
Hi All,
I've been trying to fix bug 340
(http://code.google.com/p/flightgear-bugs/issues/detail?id=340), where
the VS KAP140 display in the c172p mysteriously stopped working about
a month ago.
To fix it partially, I've created a new AP filter converting from the
pressure-rate-target to a fpm
Anyone got any ideas?
Hi Stuart,
The correct usage would be
animation
typetextranslate/type
object-namevs-digit5/object-name
property/autopilot/KAP140/settings/target-pressure-rate-fpm/property
factor0.1/factor
step1/step
axis
x1/x
y0/y
z0/z
/axis
Typo!!! (see inline)
Why?
The order of computation is (example for digit2, propertyvalue=500):
1. get property value (500)
2. apply stepping ( 500 step 1000 = 0)
3. apply factor (0 * 0.0001 = 0 -- don't shift texture)
or for propertyvalue=5500
1. get property value (500)
1. get property
6 matches
Mail list logo
