In this engine there is literally NO reason on ANYTHING.
In case you wasn’t aware, it doesn’t cost you anything to not reply to questions you don’t know the answer to.
With regards to floating point precision, the engine has trouble past 2km no at 640m.
If we want to discuss it scientifically, floating point precision problem is always present. You can have the problem right from 0.
The threshold in which you deem it as “trouble” is arbitrary and is not the point of my thread.
The point is, with cm as default unit, you will reach more “trouble” a lot “sooner” than meter as the unit. Which makes Centimeters worse as an option for “default” unit .
I want to know why Epic engineers chose the worse option for the default option.
And even then, it’s pointless to argue that “it’s built and maketed for large words” or whatever - a large world will always require world origin shifting. The engine does include the function.
It’s also fairly easy to set up for “infinite” geometry without ever incurring into floating point issues in practice.
Again, this post is not about origin shifting.