Critical map bug (using ruler map tool)

TheDarkWraith · 12-13-10, 11:31 PM

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

So I changed screen resolutions to different screen resolutions and did the same tests. Result: different readings for each different screen resolution

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

The mast height problem was fixable but I don't see any way to fix this one

Anyone have any ideas?

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.

12-13-10, 11:31 PM	#1
TheDarkWraith Black Magic Join Date: Jun 2007 Posts: 11,962 Downloads: 147 Uploads: 5	Critical map bug (using ruler map tool) 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 So I changed screen resolutions to different screen resolutions and did the same tests. Result: different readings for each different screen resolution 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 The mast height problem was fixable but I don't see any way to fix this one Anyone have any ideas? 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.