lshems
lshems
I love these balanced and open discussions on where to go when. Refreshing. I think some will know why I post this.
If you don't you don't need to. It's just a compliment then. :)
You don't need a rounding function if that would slow things down to much. A conversion table for 1024 scaled values to the rounded 100.0% values would work also, and...
But it is not an easy problem to solve. example of simple rounding, where the values 1003 and 1002 would both be mapped on 97,9%, but the difference would give...
using a table would prevent this, and exclude for instance the 1002 or 1003 value. It would literally mean that you would loose accuracy. If you really would like to...
anyway, the current, legacy, and very hard to change storage range of -1024-1024, in combination with a comprehensible -100,0 - 100.0% display range was perhaps not the best choice. I...
Be aware, a more solid solution would be to map all values on a -1000 -> 1000 integer instead of the current -1024 -> 1024 range. But that is perhaps...
I'm not sure it should be closed. The info is given in the opentx link. I'll see if can make the script to show the error.
When will this be in a RC? Would love to test.
Inputs allow telemetry sources and multiplication. Division is as always multiplication by the inverse. So setting a scale in an input of 33% is similar to dividing by 100/33% =...