Counter-Strike 2

Counter-Strike 2

View Stats:
Lynked Dec 16, 2014 @ 11:22am
Viewmodel not launching
Got a new viewmodel recently and as i always do when i get new settings for CS:GO i put it in my config and autoexec files, however my viewmodel seems to reset everything i start CS:GO. So everytime i start CS:GO i have to add the viewmodel through console. Anyone know how to possibly fix this?

Viewmodel is: viewmodel_fov 90
viewmodel_offset_x 22
viewmodel_offset_y 33
viewmodel_offset_z -22
cl_bob_lower_amt 15

And yes i have -exec autoexec in launch parameters.
< >
Showing 1-13 of 13 comments
apple Dec 16, 2014 @ 2:36pm 
Those command values go over the limits. You can't have viewmodel_fov being over 68, viewmodel_offset_x can't be over 2.5 etc.
Lynked Dec 17, 2014 @ 3:26am 
Originally posted by Omnom:
Those command values go over the limits. You can't have viewmodel_fov being over 68, viewmodel_offset_x can't be over 2.5 etc.
You can, they work when you put them in console.
apple Dec 17, 2014 @ 8:17am 
Originally posted by Nash:
Originally posted by Omnom:
Those command values go over the limits. You can't have viewmodel_fov being over 68, viewmodel_offset_x can't be over 2.5 etc.
You can, they work when you put them in console.

You can put them in the console but since those values go over the limits then the game automatically lowers them to the highest possible value i.e 68 for viewmodel_fov etc
Lynked Dec 17, 2014 @ 8:19am 
Originally posted by Omnom:
Originally posted by Nash:
You can, they work when you put them in console.

You can put them in the console but since those values go over the limits then the game automatically lowers them to the highest possible value i.e 68 for viewmodel_fov etc
So it's something "wrong" with the game then?
Lynked Dec 17, 2014 @ 8:24am 
Originally posted by $n@ke Eye$:
As previously mentioned, those values are too high and those settings do not save. They are reset back to the same amount everytime you launch the game.

Placing them in an autoexec.cfg doesn't help either, unless you type exec autoexec.cfg into console once you are ingme.
Wouldn't "host_writeconfig" overwrite the config file?
apple Dec 17, 2014 @ 8:50am 
Originally posted by Nash:
Originally posted by Omnom:

You can put them in the console but since those values go over the limits then the game automatically lowers them to the highest possible value i.e 68 for viewmodel_fov etc
So it's something "wrong" with the game then?

No not really, Valve decieded to have upper and lower limits to these commands.
videogames Dec 17, 2014 @ 9:15am 
It can save if you change viewmodel_presetpost to a different value. Set it to 4, or 0, or whatever else that isn't 1-3. You'll get a message saying that's not one of the default values, but it should stick.
Lynked Dec 17, 2014 @ 9:31am 
Originally posted by gordon:
Originally posted by $n@ke Eye$:
I think I figured out why your settings don't save.

It has to do with the viewmodel_presetpos command.

Mine is set at viewmodel_presetpos 3, so whenever the game is launched that setting reverts any custom settings.

We need Valve to fix it so it can be disabled so we can save custom settings.

It is indeed related to that command. set it to "0" to get an "invalid" value which won't load default viewmodel settings and will give you your custom viewmodel instead
Heard somewhere that setting it to "0" doesn't work
Lynked Dec 17, 2014 @ 9:37am 
Originally posted by videogames:
It can save if you change viewmodel_presetpost to a different value. Set it to 4, or 0, or whatever else that isn't 1-3. You'll get a message saying that's not one of the default values, but it should stick.
I already had mine set to "0", still won't launch my viewmodel. Any ideas?
Lynked Dec 17, 2014 @ 9:51am 
Originally posted by gordon:
Originally posted by Nash:
I already had mine set to "0", still won't launch my viewmodel. Any ideas?

put the command into autoexec, it should work. maybe try putting the command before the viewmodel_offset commands, and try execing your autoexec ingame once
Does nothing at all. But i did find this in console: exec: couldn't exec config.cfg
Lynked Dec 17, 2014 @ 9:56am 
Originally posted by gordon:
Originally posted by Nash:
Does nothing at all. But i did find this in console: exec: couldn't exec config.cfg

config.cfg? put all your commands you need into the "autoexec.cfg" file. create one if you don't have it
I have my commands set in both my cfg and autoexec.
Lynked Dec 17, 2014 @ 10:06am 
Pretty sure i fixed it, thanks for the help y'all
skape Jun 25, 2020 @ 3:48pm 
Originally posted by 7Seven7:
Pretty sure i fixed it, thanks for the help y'all
how?
< >
Showing 1-13 of 13 comments
Per page: 1530 50

Date Posted: Dec 16, 2014 @ 11:22am
Posts: 13