.Map :: MoHAA Mapping

I still can ask stupid questions! Here they are:
I saw in this thread a parameter i never used before: -attenuate #
now, i can read the 'help' given by MOHlight itself and also the lines about it in the tutorial section, but i do not understand. Also, it seems to do not much, atleast in my testmap. Can someone explain what it means?
Then I found -border to add debugging borders of the lightmap. What is it good for? Looks funny, btw...

The attenuate setting affects the radiosity lighting. It basically defines the "reach" of the rad bounce, and softens the spherical edges.

-attenuate X adds an extra X% reduction in intensity per 16 grid over the reach of the light. Default is 4, so -attenuate 2 actually increases the sharpness of the light at distance, thus creating more distinct shadows. The effect is subtle, and often difficult to notice.

Consider it the difference between a clear glass lightbulb, and a frosted "soft white" light bulb.

Wacko wrote:Then I found -border to add debugging borders of the lightmap. What is it good for? Looks funny, btw...

Well I guess its to visualize that your light compile acts as you want, as te differences in light may sometimes be hard to detect...

thnx so far.
crunch, i'll do some other experiments, and hopefully i'll see the difference one fine day. but it's probably not that important anyway?! Or would u suggest certain values for special occasions? higher values for sunset maps, 0 for high noon?

bjarne, mmm, yes, u're probably right. but what is it good for? if a faulty light compile isn't visible by itself, why should I care?!

Wacko wrote:if a faulty light compile isn't visible by itself, why should I care?!

lol you have a point there

I think the debugging borders may actually be meant to debug mohlight.exe