Calculator operands maximum and minimum precision errors
@Alados they were always capped before I believe.
@Mm cheers ^^
AdminQA Team (QA, Media Molecule) commented
I can confirm that the issue you have reported has been bugged
Thank you Lara L
However calculators display "0.00" when an operand is 2^64 or larger, even if you can use numbers up to 2^128 (not included). The second calculator is to show the value is actually kept and dividing by 2 gets you 2^63 just fine, and the number barely fits.
Of course numbers over 2^64 are absurdly large and they wouldn't fit, and the slider is maxed out (same happens with negative numbers, as only the Sign bit changes), and the cable lit, so you know it isn't actually 0, but that "0.00" display is confusing. Maybe use scientific notation? Some "Over 2^64" prompt? The elephant icon?
Just please, please, please, don't cap calculators again, floats can be confusing but being able to use them fully is perfect, and limiting them would be catastrophic for some creations D:
I'm sure it has to do with how 32-bit floats work, and how the increment/decrement with the D-Pad is coded. Just wrote a long explanation on Twitter so allow me to send a link: https://twitter.com/adriaalados5/status/1232469152431915008
Basically after 8,388,608 you cannot represent any decimal places, after 16,777,216 the precision is 2, and so on. If you enter a number with L1+Square you'll see how it gets rounded to the nearest possible representation.
Also on calculators I don't see what you say on the other post for text displayers when using the D-Pad to increment/decrement. It takes a while to change, but I think that's normal, as it has to go from one integer to the next without being able to represent any numbers in between. If you keep the button pressed, it will start to go faster as it usually does.