Frequently Asked Questions (FAQ) Help - my map looks glossy - as if it is wet! [image: 1609365437597-help-glossy.png] An example of terrain that appears glossy or wet [image: 1609404288193-help-glossy-normal.png] An example of a noisy normal map [image: 1609404297213-help-glossy-albedo.png] An example of a speccy albedo map This is a combination of factors: A bright albedo color from either strata layers or other decals. A noisy normal map. A speccy albedo map. The noisy normal causes some pixels to be lit or darkened accordingly. If this happens quite rapidly (in other words: it starts resembling noise) then some pixels will be lit completely while you wouldn't expect it. Due to how Supreme Commander works with bright colors in combination with bloom it starts looking glossy and / or wet. A solution can be to slightly blur the terrain before generating a normal map from it - this ensures that all pixel-level noise is removed prior to making the normal map!

[image: 1608070821428-baseline.png] The 5th Nomad mission without a lighting map [image: 1608062728745-4096.png] The 5th Nomad mission with a direct + indirect lighting map at a resolution of 4096x4096 [image: 1608062750894-2048.png] The 5th Nomad mission with a direct + indirect lighting map at a resolution of 2048x2048 [image: 1608062761654-1024.png] The 5th Nomad mission with a direct + indirect lighting map at a resolution of 1024x1024 [image: 1608062770217-512.png] The 5th Nomad mission with a direct + indirect lighting map at a resolution of 512x512 [image: 1608062778796-256.png] The 5th Nomad mission with a direct + indirect lighting map at a resolution of 256x256 The indirect lighting slowly causes more and more issues as the resolution is lowered. This may be due to me messing it up in Photoshop accidentally. [image: 1608070458904-direct-4096.png] The 5th Nomad mission with a direct lighting map at a resolution of 4096x4096 [image: 1608070464202-direct-2048.png] The 5th Nomad mission with a direct lighting map at a resolution of 2048x2048 [image: 1608070469334-direct-1024.png] The 5th Nomad mission with a direct lighting map at a resolution of 1024x1024 [image: 1608070482592-direct-512.png] The 5th Nomad mission with a direct lighting map at a resolution of 512x512 [image: 1608070486612-direct-256.png] The 5th Nomad mission with a direct lighting map at a resolution of 256x256 [image: 1608070495230-direct-128.png] The 5th Nomad mission with a direct lighting map at a resolution of 128x128 The map in question is 20x20 with a heightmap of 1025x1025. In this case I've made sure there are no artifacts to be seen in Photoshop / during the initial tests. I think we could get away with using the 512x512 version which has essentially no impact on loading times. For smaller maps 512x512 would be more than sufficient and you could get away with less but that has no further impact on the loading time of the map.

Thanks for taking the time to write this up. Even a top player could learn some things from this. Personally, even though I had internalized a lot of these concepts, hearing it summarized in this fashion is very useful and helped me identify some areas where my decision making is not as strong.

It may, in some cases be too dense, but it works well for the size of maps usually involved with FAF - and it overcomes a lot of issues where maps are either poorly marked, or not marked at all - which is a big plus. On larger maps, this many nodes will cause some visible impact in game speed - especially as you get more AI involved.

This is phenomenally written and something I hope to see more of. Nice work, Jip!