Shadows and SSMF Broken on ATI, any way to fix?

[The Yak]

Specs:
AMD FX-6100 Bulldozer 3.4ghz
Windows 7 64-bit
8GB RAM
XFX Radeon HD 6850 (Catalyst 12.8)

I was okay with Shadows working only on units/ground decals and not terrain, but I've recently found out that you need shadows enabled (and I assume working) for SSMF to work. Since I'm in the middle of making a map, it would be of great interest for me to get both working so I can see if specularity is working on my map. :( Does anyone know of a way to fix this, or this is just one of those things that are completely broken with ATI?

EDIT: I've tried both /shadows 1 and /shadows 2, no shadows on terrain either way.

[Beherith]

Shadows are not needed for ssmf. If its still off, try /advmapshading 1

[Kloot]

http://i49.tinypic.com/n533h3.png appears to show some barely visible shadows (as well as specular highlights), so maybe you have just set groundShadowDensity too close to zero on your map?

[Beherith]

Post your .smd parameters please.

[The Yak]

http://i49.tinypic.com/n533h3.png appears to show some barely visible shadows (as well as specular highlights), so maybe you have just set groundShadowDensity too close to zero on your map?

Actually yes, I got shadows/ssmf working for this screenshot, forgot to update this post. Fixed it with /advmapshading 1 by trying out random engine settings. Thanks anyways.

Can't believe I've gone all this time without having SSMF or shadows working, heh... instant beautification for any map I play now. Makes me wonder how many people go without them because everyone just says that it's due to shitty AMD/ATI drivers and they have to get used to it or buy an Nvidia card, which was pretty much my situation. Wouldn't it make sense to have such an important visual setting enabled by default on higher-end cards?

[Beherith]

It is enabled by default.

Code: Select all

CONFIG(bool, AdvMapShading).defaultValue(true).safemodeValue(false);

[The Yak]

It is enabled by default.

Code: Select all

CONFIG(bool, AdvMapShading).defaultValue(true).safemodeValue(false);

Odd, I've done at least 2 clean installs on different computers with this problem, if the engine has it enabled by default then I guess something game-side must be turning it off. Zero-K used to crash for me on ultra settings and reset everything to safe mode, so I'm suspecting that's why. I'll look into it more.