New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Difficulty to see enemy with GPS Satellite under FoW, if enemy's color is close to terrain's #10504
Comments
The best option is to create new icon artwork that is larger, uses the brighter end of the remap range, and has a border to match our other overlay icons (repair, powerdown). |
@pchote Nice 👍 |
Definitely an improvement! |
Maybe use the icons from the build palette tabs for the things they match with, and then make new ones in the same style for the ones that are missing? The original vector artwork for these are available at https://github.com/OpenRA/ArtSrc/blob/master/cnc/chrome.svg |
Thanks, I used that for the tank and naval icons now, but for the rest they're pretty much identical to what I already have, or they won't look good at all, e.g. the infantry icon which would either look like crap at too small a size or take up too much space if larger, so I'll stick to a dot for infantry. |
This'll be troublesome. The outer white edge will not work on snow terrain - you should use 2 pixel width outlines with the outer being white, the inner being black. |
IMO give the buildings' inner the outline as well - looks odd with all the rest (esp since tanks do have it). |
I tried that before, but I think looks better like this. There's a darker colour on the inner outline, so the background doesn't shine through. |
When some players choose colors close to terrain's (on temperal maps, dark green, dark blue, ... or even manage to get black with some color trick), it is very hard to see their GPS symbols under the FoW.
So it can become much easier to sneak attack, which is almost impossible for players who use colors with contrast to terrain.
Not sure what the solution could be.
The text was updated successfully, but these errors were encountered: