Every time I start ET, apparently regardless of mod loaded at startup time, r_overbrightbits is set from 2 (or 1.9, or where ever I put it last time I was playing) back to 1.000000. I’ve tried modifying all of my configuration files to show r_overbrightbits 2 and also tried setting it on the command line when the ET loads, but to no avail. Is there any way to make the game retain my r_overbrightbits setting, or must I set it and vid_restart every time I play? Or am I missing something really simple?
Any way to stop r_overbrightbits from resetting to 1?
Create a file in etmain called ‘autoexec.cfg’, then type the following inside it:
seta r_overbrightbits 2
I think that’ll work, anyway.
I’m not 100% sure about this, but I’d guess r_overbrightbits 1 is the default value and ET is restting it because you have a stray profile.pid file lurking about. Same as with the resolution continually reverting to default, if the file \etmain\profiles[i]yourname[/i]\profile.pid exists certain things get set back to default. Delete this file and your settings should stick.
run your config
vid_restart
Ive made that routine, before playing war…as soon as i join…i exec my config…and after that vid_restart…then im sure all is set…and not only “latched”.
Or you could just use 0 and not bother with it. :]
Or, make your config read only after setting the value so it CANT change it.
Doubtful, I run ET from a batch file which should delete these. I checked it to make sure it was deleting everything before replying here, which it appears to be doing.
Making the file read-only doesn’t stop the engine from doing what it wants (I think you’re underestimating John Carmack by a couple hundred IQ points), it just prevents it from showing the true values in the file.
This is what I do now. I want to stop doing it.
MOST LIKELY ANSWER TO MY ORIGINAL QUESTION: Maybe it doesn’t go up past 1. I had it set to 2 in RtCW, and, like a noob, assumed I could do the same in Enemy Territory. This would explain both why it appears the engine is clamping me (I’m set to exactly ‘1.000000’) and why all leagues I’ve seen permit only 0-1.
I’ve ask this question on the boards before and didn’t really get a concrete response.
It seems you CAN’T change it.
seta r_mapoverbrightbits, you can change, but r_overbrightbits doesn’t seem to change.
I also notice that when i type in the console,
/cvarlist r_overbrightbits, the value is ALWAYS 1.0 (or was it 1.000?), it doesn’t say “1” like the other cvar’s would.
don’t have a problem with these cvars in RtCW though…
Making it readonly stops ET from changing the value outside of the game. If you set it in config (bare in mind youll probs to delete other configs and the .pids. Dont expect the .bat file to do it all correctly… its flawed) and make sure its the only in use config it should exec at the value you have set then a case of vid_restart and your sorted. But, why 2? Wouldnt that just make it worse?
Cyber-Knight:
Did you read my last post? I think that ET will not accept values for r_overbrightbits higher than 1. I had assumed, retardedly, that I could still set it to 2 as I could in RtCW, but I think ET may only accept 0-1.
pgh:
- Are you telnetted into this box right now and proof-reading my batch file? If not, why are you telling me it’s flawed?
- Did you read all of my previous post? This is the important part:
MOST LIKELY ANSWER TO MY ORIGINAL QUESTION: Maybe it doesn’t go up past 1. I had it set to 2 in RtCW, and, like a noob, assumed I could do the same in Enemy Territory. This would explain both why it appears the engine is clamping me (I’m set to exactly ‘1.000000’) and why all leagues I’ve seen permit only 0-1.
umm… did you read my post in detail?
i addressed all your issues about /r_overbrightbits, and I have the same problems as you.
and I came to the conclusion that it can’t be changed. I’ve tried autoexec, i’ve tried the profiles, i’ve tried the mains. I try it in-game. even though it says “settings will be changed upon restart” I type vid_restart, and it’s still at 1.000.
There may be a reason why when you type “/cvarlist r_overbrightbits” the output number is ALWAYS 1.000, instead of just 1.
maybe you can look into the source code.
Okay then, I think what we’re trying to say is that we’ve come to the same conclusion, and we agree. That wasn’t so hard was it? I just thought it was odd that you were rehashing what I had written as though the issue hadn’t yet come up. Specifically: