does any1 know or has a list of all settings that are forced in mm?
thanks
settings forced in mm
posted in
TF2 General Discussion
Better yet, if someone can make a list and also list the commands that are still changeable that benefit anything (performance, etc)
Better yet, if someone can make a list and also list the commands that are still changeable that benefit anything (performance, etc)
how is forcing jigglebones making a 'level playing field'
how is forcing jigglebones making a 'level playing field'
EoNhow is forcing jigglebones making a 'level playing field'
the only thing i can think of for "level playing field" is ragdolls and gibs will be a distraction and block visoin for everyone now.
also the grass in process second and some other places, that you dont see if you have a FPS config, but thats such a small thing
Maybe what they meant is making the game run like crap for everyone
[quote=EoN]how is forcing jigglebones making a 'level playing field'[/quote]
the only thing i can think of for "level playing field" is ragdolls and gibs will be a distraction and block visoin for everyone now.
also the grass in process second and some other places, that you dont see if you have a FPS config, but thats such a small thing
Maybe what they meant is making the game run like crap for everyone
the only thing i can think of for "level playing field" is ragdolls and gibs will be a distraction and block visoin for everyone now.
also the grass in process second and some other places, that you dont see if you have a FPS config, but thats such a small thing
Maybe what they meant is making the game run like crap for everyone
I can understand why they'd want to force some really obscure settings. Even having settings like that that exist that give insiders that know about them a pretty big advantage (in regards to performance) is definitely an issue. Moreso if they have to spend extra time supporting those settings.
I especially understand not wanting to support DX8. It's fucking old. People only used it to boost performance because it turns some stupid things off.
But the answer isn't to force high settings on everyone. The right answer to that is to make a new fucking advanced video options menu with all of those damn variables so they can be configured (if desired) by end-users. And make them actually change when general graphics settings change, which a lot of them don't currently do.
I can understand why they'd want to force some really obscure settings. Even having settings like that that exist that give insiders that know about them a pretty big advantage (in regards to performance) is definitely an issue. Moreso if they have to spend extra time supporting those settings.
I especially understand not wanting to support DX8. It's fucking [i]old[/i]. People only used it to boost performance because it turns some stupid things off.
But the answer isn't to force high settings on everyone. The right answer to that is to [i]make a new fucking advanced video options menu[/i] with all of those damn variables so they can be configured (if desired) by end-users. And make them actually change when general graphics settings change, which a lot of them don't currently do.
I especially understand not wanting to support DX8. It's fucking [i]old[/i]. People only used it to boost performance because it turns some stupid things off.
But the answer isn't to force high settings on everyone. The right answer to that is to [i]make a new fucking advanced video options menu[/i] with all of those damn variables so they can be configured (if desired) by end-users. And make them actually change when general graphics settings change, which a lot of them don't currently do.
STOGEBetter yet, if someone can make a list and also list the commands that are still changeable that benefit anything (performance, etc)
You can exec your config once again after joining a mm game. Those commands that aren't locked would be set the way they're in your config.
[quote=STOGE]Better yet, if someone can make a list and also list the commands that are still changeable that benefit anything (performance, etc)[/quote]
You can exec your config once again after joining a mm game. Those commands that aren't locked would be set the way they're in your config.
You can exec your config once again after joining a mm game. Those commands that aren't locked would be set the way they're in your config.
There are some things I'm ok with forcing like overlays because they literally change the way people communicate but the overwhelming majority of commands in simple FPS configs are important. Come up with a list of specific PLEASE UNBLOCK THESE settings. Fixing some settings that really should not be reset by the game on every map change like they currently are (cl_detaildist and cl_detailfade) would be nice too.
A lot of performance options in TF2 have absolutely negligible effect on gameplay and just turn off eyecandy. Overwhelmingly locking these settings by default is silly at best and against the competitive spirit by default. Performance settings exist so that people with weak PCs can trade away eyecandy in return for performance. Performance is not a secondary matter for competitive play. The game already has a lot of performance-vs-visuals settings literally built in. Some of them shouldn't exist because they affect gameplay so much (hello r_renderoverlayfragment!) but so many of them give an incredible performance gain in return for making some random detail of the game look slightly worse in a way that doesn't affect gameplay in any meaningful way whatsoever.
I don't have a list of all settings that comp disables so I'm just going to pull out obvious settings that I can't find in the video options or advanced options menus. If any of these are unlocked then just ignore them.
Repeat: This is not a list of some of the settings that comp disables. This is a list of settings that should definitely not be disabled in the way settings are currently disabled, and I'm assuming they're disabled because I can't determine that they're not disabled.
MASSIVE performance effect:
cl_detaildist controls the fading-out-at-distance of displacement foliage sprites e.g. grass; the default settings are a HUGE performance sink on some maps like cp_sunshine
cl_detailfade see above
cl_jiggle_bone_framerate_cutoff should obviously be user-configurable because different people place "good performance" at different framerates.
cl_ragdoll_forcefade, cl_ragdoll_physics_enable, cl_ragdoll_collide, ragdoll_sleepaftertime, cl_ragdoll_fade_time
not all of these are necessary to get good performance, just add a "disable ragdolls" switch and make it do the right thing: when high performance deaths are turned on for better performance, player models should fade out over a very short period of time when you kill them instead of making a ragdoll. I don't even care about gibs but they matter too. Do the right thing.
mat_phong
r_3dsky on badly optimized maps
MASSIVE gameplay effect:
cl_cmdrate
cl_updaterate
cl_interp
cl_interp_ratio
^---- These are all constrained by server settings in the first place! if you need to constrain them for fairness and correctness, Use Those! (add a lower cap to cl_interp too tbh, you should not be able to use 500ms interp)
Low updaterates and high interp dramatically increase the latency of projectile weapons and other players' character models. Updaterate applies a floor to the interp window and high interp is basically the same thing as high ping. Lowering these settings (like CSGO does by default!) is literally the most overwhelmingly and unarguably gameplay-improving thing that comp players do.
MASSIVE obnoxious visual effect:
mat_non_hdr_bloom_scalefactor I want to be able to reduce bloom without completely disabling it. Some maps have way too much bloom but some maps use HDR settings that make the outdoors too dark in HDR mode if bloom is fully disabled. Some maps have outright broken lighting settings in LDR mode, too.
cl_smoothtime (first-person input prediction error smoothing period)
other:
r_drawflecks
snd_mixahead engine's audio latency floor. setting this to around 0.05 is literally one of the first things I do when I install a new source engine game.
cl_phys_props_max for badly optimized maps
r_worldlights for badly optimized maps (restricting this to 2 or so might be a good idea because it affects player visibility a lot)
snd_async_fullyasync 1 historically dramatically improves hitching for some people
btw add real transparent viewmodels, minmode viewmodels are not enough
There are some things I'm ok with forcing like overlays because they literally change the way people communicate but the overwhelming majority of commands in simple FPS configs are important. Come up with a list of specific PLEASE UNBLOCK THESE settings. Fixing some settings that really should not be reset by the game on every map change like they currently are (cl_detaildist and cl_detailfade) would be nice too.
A lot of performance options in TF2 have absolutely negligible effect on gameplay and just turn off eyecandy. Overwhelmingly locking these settings by default is silly at best and against the competitive spirit by default. Performance settings exist so that people with weak PCs can trade away eyecandy in return for performance. Performance is not a secondary matter for competitive play. The game already has a lot of performance-vs-visuals settings literally built in. Some of them shouldn't exist because they affect gameplay so much (hello r_renderoverlayfragment!) but so many of them give an incredible performance gain in return for making some random detail of the game look slightly worse in a way that doesn't affect gameplay in any meaningful way whatsoever.
[i]I don't have a list of all settings that comp disables[/i] so I'm just going to pull out obvious settings that I can't find in the video options or advanced options menus. If any of these are unlocked then just ignore them.
Repeat: [i]This is not a list of some of the settings that comp disables. This is a list of settings that should definitely not be disabled in the way settings are currently disabled, and I'm assuming they're disabled because I can't determine that they're not disabled.[/i]
MASSIVE performance effect:
cl_detaildist controls the fading-out-at-distance of displacement foliage sprites e.g. grass; the default settings are a HUGE performance sink on some maps like cp_sunshine
cl_detailfade see above
cl_jiggle_bone_framerate_cutoff should obviously be user-configurable because different people place "good performance" at different framerates.
cl_ragdoll_forcefade, cl_ragdoll_physics_enable, cl_ragdoll_collide, ragdoll_sleepaftertime, cl_ragdoll_fade_time
not all of these are necessary to get good performance, just add a "disable ragdolls" switch and make it do the right thing: when high performance deaths are turned on for better performance, player models should fade out over a very short period of time when you kill them instead of making a ragdoll. I don't even care about gibs but they matter too. Do the right thing.
mat_phong
r_3dsky on badly optimized maps
MASSIVE gameplay effect:
cl_cmdrate
cl_updaterate
cl_interp
cl_interp_ratio
^---- These are all constrained by server settings in the first place! if you need to constrain them for fairness and correctness, Use Those! (add a lower cap to cl_interp too tbh, you should not be able to use 500ms interp)
Low updaterates and high interp dramatically increase the latency of projectile weapons and other players' character models. Updaterate applies a floor to the interp window and high interp is basically the same thing as high ping. Lowering these settings (like CSGO does by default!) is literally the most overwhelmingly and unarguably gameplay-improving thing that comp players do.
MASSIVE obnoxious visual effect:
mat_non_hdr_bloom_scalefactor I want to be able to reduce bloom without completely disabling it. Some maps have way too much bloom but some maps use HDR settings that make the outdoors too dark in HDR mode if bloom is fully disabled. Some maps have outright broken lighting settings in LDR mode, too.
cl_smoothtime (first-person input prediction error smoothing period)
other:
r_drawflecks
snd_mixahead engine's audio latency floor. setting this to around 0.05 is literally one of the first things I do when I install a new source engine game.
cl_phys_props_max for badly optimized maps
r_worldlights for badly optimized maps (restricting this to 2 or so might be a good idea because it affects player visibility a lot)
snd_async_fullyasync 1 historically dramatically improves hitching for some people
btw add real transparent viewmodels, minmode viewmodels are not enough
A lot of performance options in TF2 have absolutely negligible effect on gameplay and just turn off eyecandy. Overwhelmingly locking these settings by default is silly at best and against the competitive spirit by default. Performance settings exist so that people with weak PCs can trade away eyecandy in return for performance. Performance is not a secondary matter for competitive play. The game already has a lot of performance-vs-visuals settings literally built in. Some of them shouldn't exist because they affect gameplay so much (hello r_renderoverlayfragment!) but so many of them give an incredible performance gain in return for making some random detail of the game look slightly worse in a way that doesn't affect gameplay in any meaningful way whatsoever.
[i]I don't have a list of all settings that comp disables[/i] so I'm just going to pull out obvious settings that I can't find in the video options or advanced options menus. If any of these are unlocked then just ignore them.
Repeat: [i]This is not a list of some of the settings that comp disables. This is a list of settings that should definitely not be disabled in the way settings are currently disabled, and I'm assuming they're disabled because I can't determine that they're not disabled.[/i]
MASSIVE performance effect:
cl_detaildist controls the fading-out-at-distance of displacement foliage sprites e.g. grass; the default settings are a HUGE performance sink on some maps like cp_sunshine
cl_detailfade see above
cl_jiggle_bone_framerate_cutoff should obviously be user-configurable because different people place "good performance" at different framerates.
cl_ragdoll_forcefade, cl_ragdoll_physics_enable, cl_ragdoll_collide, ragdoll_sleepaftertime, cl_ragdoll_fade_time
not all of these are necessary to get good performance, just add a "disable ragdolls" switch and make it do the right thing: when high performance deaths are turned on for better performance, player models should fade out over a very short period of time when you kill them instead of making a ragdoll. I don't even care about gibs but they matter too. Do the right thing.
mat_phong
r_3dsky on badly optimized maps
MASSIVE gameplay effect:
cl_cmdrate
cl_updaterate
cl_interp
cl_interp_ratio
^---- These are all constrained by server settings in the first place! if you need to constrain them for fairness and correctness, Use Those! (add a lower cap to cl_interp too tbh, you should not be able to use 500ms interp)
Low updaterates and high interp dramatically increase the latency of projectile weapons and other players' character models. Updaterate applies a floor to the interp window and high interp is basically the same thing as high ping. Lowering these settings (like CSGO does by default!) is literally the most overwhelmingly and unarguably gameplay-improving thing that comp players do.
MASSIVE obnoxious visual effect:
mat_non_hdr_bloom_scalefactor I want to be able to reduce bloom without completely disabling it. Some maps have way too much bloom but some maps use HDR settings that make the outdoors too dark in HDR mode if bloom is fully disabled. Some maps have outright broken lighting settings in LDR mode, too.
cl_smoothtime (first-person input prediction error smoothing period)
other:
r_drawflecks
snd_mixahead engine's audio latency floor. setting this to around 0.05 is literally one of the first things I do when I install a new source engine game.
cl_phys_props_max for badly optimized maps
r_worldlights for badly optimized maps (restricting this to 2 or so might be a good idea because it affects player visibility a lot)
snd_async_fullyasync 1 historically dramatically improves hitching for some people
btw add real transparent viewmodels, minmode viewmodels are not enough
wareyaSome maps have way too much bloom but some maps use HDR settings that make the outdoors too dark in HDR mode if bloom is fully disabled.
i'm looking at you, metalworks. i sure hope that map was recompiled properly before being included because fuck that.
[quote=wareya]Some maps have way too much bloom but some maps use HDR settings that make the outdoors too dark in HDR mode if bloom is fully disabled.[/quote]
i'm looking at you, metalworks. i sure hope that map was recompiled properly before being included because fuck that.
i'm looking at you, metalworks. i sure hope that map was recompiled properly before being included because fuck that.
Please
sign in through STEAM
to post a comment.