GTLD Range Not Accurate

[RAWSwampFox]

Good Morning,

Ok, it appears that the range in the GTLD gets a bit inaccurate the further out you go from a target. Now, I'm not exactly sure how else to prove this other than the following two screenshots. I set the target with my GTLD and walked until the range at the bottom of the screen changed to 250 which, to me, would indicate that I'm exactly (I use this term loosely) 250m away from the target. When I look at the target through my GTLD, it shows 224m instead of 250m. Please advise.

[AncientMan]

The range indicator on the map rounds to the nearest 50, so it saying 250 actually means the range is somewhere between [225-275). The reason it's saying 224 for you is probably due to the marker you placed not being exactly where you're aiming with the GLTD.

Not a bug, just a misunderstanding.

[RAWSwampFox]

Good Afternoon,

So, the rounding up as you state, applies to everything regardless of whether you walk it off with the range window up watching the range number change at the exact time that it has reached the number indicated?

I mean, I walked backwards with my CAPSLock screen open watching the number waiting on it to change. When it changed, I walked a bit forward to make sure that I was at the exact point when it changed which would indicate to me that I was 250m away from the target. Now, if what you are saying is true, then all measurements are a "50m" (or whatever the keypad distance is) approximately??

Please explain.

[camo]

Within plus 25 metres and minus 25 metres yeah. Doesn't matter about keypad size though, it doesn't scale to the map, its always 50.

Didn't really understand your question though so I don't know if I answered it.

[RAWSwampFox]

Good Afternoon,

Ok, so here is what I did:

1. Set target marker with GTLD zoomed in on the target.
2. Hit CAPS-lock and walked backwards watching the range number at the bottom of my screen.
3. I waited until it changed to the next 50 number and then adjusted to make sure I was at the exact spot where it changed to the next 50 number.
4. Refocused my GTLD back onto the target and came up with a 224 range instead of a 250 range which, according to the CAPS-lock screen range number, I was at.

Now combine that information with Ancient's response, all measurements in PR are approximate and are not anywhere close to scale? This is what I'm gathering from this thread.

[Mineral]

Ancients post is very clear.

1: your mapmarker and GTLD aren't aimed at the same thing
2: the range said by the map isn't accurate as it's a 50m range.

[RAWSwampFox]

Good Afternoon,

Well, ok, I agree then it is not a bug but based on all discussed in this thread, I doubt there is any possibility of an accurate means of measurement within PR based upon this.

Is this is a specific game engine issue or is this across the board with all game engines?

[dysin]

AncientMan;2088731']The range indicator on the map rounds to the nearest 50, so it saying 250 actually means the range is somewhere between [225-275). The reason it's saying 224 for you is probably due to the marker you placed not being exactly where you're aiming with the GLTD.

Not a bug, just a misunderstanding.

i always thought, for example- the range was accurate on 50m mark, then rolls over to 100 once the mark is legitimately at or beyond 100m.
so a mortar range on a map mark reads 850. we just toggle the mark until it rolls over to 900, and estimate the difference for accurate range to original target. what you're saying is that even if it reads 850, it might be 830 and rounding up?

[AncientMan]

I'll try and explain in a bit more detail then, to demonstrate why you think there might be inaccuracies.

There are 4 positions we are talking about here:

• XYZ(1) = Player position (this is at the players origin point, which is their feet).
• XYZ(2) = Camera position (this is at the players eyes, in their head).
• XYZ(3) = Marker position
• XYZ(4) = GLTD look at position.

GLTD is the most accurate way of determining position. It calculates the distance between XYZ(2) and XYZ(4) in 3D space. The resulting value is the exact distance between where your view point is, and what you're looking at. Lets assume that the resulting value of this calculation is 224.999999354131. Because having floating point numbers on the HUD looks bad and is unnecessary, the resulting value is truncated down to 224. This is the value you're seeing in the pictures above.

On the other hand, the range value shown on the map view is calculated completely differently. For starters, it uses different start and end positions - XYZ(1) and XYZ(3). Secondly, it also only calculates in 2D space, the Y value (height) is ignored. You will notice this inaccuracy if there was large elevation differences between the player position and the marker position (in the pictures above, there is very little). This is intentional, because of mortars (they have a separate parameter for elevation, which when used correctly, will solve this issue).

So, the range value is now the distance between XZ(1) and XZ(3). Lets say that this resulting value is 225.0000000654132. This is rounded to the nearest 50, which is of course 250, and is the value you're seeing in the pictures above.

Also, to re-iterate my previous post, the range value on the map view is rounded to the nearest 50. So when it says 250, the real range is between [225-275) (between 225.0000000000 and 274.9999999999). It is not a different calculation that some are assuming, it is not rounded down like 299 = 250, or rounded up like 201 = 250. It's the nearest 50.

Does this make sense now? There may be perceived inaccuracies, but really, it's completely separate calculations using completely separate positional values. I hope that helps.

[dysin]

I hope that helps.

yeah thanks, useful information i've never seen before

[RAWSwampFox]

Good Morning,

Thank you AncientMan for the additional information. Still working through some kind of way to accurately measure things in PR. I mean heck, the map has grids.