Is it possible to have a config similar to the comp config but with high textured viewmodels for the new warpaints? Without increasing the textures of everything else?
BenNZLIs it possible to have a config similar to the comp config but with high textured viewmodels for the new warpaints? Without increasing the textures of everything else?
You can't selectively change texture quality. If you want decent looking war paints, you will have to use mat_picmip 0.
Just add that to a new custom.cfg and uncomment exec custom in comfig.cfg and you should be good to go.
You can't selectively change texture quality. If you want decent looking war paints, you will have to use mat_picmip 0.
Just add that to a new custom.cfg and uncomment exec custom in comfig.cfg and you should be good to go.
I'm using the preset maxperformance and I'm not able to put tf2 into dx8 mode using -dxlevel 81 in my launch options. Any ideas?
LetMeStallI'm using the preset maxperformance and I'm not able to put tf2 into dx8 mode using -dxlevel 81 in my launch options. Any ideas?
check comfig.cfg
theres a part that says "mat_dxlevel 95"
change it to "mat_dxlevel 81"
check comfig.cfg
theres a part that says "mat_dxlevel 95"
change it to "mat_dxlevel 81"
LetMeStallI'm using the preset maxperformance and I'm not able to put tf2 into dx8 mode using -dxlevel 81 in my launch options. Any ideas?
Change mat_dxlevel in the init section of comfig.cfg.
EDIT: ninja'd. curse you slow internet!
Change mat_dxlevel in the init section of comfig.cfg.
EDIT: ninja'd. curse you slow internet!
Ninlopim having an issue where i literally can not move or shoot only with this config, all my bindings are correct but for some reason with this config installed i cant move or shoot
Hi, just enter host_thread_mode 0 into console, and host_thread_mode 1 when you're done in your local server.
(as said in the troubleshooting wiki page, in a comment at the top of the config and printed to console.)
Could I get some advice on where else to put it?
Hi, just enter host_thread_mode 0 into console, and host_thread_mode 1 when you're done in your local server.
(as said in the [url=https://github.com/mastercoms/tf2cfg/wiki/Troubleshooting]troubleshooting[/url] wiki page, in [url=https://github.com/mastercoms/tf2cfg/blob/master/mastercomfig/cfg/comfig.cfg#L8]a comment[/url] at the top of the config and [url=https://github.com/mastercoms/tf2cfg/blob/master/mastercomfig/cfg/comfig.cfg#L1049]printed to console[/url].)
Could I get some advice on where else to put it?
in a file in all caps at the top level of the repository
IF_YOU_CANT_MOVE_OR_SHOOT_USE_host_thread_mode_0.fcku
IF_YOU_CANT_MOVE_OR_SHOOT_USE_host_thread_mode_0.fcku
4.5.6 released with documentation improvements, file cleanup and a party bug fix.
Also thank you for 100 frags!!! woooo
Also thank you for 100 frags!!! woooo
Hey mastercoms I was wondering which I should choose:
snd_async_minsize 0 // Do not wait for audio file loading for SSDs
snd_async_minsize 262144 // Wait longer for CPUs with less than 4 cores
As I have an SSD, but only 2 cores, thanks
snd_async_minsize 0 // Do not wait for audio file loading for SSDs
snd_async_minsize 262144 // Wait longer for CPUs with less than 4 cores
As I have an SSD, but only 2 cores, thanks
BrimstoneHey mastercoms I was wondering which I should choose:
snd_async_minsize 0 // Do not wait for audio file loading for SSDs
snd_async_minsize 262144 // Wait longer for CPUs with less than 4 cores
As I have an SSD, but only 2 cores, thanks
Sorry, I meant that comment for CPUs with less than 4 cores with HDDs. Though, are you having any problems with snd_async_minsize 0, like any stuttering? If so, use a higher setting for it.
snd_async_minsize 0 // Do not wait for audio file loading for SSDs
snd_async_minsize 262144 // Wait longer for CPUs with less than 4 cores
As I have an SSD, but only 2 cores, thanks[/quote]
Sorry, I meant that comment for CPUs with less than 4 cores with HDDs. Though, are you having any problems with snd_async_minsize 0, like any stuttering? If so, use a higher setting for it.
reposting in a more relevant thread
lootI notice some servers lately blocking cl_interp_ratio 2 (always stays at 1 when you try to change it) so I've had to go back to using cl_interp when I want to change lerp, can anybody else confirm this?
[quote=loot]I notice some servers lately blocking cl_interp_ratio 2 (always stays at 1 when you try to change it) so I've had to go back to using cl_interp when I want to change lerp, can anybody else confirm this?[/quote]
lootI notice some servers lately blocking cl_interp_ratio 2 (always stays at 1 when you try to change it) so I've had to go back to using cl_interp when I want to change lerp, can anybody else confirm this?
Not sure what's there to confirm, if you can't change cl_interp_ratio while in spectating, then the server is restricting it and you'll have to use cl_interp.
Not sure what's there to confirm, if you can't change cl_interp_ratio while in spectating, then the server is restricting it and you'll have to use cl_interp.
loot
AFC config enforces cl_interp_ratio 1 and net_splitpactet_maxrate 100000
AFC config enforces cl_interp_ratio 1 and net_splitpactet_maxrate 100000
what is the reason for enforcing cl_interp_ratio 1? Some exploit?
According to natapon, it is to prevent players from abusing it, but I think that was in the old days.
I have 2 possible recommendations for the config.
1) Maybe move info about dxlevel launch options to where the mat_dxlevel options are and specify that you need both to effectively change the dxlevel. It seems kind of confusing how it is at the moment. I.E: Someone may just change to the mat_dxlevel 90 option and not realize they need to add and then remove the dxlevel launch option to completely change over.
2) Maybe have the exec custom uncommented by default? I think it would be much nicer for people updating the config to be able to just copy paste/drag drop and not worry about having to change it every time. It isn't particularly difficult to change it, but just a bit nicer not to have to. That or maybe having autoexec removed and just having people execute themselves in their own autoexec? IDK, I just feel that it's easier to maintain for users that way.
1) Maybe move info about dxlevel launch options to where the mat_dxlevel options are and specify that you need both to effectively change the dxlevel. It seems kind of confusing how it is at the moment. I.E: Someone may just change to the mat_dxlevel 90 option and not realize they need to add and then remove the dxlevel launch option to completely change over.
2) Maybe have the exec custom uncommented by default? I think it would be much nicer for people updating the config to be able to just copy paste/drag drop and not worry about having to change it every time. It isn't particularly difficult to change it, but just a bit nicer not to have to. That or maybe having autoexec removed and just having people execute themselves in their own autoexec? IDK, I just feel that it's easier to maintain for users that way.
DulZuroI have 2 possible recommendations for the config.
1) Maybe move info about dxlevel launch options to where the mat_dxlevel options are and specify that you need both to effectively change the dxlevel. It seems kind of confusing how it is at the moment. I.E: Someone may just change to the mat_dxlevel 90 option and not realize they need to add and then remove the dxlevel launch option to completely change over.
2) Maybe have the exec custom uncommented by default? I think it would be much nicer for people updating the config to be able to just copy paste/drag drop and not worry about having to change it every time. It isn't particularly difficult to change it, but just a bit nicer not to have to. That or maybe having autoexec removed and just having people execute themselves in their own autoexec? IDK, I just feel that it's easier to maintain for users that way.
Thank you for the suggestions.
1) I will add a note to check the top of the config in the init section and installation instructions. I want it at the top of comfig so it is more likely for people to see they need to change -dxlevel and mat_dxlevel.
2) I'll have to think a bit more about how a better exec system would be implemented to solve this issue.
1) Maybe move info about dxlevel launch options to where the mat_dxlevel options are and specify that you need both to effectively change the dxlevel. It seems kind of confusing how it is at the moment. I.E: Someone may just change to the mat_dxlevel 90 option and not realize they need to add and then remove the dxlevel launch option to completely change over.
2) Maybe have the exec custom uncommented by default? I think it would be much nicer for people updating the config to be able to just copy paste/drag drop and not worry about having to change it every time. It isn't particularly difficult to change it, but just a bit nicer not to have to. That or maybe having autoexec removed and just having people execute themselves in their own autoexec? IDK, I just feel that it's easier to maintain for users that way.[/quote]
Thank you for the suggestions.
1) I will add a note to check the top of the config in the init section and installation instructions. I want it at the top of comfig so it is more likely for people to see they need to change -dxlevel and mat_dxlevel.
2) I'll have to think a bit more about how a better exec system would be implemented to solve this issue.
+1 for default uncommented "exec custom". Having no autoexec in config will not work with simple copy-paste. Having "exec custom" uncommented is better because it will be easier to update (with copy-paste or some git automation idk). custom.cfg is not present and unless you create one, it will simply be skipped (printed to console "custom.cfg not present, not executing)
I've having random sounds not play such as deflects or gunshots and I think it's because of async audio. Running from an SSD btw.
VantavimeowI've having random sounds not play such as deflects or gunshots and I think it's because of async audio. Running from an SSD btw.
I'm currently investigating possible fixes to this issue, with some work on it done in 5.0.0.
5.0.0 released with revamped folder structure, formatting improvements, comment improvements, sound fixes, performance optimizations and new stripped quality addon.
I'm currently investigating possible fixes to this issue, with some work on it done in 5.0.0.
[quote][/quote]
[url=https://github.com/mastercoms/tf2cfg/releases/tag/5.0.0]5.0.0[/url] released with revamped folder structure, formatting improvements, comment improvements, sound fixes, performance optimizations and new stripped quality addon.
Is there a way to use your max performance cfg but not have the game so dark. I hate it being so dark in certain areas and I don't like how the transition on lighting is non-existent. Real picky request but what console commands would brighten up the world so that lighting isn't so drastic.
AbridgeIs there a way to use your max performance cfg but not have the game so dark. I hate it being so dark in certain areas and I don't like how the transition on lighting is non-existent. Real picky request but what console commands would brighten up the world so that lighting isn't so drastic.
r_worldlightmin 0.004
r_worldlightmin 0.004
do you know if skins / warpaints affect fps at all?
because i benchmarked ur config with dx90 and dx81 a few days ago and appareantly and they both had the exact same results, but i feel like i get less fps in dx9
i used the old "benchmark1" demo which is quite old and doesnt show any war paints or skins in that demo cuz they didnt exist back then
because i benchmarked ur config with dx90 and dx81 a few days ago and appareantly and they both had the exact same results, but i feel like i get less fps in dx9
i used the old "benchmark1" demo which is quite old and doesnt show any war paints or skins in that demo cuz they didnt exist back then
smesido you know if skins / warpaints affect fps at all?
because i benchmarked ur config with dx90 and dx81 a few days ago and appareantly and they both had the exact same results, but i feel like i get less fps in dx9
i used the old "benchmark1" demo which is quite old and doesnt show any war paints or skins in that demo cuz they didnt exist back then
DirectX 9 is much more efficient renderer that uses your graphics card more effectively. And about skins, they shouldn't affect FPS too much except for the initial generation.
I've made a very basic new benchmark that should be better at testing FPS on modern TF2 for now.
because i benchmarked ur config with dx90 and dx81 a few days ago and appareantly and they both had the exact same results, but i feel like i get less fps in dx9
i used the old "benchmark1" demo which is quite old and doesnt show any war paints or skins in that demo cuz they didnt exist back then[/quote]
DirectX 9 is much more efficient renderer that uses your graphics card more effectively. And about skins, they shouldn't affect FPS too much except for the initial generation.
I've made a very basic [url=http://www.teamfortress.tv/42867/mastercomfig-fps-customization-config/?page=19#556]new benchmark[/url] that should be better at testing FPS on modern TF2 for now.
mastercomsDirectX 9 is much more efficient renderer that uses your graphics card more effectively. And about skins, they shouldn't affect FPS too much except for the initial generation.
I've made a very basic new benchmark that should be better at testing FPS on modern TF2 for now.
thanks for the somewhat fast response, i dont think i have a graphics card iirc and if i do its barely noticeable / really bad.
also here are the benchmarks with that new demo u posted
4812 frames 109.179 seconds 44.07 fps (22.69 ms/f) 6.695 fps variability
dx95
4812 frames 109.850 seconds 43.81 fps (22.83 ms/f) 6.199 fps variability
dx81
4812 frames 98.275 seconds 48.96 fps (20.42 ms/f) 7.023 fps variability
it looks like i get overall better fps on dx81 although i could be wrong since idk much about comparing benchmarks so
DirectX 9 is much more efficient renderer that uses your graphics card more effectively. And about skins, they shouldn't affect FPS too much except for the initial generation.
I've made a very basic [url=http://www.teamfortress.tv/42867/mastercomfig-fps-customization-config/?page=19#556]new benchmark[/url] that should be better at testing FPS on modern TF2 for now.[/quote]
thanks for the somewhat fast response, i dont think i have a graphics card iirc and if i do its barely noticeable / really bad.
also here are the benchmarks with that new demo u posted
[spoiler]dx90
4812 frames 109.179 seconds 44.07 fps (22.69 ms/f) 6.695 fps variability
dx95
4812 frames 109.850 seconds 43.81 fps (22.83 ms/f) 6.199 fps variability
dx81
4812 frames 98.275 seconds 48.96 fps (20.42 ms/f) 7.023 fps variability[/spoiler]
it looks like i get overall better fps on dx81 although i could be wrong since idk much about comparing benchmarks so
I sort of feel like the command that lets you see shadows through walls should be in the compquality cfg
r_shadowrendertotexture 1
r_shadowrendertotexture 1
ScrambledI sort of feel like the command that lets you see shadows through walls should be in the compquality cfg
r_shadowrendertotexture 1
It is in the config.
smesiit looks like i get overall better fps on dx81 although i could be wrong since idk much about comparing benchmarks so
You do get better FPS, probably because of your bad graphics card, but you should also play a while with dx9 and dx8 because average FPS is only part of the story. See which one feels smoother and has less stutter. If that is dx8 for you, then use it, but if not, I would sacrifice those few extra frames for more stability.
r_shadowrendertotexture 1[/quote]
It is [url=https://github.com/mastercoms/tf2cfg/blob/master/mastercomfig/cfg/presets/compquality.cfg#L9]in the config[/url].
[quote=smesi]it looks like i get overall better fps on dx81 although i could be wrong since idk much about comparing benchmarks so[/quote]
You do get better FPS, probably because of your bad graphics card, but you should also play a while with dx9 and dx8 because average FPS is only part of the story. See which one feels smoother and has less stutter. If that is dx8 for you, then use it, but if not, I would sacrifice those few extra frames for more stability.