[EL 1.0298] Nav console DIST is displayed x10 when not in whole sectors

[Senex]

On the navigation console, when a nav point is set close (same or adjacent sector) from the current position, the DIST readout (bottom-right of Destination Position section) is shown with a value 10 times of what it really is.

For example, if your current position is:
X = 50000
Y = 0
Z = 50000
and your destination position in the same sector is:
X= 50000
Y= 0
Z = -70000
the actual distance is 120K but it is displayed as DIST:0S/1.2M or ten times what it should be.

Another example: If you maintain your original XYZ position as your destination XYZ but you increment your destination SX by one from your current position (in other words, exactly 1 sector away), the distance is displayed as DIST:1S/2.0M which is again ten times what it should be since sectors are 200,000 distance units wide, not 2,000,000.

(Beyond same or adjacent sectors, the DIST readout reverts to a whole sector count on both sides of the slash. For example, a further increment of SX gives a display of DIST:2S/2S, which is OK.)

I apologize if this trivial observation is based on my misunderstanding or it has been raised before (though I cannot find it). I'm very new.

[Vice]

You are reading it correctly. In sector coordinates just use a different multiplier from meter distance used for ship/nav/jump distance tracking. So 1,000 radar/sensor range is 100 in-sector coordinate distance (ie decameters). The 1/10 values are used for in-sector coordinates (nav map) to help keep things a little more manageable for manual entry and visual reference, rather than have to sort through million level values. The greater 10X values are used for other ranges for higher precision up close.

So in summary, a sector consists of 200K X 200K X 200K sub-sector coordinate units in a cube, which is 2-million X 2-million X 2-million close range units you find on the 2D/3D radar, nav marker, target detail, target range, etc.

[DaveK]

I think it might help if I list all of the distance measures and their relationships/multiplier factors and add it to the techy guide. Anyone disagree?

[Senex]

Thank you so much for the reply, Vice. Understood and much appreciated.

And Dave, I personally think your suggestion is a good one and would help. It may not be just me who thinks like an engineer, albeit (in my case) a retired one!

[Marvin]

I think it might help if I list all of the distance measures and their relationships/multiplier factors and add it to the techy guide.

If you do, I think you should add the number 0.00315 as a reference.