You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to tweak the lighting settings to make the game look better, especially with the mission packs where there are a bunch of textures which are supposed to represent lights but are not recognized as such , so there are many completely dark areas...
To remedy this, I have set rt_elight_threshold to 0 which turns most textures into light sources, and it results in an even, flat environment lighting, the problem is it is also too bright...
Fortunately, there is the rt_elight_normaliz command which, when raised above the default value of 100, darkens the environment lights, and at a value around 300 to 1000, it looks quite similar to the original Quake
However whenever the level changes, this value changes back to 100, and it even overwrites the value within config.cfg so I cannot make the change permanent... Is there a way to stop it doing this?
The text was updated successfully, but these errors were encountered:
I am trying to tweak the lighting settings to make the game look better, especially with the mission packs where there are a bunch of textures which are supposed to represent lights but are not recognized as such , so there are many completely dark areas...
To remedy this, I have set rt_elight_threshold to 0 which turns most textures into light sources, and it results in an even, flat environment lighting, the problem is it is also too bright...
Fortunately, there is the rt_elight_normaliz command which, when raised above the default value of 100, darkens the environment lights, and at a value around 300 to 1000, it looks quite similar to the original Quake
However whenever the level changes, this value changes back to 100, and it even overwrites the value within config.cfg so I cannot make the change permanent... Is there a way to stop it doing this?
The text was updated successfully, but these errors were encountered: