Atan2 table

[dafioram]

1. Add a float lookup table for atan2, similar to star trek's atan2 lookup, except that one is for a fixed size table and uses ints. This lookup is faster than atan2().
2. Use the table in titanic star control. I tested it as well.

Making a atan2 table based only on ints may also be useful to add.

[foobar13372]

Does this improve anything? How much faster is "faster"? LUT's are great on limited hardware that is needing the calculation very often - this isn't the case here. For now I only see increased code complexity that doesn't add anything.

But maybe I'm just not seeing the intention here, that's why I'm asking.

[lskovlun]

One problem with this is that in cases where LUTs are actually useful they can easily contain little idiosyncrasies on a per-engine basis (round-off errors, edge cases and the like). So you end up having to have one for each engine anyway.

[dafioram]

@foobar13372 it is 65% faster than the float atan2 call. While titanic may not speed up that much since the atan2 is not used much something like bladerunner does a lot more atan2 so it would benefit more.

@lskovlun I'm not sure I understand, how can an engine do an atan2 function correctly, but not be replaced by a more general atan2 call? I'm thinking of star trek here. We can always select a lower number of points/bits to model less precision to stay true to an engine.