Critical map bug (using ruler map tool)

[TheDarkWraith]

I was working on adding super marks and user placed navigation markers for real navigation when I discovered that where I clicked on the screen wasn't matching what should be the equivalent distance in meters. So I ran a little test. I set the game screen resolution to 1024 X 768. Ran the game. Went to both maps and using the scale located in the bottom left of each map I took my ruler tool and measured that reference distance. Result: didn't even come close :o So I changed screen resolutions to different screen resolutions and did the same tests. Result: different readings for each different screen resolution :o :nope: So what does this mean? The maps are bugged and using the ruler tool gives erroneous readings for the distance based on screen resolution.
How in the world did this ever pass QA? This is worse than the mast height problem :damn: The mast height problem was fixable but I don't see any way to fix this one :hmmm: Anyone have any ideas? :06:
Someone do the same tests as I did and see if you don't come up with different readings for the reference scale based on screen resolution.

[stoppro]

yes I Noticed this a while back I play at 1920 x1200 like you do. the scales are way off I got used to it and ajusted my attacks. but not before i ran right into a dd or too close to use torpedos. I can work around it but I don't play at 100 percent yet.I can see where it would be a real pia if you are at 100 percent realism. It gets worse when you zoom the tai map in or out

[Zedi]

The scaling is wrong all over in the game. I realized that when I was working on ERM and measured the whole fleet. I was kinda shocked to see that a tanker is shorter than a cargo ship, at least in the ship .cfg file. I stopped using the navmap when I was getting very wrong values on the 4 bearing method using the tools provided by the game. Since then, I use real papers and pencils and a very personal way to approach my targets.

SH5 is a mess already, gathering all the bugs from the previous versions. If there will be any new version, that need to be built from the scratch.

[PL_Andrev]

I don't see any way to fix this one :hmmm: Anyone have any ideas? :06:

I'm not sure I understand this problem correctly...

To fix them:
1) Read the current game resolution
2) Put the correction variables depend from current resolution.

But... could you insert the more precise description with screens?

[Vanilla]

As I get it - what TDW is saying is that the map is squeezed or stretched depending on the resolution and tools aren't. That means that for example on 1024x768 4:3 on certain map zoom level you will get 4km of actual in-game distance while measuring vertically and on another screen say on 1280x720 16:9 on another zoom level you'll get 5km vertically and 3km horizontaly with the same ruler because the map is squeezed and stretched while the tool remains the same size. And, oh my, on the ruler you will always see the same 3.8km. So you don't actually measure anything, but you think that you do, because the ruler does not show the actual in-game distance but rather some quasi-random number.

To aggravate things further while one can introduce certain coefficients for vertical or horizontal measurment on the map if you place the in-game ruler at some other arbitrary angle (not vertically or horizontally) you will need to use some sine or cosine law to determine correct length. And that's not all - with changing zoom level (remember that at the moment there is no 'indicator' for zoom level of the map) you will need new coefficients even if the screen resolution remains the same.

More than that - imagine that somebody had somehow modded in the coefficients so the above mentioned calculation is done automatically, but then a new problem would arise - when you were pivoting your ruler, holding it at one end, then the game should either automatically resize the ruler (simultaneously moving the holding point, that is mouse X and Y coords) or change the range written on it. Even if it was done, and I guess it is not all that easy, then you would still have a problem of 'erratic ruler' with some not so easily understood by a ordinary captain behaviour while pivoting it.

The only solution is to, somehow, force the map not to re-size with the screen res always having a fixed size as do the map tools. But I guess it requires complete rehaul of the map engine through hex-editing. Or?

BTW, if all of the above is true, then when you plot everything by hand, not using ship icons or shores given on the map, you won't notice the problem - it is the same as drawing it on paper. :) So 100% realism only! But this bug is a major killer for all the mods that would automatically place something on the map.

[Trevally.]

When I did harbour pilot, I had to map harbours and plot waypoints.
To do this I had the Nav officer call coordinates for each one.
No problems.:up:

The problem I did have was measuring distances. Turns for waypints were either 50m or 100m from the called point. Knowing how big this really was on the map was apita:nope:

[BigBANGtheory]

I took Trevally's TDC practice map, paused it and measured the distance nose to nose from sub to target (by zooming in and out) at a screen res of 1920x1080 and then at 1024x768.

I measured them both at 6900m with the ruler which should be repeatable by others.

When I used the ruler to check the scale indicator on the bottom left I found it to be way out, worse at 1920x1080.

[Reece]

Are the measurements correct for 1024x768?:hmmm:

[Vanilla]

I took Trevally's TDC practice map, paused it and measured the distance nose to nose from sub to target (by zooming in and out) at a screen res of 1920x1080 and then at 1024x768.

I measured them both at 6900m with the ruler which should be repeatable by others.

When I used the ruler to check the scale indicator on the bottom left I found it to be way out, worse at 1920x1080.

Great news! At least the ship and other marks are correct and only scale indicator is wrong. I guess it means that the marks are placed correctly but the map is still distorted so the only problem is land. Must check...