[Solved] float logs as 2, but floors to 1, and != 2.

[lordofduct]

This ToString is ironically a lot like this other discussion:

Don't use double.ToString() if you don't want to lose precision

Hi devs, So I’ve just spent 2 hours figuring this out and thought I could help other devs avoid this. This is a general C# oddity I found (java doesn’t do this) Don’t use double.ToString() without a specifier if you plan to then parse it back. Use the “G17” specifier whose sole purpose is to assure a roundtrip conversion without loss of precision. More info (the “R” specifier I think is kept for historical reasons, and it shouldn’t be used either): Link Test it: double d = new System.Rando…

In the future… if you see numbers acting weird, first consult the magical oracle of floating point and assume that’s the problem.

Yep, it’s weird… but as you have said, now you know.

Cause at the end of the day… if there was somethign truly buggy about floats/doubles. The internet by and large would be up in arms. Becuase consider the fact that Unity didn’t create C#/mono/.net. Microsoft created C# and .net, and mono by Ximian/Xamarin/opensource community and has a massive user base around the world. They’d know if float acted outside of the IEEE 754 standard:

IEEE 754

Especially considered that most floating point operations are really just pass through to the CPU, and if the CPU doesn’t support it (what is this? 1995?) the OS has an implementation for it. So as to avoid environment to environment differences/bugs like you thought you may have found.