Been trying to figure this out for awhile and it's been bothering me a bit. Theres like 3 or 4 settings that just refuse to save. Them being Crosshair color, teammate autocall, autoheal and display a marker over patient. For some reason even if I apply these settings they never save and I need to redo them every time I launch TF2. I was trying to figure out console commands but didn't know exactly what to do.
Certain settings not saving.
posted in
Q/A Help
Been trying to figure this out for awhile and it's been bothering me a bit. Theres like 3 or 4 settings that just refuse to save. Them being Crosshair color, teammate autocall, autoheal and display a marker over patient. For some reason even if I apply these settings they never save and I need to redo them every time I launch TF2. I was trying to figure out console commands but didn't know exactly what to do.
Crosshair color consists of 3 commands, cl_crosshair_blue and then red and green instead of blue. Can be anything from 0 to 255 for each. hud_medicautocallers 1 is to turn on autocall. tf_medigun_autoheal 1 is to turn on autoheal. hud_medichealtartgetmarker 1 is to turn on marker over patient. If you put all of those in your autoexec.cfg file, it should re-execute them every time you restart.
Crosshair color consists of 3 commands, cl_crosshair_blue and then red and green instead of blue. Can be anything from 0 to 255 for each. hud_medicautocallers 1 is to turn on autocall. tf_medigun_autoheal 1 is to turn on autoheal. hud_medichealtartgetmarker 1 is to turn on marker over patient. If you put all of those in your autoexec.cfg file, it should re-execute them every time you restart.
probably a longshot but in your custom cfg folder see if you have config.cfg and if you do delete it
probably a longshot but in your custom cfg folder see if you have config.cfg and if you do delete it
When you edit your config, you need to edit the ones that are in custom > my_stuff (or whatever you named it).
If you are changing stuff through you console or in-game tf2 options, the game saves it to 'tf > cfg > config.cfg', which is wrong, so here's what I did to make those changes:
1.) Save '\custom\my_stuff\config.cfg' over the 'tf\cfg\config.cfg' file (this keeps your current binds and other configs).
2.) Re-launch tf2 and make the in-game option changes you want, then close it.
3.) Copy the 'tf\cfg\config.cfg' file and paste it over and replace the 'custom\my_stuff\config.cfg' file.
Check and see if that fixed it. If it didn't or you're confused (cause I suck ass at explaining), then just add me or something.
EDIT: Easier way is what Whoopee_Cushion said. If you find and put all the commands for those in-game options in your autoexec, it'll just set them everytime you launch tf2 anyways.
When you edit your config, you need to edit the ones that are in custom > my_stuff (or whatever you named it).
If you are changing stuff through you console or in-game tf2 options, the game saves it to 'tf > cfg > config.cfg', which is wrong, so here's what I did to make those changes:
1.) Save '\custom\my_stuff\config.cfg' over the 'tf\cfg\config.cfg' file (this keeps your current binds and other configs).
2.) Re-launch tf2 and make the in-game option changes you want, then close it.
3.) Copy the 'tf\cfg\config.cfg' file and paste it over and replace the 'custom\my_stuff\config.cfg' file.
Check and see if that fixed it. If it didn't or you're confused (cause I suck ass at explaining), then just add me or something.
EDIT: Easier way is what Whoopee_Cushion said. If you find and put all the commands for those in-game options in your autoexec, it'll just set them everytime you launch tf2 anyways.
If you are changing stuff through you console or in-game tf2 options, the game saves it to 'tf > cfg > config.cfg', which is wrong, so here's what I did to make those changes:
1.) Save '\custom\my_stuff\config.cfg' over the 'tf\cfg\config.cfg' file (this keeps your current binds and other configs).
2.) Re-launch tf2 and make the in-game option changes you want, then close it.
3.) Copy the 'tf\cfg\config.cfg' file and paste it over and replace the 'custom\my_stuff\config.cfg' file.
Check and see if that fixed it. If it didn't or you're confused (cause I suck ass at explaining), then just add me or something.
EDIT: Easier way is what Whoopee_Cushion said. If you find and put all the commands for those in-game options in your autoexec, it'll just set them everytime you launch tf2 anyways.
Yeah I had to put ragdoll commands on my class configs because they wouldn't save or run on the autoexec
Yeah I had to put ragdoll commands on my class configs because they wouldn't save or run on the autoexec
fishprobably a longshot but in your custom cfg folder see if you have config.cfg and if you do delete it
I think that was the problem, it wasn't overwriting this file so be getting the default one every time.
I'm going to add the commands to my autoexec just incase thought. Thanks everybody for the help
[quote=fish]probably a longshot but in your custom cfg folder see if you have config.cfg and if you do delete it[/quote]
I think that was the problem, it wasn't overwriting this file so be getting the default one every time.
I'm going to add the commands to my autoexec just incase thought. Thanks everybody for the help
I think that was the problem, it wasn't overwriting this file so be getting the default one every time.
I'm going to add the commands to my autoexec just incase thought. Thanks everybody for the help
RawrSpoonYeah I had to put ragdoll commands on my class configs because they wouldn't save or run on the autoexec
Just make sure you don't put too many commands like that in your class files. I tried to put almost an entire fps config in my class files once, and it created a ridiculous lag when changing classes. Just something that if you have it will be really noticeable and frustrating, but if not, you're not doing anything wrong.
[quote=RawrSpoon]Yeah I had to put ragdoll commands on my class configs because they wouldn't save or run on the autoexec[/quote]
Just make sure you don't put too many commands like that in your class files. I tried to put almost an entire fps config in my class files once, and it created a ridiculous lag when changing classes. Just something that if you have it will be really noticeable and frustrating, but if not, you're not doing anything wrong.
Just make sure you don't put too many commands like that in your class files. I tried to put almost an entire fps config in my class files once, and it created a ridiculous lag when changing classes. Just something that if you have it will be really noticeable and frustrating, but if not, you're not doing anything wrong.
Please
sign in through STEAM
to post a comment.