> 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 somewhere, but I don't see
> how it has only just come to light, and it seems very unlikely to affect
> such straightforward
> numbers.
Yes - that has been a known "feature" for long.
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.
This might work (untested)
<animation>
<type>textranslate</type>
<object-name>vs-digit2</object-name>
<property>/autopilot/KAP140/settings/target-pressure-rate-fpm</property>
<factor>0.0001</factor>
<step>1000</step>
<bias>0.001</bias> <!-- any small number does the trick -->
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</animation>
Torsten
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
