[Bug] Two Rounding Error Bugs

[Tiles]

MMF Build 248

I have two bugs here in a downtracked troublefile. I always just add or substract 0.1 here by pressing and holding the buttons:



1) The first one is that i cannot set my counter to 0 by adding 0.1 and substracting 0.1. What appears instead then is a number containing an e. 2.77556e-017 for example. Which is of course not zero. I can set it to zero by an event though.

2) This one is caused by the 3D Mesh Object and its Memory Leaks i guess. Fact is it adds fine the 0.1 when you start the frame without the 3D Mesh Object. But when you enter the next frame that contains the 3D Mesh Object it starts to spit out rounding errors. 26.6 + 0.1 is of course not 26.7001

This is probably the end of the road after 4 months of work. I need proper adding. Any Workarounds?

Attached file is 15 Kb

EDIT: i think i found a valid workaround. I have to check both checkboxes for floating point values. Number of significant Digits and Number of digits after decimal point. Then the above errors doesn't appear. Clean zero when zero and no more rounding errors. Nevertheless curious with the e number and how the Mesh Object took influence here with rounding.

[Yves]

I didn't loaded your example, but it's certainly due to the way the computer stores floating point numbers, this is very well explained in this thread.

[Sphax]

It's the same problem for me... What is strange here is that the rounding error appears when the mesh object is in the frame...

[Tiles]

Yes, the first error is probably because of the way floats work. I still feel that zero should give back 0 in the counter, and not 2.77556e-017, no matter if the counter is setup as integer or as float. But i can live with that. Setting up the counter properly did solve the quirk

The second error though with the appearing rounding errors is too obvious connected if the 3D Mesh Object is in the frame or not. That's definitely a bug.