Fixed-point game calculations are ugly and inflexible about broguece HOT 4 CLOSED

Assuming we can convince the compiler to conform to IEEE, the only way I can currently see out-of-sync errors occuring is due to accumulated errors when modifying floats. For example, if non-recorded inputs somehow temporarily modify floating-point state variables, by say adding and then taking away a value, then the result may be slightly different to the original. But this would require careful inspection of the code.

from broguece.

It may be possible to instead implement a reasonable fixed-point pow function. There is a technique where you expand the fractional part of the exponent as a sum of negative powers of 2, (i.e. 1/2 + 1/4 + 1/8 + ...) and use square roots to compute the result. However this would be slower than both lookup tables and floating point.

from broguece.

A fixed-point pow was added in 2e7a8a0. Rewriting the lookup tables with this function will make things a lot tidier.

from broguece.

Closing this as the tools are available to remedy it; things will be refactored as needed.

from broguece.