[BUG] Movement/rotation precision is reduced in multiplayer

[thecraftianman]

Short Description

Currently, most movement/rotation calculations are performed clientside and sent to the server at the end. In order to improve building precision in multiplayer, these calculations should be moved serverside and returned to the client afterwards.

[Niterux]

Question, why would the server be more precise than the client? Wouldn't this only be a problem for moving props?

[thecraftianman]

There is unavoidable precision loss in the networking of float values. The position/angle/etc. values are already networked once from the server to the client so that the client can know about them, then the tool performs its calculations on the client and networks them back to the server. We need to move to fully performing all of those calculations on the server so that no precision loss occurs during that process.

[Niterux]

Why would networking a float cause a loss of precision?

[thecraftianman]

The engine does not network this information in full float precision as an optimization.