When I start up an offline server and play co_sava, it says when I join 'Gamma set to 1.6'.

When I changelevel to co_pulse, it says 'Gamma set to 1.7'.

My map is called ns_sekhmet, it has an env_gamma in it set to 1.0. The gamma setting in Batch Compiler is 0.5.

When I then changelevel to my map, from pulse, it again says 'Gamma set to 1.7'. Then, if I either a) hit escape twice, or b) hit the console key twice, it then says 'Gamma set to 1.0' and the lighting levels look correct.

Why isn't it set when I enter the map? Does anyone know why it requires a console or escape 'refresh' to be set correctly? This is something that I have to get fixed :s

Any help or suggestions would be appreciated

PHASED to map help. Try and keep it in the right forums.

On the topic, unfortunately, I have no idea. That's just plain weird.

The reason you have to press esc twice is because (afaik) is because it doesn't seem to change it when it just 1.0 and instead keeps the previous maps gamma setting on map change unless there is a new one telling it otherwise.

But as I said, there IS a new one telling it otherwise.

Unless you're saying it only doesn't work with setting of 1.0?

the gamma value your talking about is set by a env_gamma point entity that is placed in the map before compile. put one in your map with a value between 1.0 and 2.0. u should then see the difference. Do a small test map wit a couple text lights to compair, and a few different values for the gamma ramp.

Just don't set it to 1.0 if you hardly want it, set it to 1.1

The gamma setting for your compile is completely independent of the gamma setting that is listed when you open the map. That is controlled by the env_gamma entity, and without it, the map will just use the previous map's gamma.