Precision errors in object position and dimensions

[trsh]

Any chance to battle those small precision errors?

https://jsfiddle.net/u0zgL0va/ (check console -> x:200.39999389648438)

[ivan.popelyshev]

You're very lucky that JS uses double precision. Because if you try to put big coordinates in Graphics, it will use single precision, and shader uses single precision and THAT will be real problem with precision. Put as much as you can in javascript side: use ".position" in graphics and meshes, dont try to put big coords inside them.

As for the case you mentioned, there's no precision problem.

[trsh]

1 hour ago, ivan.popelyshev said:

You're very lucky that JS uses double precision. Because if you try to put big coordinates in Graphics, it will use single precision, and shader uses single precision and THAT will be real problem with precision. Put as much as you can in javascript side: use ".position" in graphics and meshes, dont try to put big coords inside them.

As for the case you mentioned, there's no precision problem.

But I put .4 and I got (.4 - 0.0000000001) something. So i lost 0.000001 something?

[ivan.popelyshev]

I guess you're right, getBounds() uses single precision and is losing some part of it. But I dont think why do you need better precision there

[xerver]

https://en.wikipedia.org/wiki/Floating_point#Representable_numbers.2C_conversion_and_rounding

Just an artifact of the IEEE 754 format. There is a reason you don't use hardware-level floating precision numbers in applications that deal with money

[ivan.popelyshev]

@xerver

Its because getBounds() of Sprite uses Float32Array which is single precision