Seriously, check https://forums.frontier.co.uk/showthread.php?t=43362&page=116&p=1165593&highlight=FSQRT#post1165593 https://forums.frontier.co.uk/showthread.php?t=43362&page=116&p=1165893&highlight=FSQRT#post1165893 and other posts around there. If you want to re-create exactly what FD is doing 1) do NOT rely on the 1/32 thing, 2) instead do everything using single precision floats, and most importantly for checking distances 3) Use the single-precision FSQRT, not the double precision SQRT.When calculating distances the SQRT is the only floating point operation. Internally coordinates are stored as 1/32 Ly, so I store them as INT. When I substract, square and add them, they're still INTs. And even if I divide them before substracting, the resulting precision is still 100%.
But your post gave me a very useful hint. I remember that the coordinates were displayed with 3 digits decimal precision during some beta phase, so I will try to round them to three digits, then round them to two. Not sure if this will help, but I'll investigate.. Thanks!
Edit: The rounding to three, afterwards to two, removed some errors and brought some more new...![]()
Obviously you may be stuck with a more hacky version of those three things if your chosen language doesn't allow you to use the necessary data types and functions.