Remove

[Alpha]

Remove

[bvughtoonice]

I've never seen begin and end map cmds used before.. but it looks like that is the root of your problem

Try adding to your Cfg or auto exec some 3 new key binds

Bind key Gl modulate 50
Bind key gl modulate .5
Bind key vid_restart.

Do manually it should all work the way you expect by hitting the three keys

[M1SERY]

 If you know how to find him, ask Chief. Setting it up manually is the way I achieved it. btw you're gay for pay all day.

[Whirlingdervish]

You could probably script it with wait commands into an alias like people use for double jump aliases.

The getting the entities bright, while the map is not, will require gl_modulate to be changed to the higher one without doing a vid_restart after. When you change map tho, it will do the restart and you'd need to execute an alias on beginning the map that sets it back to normal, then re-applies the alias that make it bright.

[haunted]

What's the purpose of those commands anyway? You can narrow down stuff or a conflict with the exec command with combinations of vid_restart and map changes but this seems so trivial to me.

[bvughtoonice]

this is how it works in order.


gl_modulate .5

vid_restart

gl_modulate 50


hit those 3 keys in that order it will work, or type those 3 commands in same order.

or make an alias bind that does all those 3 commands with 1 key.

[|iR|Focalor]

I dunno that you'd even need to add aliases. Something like this might work...

bind x gl_modulate .5; wait; vid restart; wait; wait; gl_modulate 50

The wait commands might not be necessary at all, but I'd anticipate there could be a problem executing the last modulate 50 command since the console might try to run it before the video finishes completely restarting.

Edit: If you keep...

set cl_beginmapcmd "gl_modulate 50"
set cl_endmapcmd "gl_modulate .5"

...in your config, then that should negate the need to hit the bind EVERY map. Having it set up to where it'll work exactly the way you want without EVER having to manually change anything with a bind might be a bridge too far.

UNLESS...

I'm wondering if you could add more shit to the beginmapcmd. Instead of...

set cl_beginmapcmd "gl_modulate 50"

...maybe try like I suggested...

set cl_beginmapcmd "gl_modulate .5; wait; vid restart; wait; wait; gl_modulate 50"

[Zeppelin]

It worked in that order. Thanks. I ended up binding 3 keys. Don't know how to do aliases

lol
just use the semicolon ; separating the cmds and all of them inside marks " " and you can have them all in the same key!

bind x "gl_modulate .5; vid_restart; gl_modulate 50"

[|iR|Focalor]

It was kinda assumed that YOU ALREADY HAD THAT IN THERE, YOU WIENERHEAD! Jeez.

[Zeppelin]

It was kinda assumed that YOU ALREADY HAD THAT IN THERE, YOU WIENERHEAD! Jeez.

yeah WHAT THE HELL

[yahoo]

It was kinda assumed that YOU ALREADY HAD THAT IN THERE, YOU WIENERHEAD! Jeez.

yeah WHAT THE HELL

bind "h" heheh

[|iR|Focalor]

I wasn't trying to sound angry, I just thought it was funny he was boneheaded enough to remove that particular setting completely from his config.

If you leave it out of your autoexec config and then set the file to read only, the game is still gonna write something for gl_modulate to the base config based on the beginmap or endmap commands that are changing THAT VERY SETTING. Which means whilst that one line might not exist in your autoexec cfg, it DOES exist in the base cfg and changes based on the last beginmap/endmap command executed before the game was closed. Because the autoexec cfg stuffs shit to the base cfg, not the other way around. Thats what its for. So you can temporarily change settings on the fly, but have them revert back upon your next startup when the autoexec overwrites the basecfg AGAIN.

Anyway, I still think there's gotta be some clever way using aliases or something to automate that chain of commands to eliminate the need to hit a bind every time you start the game.