Upvote Upvoted 2 Downvote Downvoted
fps_max in config does nothing
posted in Q/A Help
1
#1
1 Frags +

so i use tf2mate for a crosshair switcher, and for some reason fps_max isn't capping my frames. i've got 'fps_max 300' in both my autoexec.cfg and the settings.cfg execed from my autoexec. When I first launch tf2 in console when I type in fps_max the value is coming up as being 0. i wouldn't really care, but getting 500+ frames on jump maps makes the game really stutter a lot.

so i use tf2mate for a crosshair switcher, and for some reason fps_max isn't capping my frames. i've got 'fps_max 300' in both my autoexec.cfg and the settings.cfg execed from my autoexec. When I first launch tf2 in console when I type in fps_max the value is coming up as being 0. i wouldn't really care, but getting 500+ frames on jump maps makes the game really stutter a lot.
2
#2
1 Frags +

do you have a setting in one of your class configs that overrides it?

ex: fpx_max 0 in your soldier.cfg

do you have a setting in one of your class configs that overrides it?

ex: fpx_max 0 in your soldier.cfg
3
#3
0 Frags +

i can't check right now, but i don't believe so. my class configs only contain interp info and some tf2mate related stuff

i can't check right now, but i don't believe so. my class configs only contain interp info and some tf2mate related stuff
4
#4
0 Frags +

are you sure your cfg is in a right place? :D

are you sure your cfg is in a right place? :D
5
#5
7 Frags +

Ctrl+f fps_max in autoexec and every cfg autoexec calls. It's set to zero somewhere in there.

Ctrl+f fps_max in autoexec and every cfg autoexec calls. It's set to zero somewhere in there.
6
#6
1 Frags +

had a similar problem but i realised that nothing i write to my autoexec.cfg updated ingame

later found out that i had my autoexec.cfg in two places: Team Fortress 2/cfg and Team Fortress 2/tf/cfg

i always updated the one in /tf/cfg, and the file in Team Fortress/cfg was the one really connected to my game

also try -autoexec in properties
idk does it work

had a similar problem but i realised that nothing i write to my autoexec.cfg updated ingame

later found out that i had my autoexec.cfg in two places: Team Fortress 2/cfg and Team Fortress 2/tf/cfg

i always updated the one in /tf/cfg, and the file in Team Fortress/cfg was the one really connected to my game

also try -autoexec in properties
idk does it work
7
#7
0 Frags +
karppohlater found out that i had my autoexec.cfg in two places: Team Fortress 2/cfg and Team Fortress 2/tf/cfg

i'll check that out, i've only been updating my tf/cfg autoexec

[quote=karppoh]later found out that i had my autoexec.cfg in two places: Team Fortress 2/cfg and Team Fortress 2/tf/cfg
[/quote]

i'll check that out, i've only been updating my tf/cfg autoexec
8
#8
2 Frags +

wut, u should have it on
C:\Program Files\Steam\SteamApps\common\Team Fortress 2\tf\custom\customfoldername\cfg

wut, u should have it on
C:\Program Files\Steam\SteamApps\common\Team Fortress 2\tf\custom\customfoldername\cfg
9
#9
1 Frags +

yeah i had issues with that too just copy your autoexec into the correct place or else tf2 won't be able to find it

yeah i had issues with that too just copy your autoexec into the correct place or else tf2 won't be able to find it
10
#10
0 Frags +

The rest of my cfg works, though, and none of it is in my custom folder (to my knowledge). i'll try that out when i'm home

The rest of my cfg works, though, and none of it is in my custom folder (to my knowledge). i'll try that out when i'm home
11
#11
3 Frags +

annnnnnnnnnnnnnnnnnnnnd i'm an idiot. Literally 20 lines below where I put the fps_max command in was chris' fps cap section, which unsurprisingly contained "fps_max 0". removing that has got me capped at a cool 299

thanks everyone

annnnnnnnnnnnnnnnnnnnnd i'm an idiot. Literally 20 lines below where I put the fps_max command in was chris' fps cap section, which unsurprisingly contained "fps_max 0". removing that has got me capped at a cool 299

thanks everyone
Please sign in through STEAM to post a comment.