Medico_di_BiscottiWhy was mat_antialias
changed to 1? Does it not improve FPS anymore, or is it to stop the screen from lagging out when changing? 'Cus the latter part is fixed by putting +mat_antialias 0
in launch options.
This is a slightly unrelated issue, but does anyone else's demos break when viewing them in mat_aaquality above 0
if they were recorded without AA? So I leave it out of the cinematic config. mat_antialias
works fine, though.
Mat_antialias causes crashes now
[quote=Medico_di_Biscotti]Why was [code]mat_antialias[/code] changed to 1? Does it not improve FPS anymore, or is it to stop the screen from lagging out when changing? 'Cus the latter part is fixed by putting [code]+mat_antialias 0[/code] in launch options.
This is a slightly unrelated issue, but does anyone else's demos break when viewing them in [code]mat_aaquality above 0[/code] if they were recorded without AA? So I leave it out of the cinematic config. [code]mat_antialias[/code] works fine, though.[/quote]
Mat_antialias causes crashes now
seiterseiter1Medico_di_BiscottiWhy was mat_antialias
changed to 1? Does it not improve FPS anymore, or is it to stop the screen from lagging out when changing? 'Cus the latter part is fixed by putting +mat_antialias 0
in launch options.
This is a slightly unrelated issue, but does anyone else's demos break when viewing them in mat_aaquality above 0
if they were recorded without AA? So I leave it out of the cinematic config. mat_antialias
works fine, though.
Mat_antialias causes crashes now
??? I've had mat_antialias set to 4 for months now and I've been fine.
[quote=seiterseiter1][quote=Medico_di_Biscotti]Why was [code]mat_antialias[/code] changed to 1? Does it not improve FPS anymore, or is it to stop the screen from lagging out when changing? 'Cus the latter part is fixed by putting [code]+mat_antialias 0[/code] in launch options.
This is a slightly unrelated issue, but does anyone else's demos break when viewing them in [code]mat_aaquality above 0[/code] if they were recorded without AA? So I leave it out of the cinematic config. [code]mat_antialias[/code] works fine, though.[/quote]
Mat_antialias causes crashes now[/quote]
??? I've had mat_antialias set to 4 for months now and I've been fine.
_Kermitseiterseiter1Medico_di_BiscottiWhy was mat_antialias
changed to 1? Does it not improve FPS anymore, or is it to stop the screen from lagging out when changing? 'Cus the latter part is fixed by putting +mat_antialias 0
in launch options.
This is a slightly unrelated issue, but does anyone else's demos break when viewing them in mat_aaquality above 0
if they were recorded without AA? So I leave it out of the cinematic config. mat_antialias
works fine, though.
Mat_antialias causes crashes now
??? I've had mat_antialias set to 4 for months now and I've been fine.
Yeah i meant it cant be set to 0.
[quote=_Kermit][quote=seiterseiter1][quote=Medico_di_Biscotti]Why was [code]mat_antialias[/code] changed to 1? Does it not improve FPS anymore, or is it to stop the screen from lagging out when changing? 'Cus the latter part is fixed by putting [code]+mat_antialias 0[/code] in launch options.
This is a slightly unrelated issue, but does anyone else's demos break when viewing them in [code]mat_aaquality above 0[/code] if they were recorded without AA? So I leave it out of the cinematic config. [code]mat_antialias[/code] works fine, though.[/quote]
Mat_antialias causes crashes now[/quote]
??? I've had mat_antialias set to 4 for months now and I've been fine.[/quote]
Yeah i meant it cant be set to 0.
mat_antialias 1 also turns the mumble overlay grossly bold stark white for a lot of people would be good to put a note next to it.
mat_antialias 1 also turns the mumble overlay grossly bold stark white for a lot of people would be good to put a note next to it.
Vanamat_antialias 1 also turns the mumble overlay grossly bold stark white for a lot of people would be good to put a note next to it.
that's odd
I use the overlay and I'm not getting that issue
actually the only time I ever had that issue was when I wasn't using -nod3d9ex in launch options
[quote=Vana]mat_antialias 1 also turns the mumble overlay grossly bold stark white for a lot of people would be good to put a note next to it.[/quote]
that's odd
I use the overlay and I'm not getting that issue
actually the only time I ever had that issue was when I wasn't using -nod3d9ex in launch options
help
(it was even worse w/ transparent viewmodels on, the entire screen would look spotty and fiery until I set r_drawviewmodel to 0) (r9 270x, i5 4460)
[url=https://streamable.com/z7l1]help[/url]
(it was even worse w/ transparent viewmodels on, the entire screen would look spotty and fiery until I set r_drawviewmodel to 0) (r9 270x, i5 4460)
ComangliaVanamat_antialias 1 also turns the mumble overlay grossly bold stark white for a lot of people would be good to put a note next to it.
that's odd
I use the overlay and I'm not getting that issue
actually the only time I ever had that issue was when I wasn't using -nod3d9ex in launch options
I don't use -nod3d9ex but most of the people I know who have gotten it where running dx8 including myself so I can only assume its a dx8 issue.
[quote=Comanglia][quote=Vana]mat_antialias 1 also turns the mumble overlay grossly bold stark white for a lot of people would be good to put a note next to it.[/quote]
that's odd
I use the overlay and I'm not getting that issue
actually the only time I ever had that issue was when I wasn't using -nod3d9ex in launch options[/quote]
I don't use -nod3d9ex but most of the people I know who have gotten it where running dx8 including myself so I can only assume its a dx8 issue.
Help,
Ive been crashing on launch with this new config update
Help,
Ive been crashing on launch with this new config update
VanaComangliaVanamat_antialias 1 also turns the mumble overlay grossly bold stark white for a lot of people would be good to put a note next to it.
that's odd
I use the overlay and I'm not getting that issue
actually the only time I ever had that issue was when I wasn't using -nod3d9ex in launch options
I don't use -nod3d9ex but most of the people I know who have gotten it where running dx8 including myself so I can only assume its a dx8 issue.
I am having the same problem. When I had mat_antialias on 1, my mumble overlay would just turn white. I also use dxlevel 81. The only way I can fix this is by having -nod3d9ex in launch options, which makes me wait like 6 seconds to alt+tab into TF2.
[quote=Vana][quote=Comanglia][quote=Vana]mat_antialias 1 also turns the mumble overlay grossly bold stark white for a lot of people would be good to put a note next to it.[/quote]
that's odd
I use the overlay and I'm not getting that issue
actually the only time I ever had that issue was when I wasn't using -nod3d9ex in launch options[/quote]
I don't use -nod3d9ex but most of the people I know who have gotten it where running dx8 including myself so I can only assume its a dx8 issue.[/quote]
I am having the same problem. When I had mat_antialias on 1, my mumble overlay would just turn white. I also use dxlevel 81. The only way I can fix this is by having -nod3d9ex in launch options, which makes me wait like 6 seconds to alt+tab into TF2.
Medico_di_BiscottiWhy was mat_antialias changed to 1? Does it not improve FPS anymore, or is it to stop the screen from lagging out when changing? 'Cus the latter part is fixed by putting +mat_antialias 0 in launch options.
0 is not a valid value for mat_antialias. The minimum value for it is 1, and if you set it to 0 it'll just be clamped by the game to 1. The same is true for mat_forceaniso.
[quote=Medico_di_Biscotti]Why was mat_antialias changed to 1? Does it not improve FPS anymore, or is it to stop the screen from lagging out when changing? 'Cus the latter part is fixed by putting +mat_antialias 0 in launch options.[/quote]
0 is not a valid value for mat_antialias. The minimum value for it is 1, and if you set it to 0 it'll just be clamped by the game to 1. The same is true for mat_forceaniso.
I have time to waste, going through the config commands and seeing what happens
I thought I found out what causes the black textures, but I couldn't get it to work again, so it's likely a result of more than one command at the same time?
I have time to waste, going through the config commands and seeing what happens
I thought I found out what causes the black textures, but I couldn't get it to work again, so it's likely a result of more than one command at the same time?
Medico_di_Biscotti0 is not a valid value for mat_antialias. The minimum value for it is 1, and if you set it to 0 it'll just be clamped by the game to 1. The same is true for mat_forceaniso.
what do you mean by that? you should be able to turn off antialias
[quote=Medico_di_Biscotti]0 is not a valid value for mat_antialias. The minimum value for it is 1, and if you set it to 0 it'll just be clamped by the game to 1. The same is true for mat_forceaniso.[/quote]
what do you mean by that? you should be able to turn off antialias
mat_antialias 1 is literally just x1 and thus has no antialiasing, is it not?
mat_antialias 1 is literally just x1 and thus has no antialiasing, is it not?
Just skimmed through config, couple questions/comments:
"mat_colcorrection_disableentities 0" - shouldn't be 1? You already disabled color-correction, but enabling entities?
"mat_picmip -1" - Last update "Eliminated occasional hitching caused by using mat_picmip 2 (or selecting low quality textures in Video Options -> Advanced)". No reason for -1 anymore, unless you like look.
"mat_trilinear 1" - Mouse movement feels smoother on 0 for me. Can confirm?
"net_queue_trace 0" - Does nothing but everyone has in config :/
AnAkkkThat cvar actually does nothing to optimize netcode, it prints debug information about the queued packet system (which is why it says “trace”) in the console, and that only happens when the value is set to “581304”, any other value will be considered as disabled.
TLDR: net_queue_trace 1 does nothing
cl_forcepreload / mat_disable_d3d9ex - Gone from last update. Probably this: "Fixed two most common forms of framerate stuttering / hitching when using popular FPS configs"
mat_shadowstate - Gone as well.
cl_detaildist 0 / cl_detailfade 0 - These 2 cvars does nothing in autoexec. They turn default values of 1200 / 400 when changing maps. Put them in class configs instead so they exec after map change.
also why so many cheat commands? Does nothing.
Just skimmed through config, couple questions/comments:
"mat_colcorrection_disableentities 0" - shouldn't be 1? You already disabled color-correction, but enabling entities?
"mat_picmip -1" - Last update [i]"Eliminated occasional hitching caused by using mat_picmip 2 (or selecting low quality textures in Video Options -> Advanced)"[/i]. No reason for -1 anymore, unless you like look.
"mat_trilinear 1" - Mouse movement feels smoother on 0 for me. Can confirm?
"net_queue_trace 0" - Does nothing but everyone has in config :/ [quote=AnAkkk]That cvar actually does nothing to optimize netcode, it prints debug information about the queued packet system (which is why it says “trace”) in the console, and that only happens when the value is set to “581304”, any other value will be considered as disabled.
TLDR: net_queue_trace 1 does nothing[/quote]
cl_forcepreload / mat_disable_d3d9ex - Gone from last update. Probably this: [i]"Fixed [u]two [/u]most common forms of framerate stuttering / hitching when using popular FPS configs"[/i]
mat_shadowstate - Gone as well.
cl_detaildist 0 / cl_detailfade 0 - These 2 cvars does nothing in autoexec. They turn default values of 1200 / 400 when changing maps. Put them in class configs instead so they exec after map change.
also why so many cheat commands? Does nothing.
also, since we're pointing out small stuff:
Unknown command: mat_shadowstate
I have no clue what this command was, all googling does is send you to other FPS configs that have it
also, since we're pointing out small stuff:
[code]Unknown command: mat_shadowstate[/code]
I have no clue what this command was, all googling does is send you to other FPS configs that have it
Would anybody happen to know why the edges of walls are really jagged and laggy when I move? This does not have to do with anti-aliasing or filtering. Also, this isn't a recent issue. It has been happening for a while.
Would anybody happen to know why the edges of walls are really jagged and laggy when I move? This does not have to do with anti-aliasing or filtering. Also, this isn't a recent issue. It has been happening for a while.
pazerMedico_di_BiscottiWhy was mat_antialias changed to 1? Does it not improve FPS anymore, or is it to stop the screen from lagging out when changing? 'Cus the latter part is fixed by putting +mat_antialias 0 in launch options.
0 is not a valid value for mat_antialias. The minimum value for it is 1, and if you set it to 0 it'll just be clamped by the game to 1. The same is true for mat_forceaniso.
But the game still recognizes it as a setting and switching between 0 and 1 also causes the game to freeze up while applying the change. I haven't tested if it actually changes, but the freeze is there and it'll say that the value was changed to 0.
I also said in the last post that my game doesn't draw the fire overlay, anyone else? I hadn't noticed people had responded when I edited more stuff in my post.
Also, when execing maxframes for high quality:
Unknown command "mat_shadowstate"
Unknown command "mat_disable_d3d9ex"
Unknown command "cl_forcepreload"
-
and when executing cinematic:
Unknown command "cl_forcepreload"
Unknown command "cl_loadondemand_default"
-
I know that loadondemand was removed from maxframes as well, just pointing out that it's still in cinematic.
What is d3d9ex? Is the command unknown because I haven't enabled it in a launch option or something. And how does dxlevel 90 compare FPS-wise to dxlevel 95 and 98?
Also, whatever makes the cloaking refraction look real funky is extremely distracting.
[quote=pazer][quote=Medico_di_Biscotti]Why was mat_antialias changed to 1? Does it not improve FPS anymore, or is it to stop the screen from lagging out when changing? 'Cus the latter part is fixed by putting +mat_antialias 0 in launch options.[/quote]
0 is not a valid value for mat_antialias. The minimum value for it is 1, and if you set it to 0 it'll just be clamped by the game to 1. The same is true for mat_forceaniso.[/quote]
But the game still recognizes it as a setting and switching between 0 and 1 also causes the game to freeze up while applying the change. I haven't tested if it actually changes, but the freeze is there and it'll say that the value was changed to 0.
I also said in the last post that my game doesn't draw the fire overlay, anyone else? I hadn't noticed people had responded when I edited more stuff in my post.
Also, when execing maxframes for high quality:
[code]
Unknown command "mat_shadowstate"
Unknown command "mat_disable_d3d9ex"
Unknown command "cl_forcepreload"
-[/code]
and when executing cinematic:
[code]
Unknown command "cl_forcepreload"
Unknown command "cl_loadondemand_default"
-[/code]
I know that loadondemand was removed from maxframes as well, just pointing out that it's still in cinematic.
What is d3d9ex? Is the command unknown because I haven't enabled it in a launch option or something. And how does dxlevel 90 compare FPS-wise to dxlevel 95 and 98?
Also, whatever makes the cloaking refraction look real funky is extremely distracting.
Why is it when i execute the config it says my detail to very high rather than low? Does it give more FPS or something?
Why is it when i execute the config it says my detail to very high rather than low? Does it give more FPS or something?
that would be mat_picmip -1, which was required because of weapon skins breaking low-quality textures and actually making performance worse on anything but highest, but that was fixed and just not updated in the config
switch it to mat_picmip 2
that would be mat_picmip -1, which was required because of weapon skins breaking low-quality textures and actually making performance worse on anything but highest, but that was fixed and just not updated in the config
switch it to mat_picmip 2
What causes the fire effects like this: https://i.gyazo.com/2e5ad47f044065d9246e9cd946fbc9e3.png
I only just got it from the updated version of the stability config.
What causes the fire effects like this: https://i.gyazo.com/2e5ad47f044065d9246e9cd946fbc9e3.png
I only just got it from the updated version of the stability config.
TennaWhat causes the fire effects like this: https://i.gyazo.com/2e5ad47f044065d9246e9cd946fbc9e3.png
I only just got it from the updated version of the stability config.
mat_specular 1 in dx8 causes these textures iirc, turn specular to 0
[quote=Tenna]What causes the fire effects like this: https://i.gyazo.com/2e5ad47f044065d9246e9cd946fbc9e3.png
I only just got it from the updated version of the stability config.[/quote]
mat_specular 1 in dx8 causes these textures iirc, turn specular to 0
For some reason the high quality config works with some dual core processors. I have an Intel Pentium G3240 @3.1GHz and it works better with the high quality pc config.
For some reason the high quality config works with some dual core processors. I have an Intel Pentium G3240 @3.1GHz and it works better with the high quality pc config.
cl_phys_timescale
mat_bloomamount_rate
mat_debug_bloom
mat_debug_process_halfscreen
mat_debugalttab
mat_force_bloom
mat_diffuse
mat_fastnobump
mat_hdr_tonemapscale
mat_leafvis
mat_loadtextures
mat_norendering
mat_show_texture_memory_usage
mat_softwareskin
mat_surfaceid
mat_surfacemat
mat_yuv
r_avglight
r_ambientfraction
r_avglightmap
r_lightcache_numambientsamples
r_lightinterp
r_lightstyle
r_radiosity
r_updaterefracttexture
r_unloadlightmaps
removed most/all sv_cheat commands
mat_disable_d3d9ex
cl_forcepreload
net_queue_trace 0
removed above needless commands
mat_antialias 1
is now commented out
mat_picmip -1 changed to 2
mat_colcorrection_disableentities 0 changed to 1
trashhelp
(it was even worse w/ transparent viewmodels on, the entire screen would look spotty and fiery until I set r_drawviewmodel to 0) (r9 270x, i5 4460)
I couldn't recreate this issue on 2 machines
Build 1
i5-4670k
R9 270x
Build 2
i7-4790k
R9 390
I tried all dxlevels and tried with and without transparent viewmodels still haven't had this issue.
-edit-
while attempting to find what's wrong with bleed/fire effect I notice that mat_viewportscale is no longer limited to .5 - 1
http://images.akamai.steamusercontent.com/ugc/404560951918458825/44A56D797958DD2BC62EF73D6FC8DC4C6D8A028F/
value is .01
still doesn't effect fps for 99% of users just thought it was interesting. mat_viewporscale is still limited to 1 at the max but the minimum seems to be 0 now.
[code]cl_phys_timescale
mat_bloomamount_rate
mat_debug_bloom
mat_debug_process_halfscreen
mat_debugalttab
mat_force_bloom
mat_diffuse
mat_fastnobump
mat_hdr_tonemapscale
mat_leafvis
mat_loadtextures
mat_norendering
mat_show_texture_memory_usage
mat_softwareskin
mat_surfaceid
mat_surfacemat
mat_yuv
r_avglight
r_ambientfraction
r_avglightmap
r_lightcache_numambientsamples
r_lightinterp
r_lightstyle
r_radiosity
r_updaterefracttexture
r_unloadlightmaps [/code]
removed most/all sv_cheat commands
[code]mat_disable_d3d9ex
cl_forcepreload
net_queue_trace 0[/code]
removed above needless commands
[code]mat_antialias 1[/code]
is now commented out
[code]mat_picmip -1 changed to 2
mat_colcorrection_disableentities 0 changed to 1[/code]
[quote=trash][url=https://streamable.com/z7l1]help[/url]
(it was even worse w/ transparent viewmodels on, the entire screen would look spotty and fiery until I set r_drawviewmodel to 0) (r9 270x, i5 4460)[/quote]
I couldn't recreate this issue on 2 machines
Build 1
i5-4670k
R9 270x
Build 2
i7-4790k
R9 390
I tried all dxlevels and tried with and without transparent viewmodels still haven't had this issue.
-edit-
while attempting to find what's wrong with bleed/fire effect I notice that mat_viewportscale is no longer limited to .5 - 1
[img]http://images.akamai.steamusercontent.com/ugc/404560951918458825/44A56D797958DD2BC62EF73D6FC8DC4C6D8A028F/[/img]
value is .01
still doesn't effect fps for 99% of users just thought it was interesting. mat_viewporscale is still limited to 1 at the max but the minimum seems to be 0 now.
Anyone know what command controls Texture settings? For some reason Comanglia set the texture to Really High in his config, and i dont like that. How can i change it to low?
Anyone know what command controls Texture settings? For some reason Comanglia set the texture to Really High in his config, and i dont like that. How can i change it to low?
mat_picmip, 2 is lowest -1 highest
mat_picmip, 2 is lowest -1 highest
comanglia, can i have your rationale on mat_trilinear 1 vs. 0? just curious
comanglia, can i have your rationale on mat_trilinear 1 vs. 0? just curious
springrollscomanglia, can i have your rationale on mat_trilinear 1 vs. 0? just curious
Personally i hated the circle effect 0 creates around the player, that any beyond the blurryness of the toaster config the 2nd most common reason people added me to fix stuff with the toaster config was about the circle effect 0 creates around the player.
That and the fps difference is negligible just like
mat_filterlightmaps 0/1
mat_filtertextures 0/1
don't affect performance for 99% of users most would prefer them set to 1
-edit-
for those of you having issues with the new configs try my old stability one here
[quote=springrolls]comanglia, can i have your rationale on mat_trilinear 1 vs. 0? just curious[/quote]
Personally i hated the circle effect 0 creates around the player, that any beyond the blurryness of the toaster config the 2nd most common reason people added me to fix stuff with the toaster config was about the circle effect 0 creates around the player.
That and the fps difference is negligible just like
mat_filterlightmaps 0/1
mat_filtertextures 0/1
don't affect performance for 99% of users most would prefer them set to 1
-edit-
for those of you having issues with the new configs try my old stability one here
I'm still getting unknown command errors in the console for some stuff that's still in your config, dunno if it means anything
Unknown command "mat_shadowstate"
Unknown command "mat_debugdepthmode"
Unknown command "mat_debugdepthval"
Unknown command "mat_debugdepthvalmax"
HDR Disabled
Unknown command "cpu_frequency_monitoring"
Unknown command "cl_forcepreload"
I'm still getting unknown command errors in the console for some stuff that's still in your config, dunno if it means anything[quote]
Unknown command "mat_shadowstate"
Unknown command "mat_debugdepthmode"
Unknown command "mat_debugdepthval"
Unknown command "mat_debugdepthvalmax"
HDR Disabled
Unknown command "cpu_frequency_monitoring"
Unknown command "cl_forcepreload"
[/quote]
VictorI'm still getting unknown command errors in the console for some stuff that's still in your config, dunno if it means anythingUnknown command "mat_shadowstate"
Unknown command "mat_debugdepthmode"
Unknown command "mat_debugdepthval"
Unknown command "mat_debugdepthvalmax"
HDR Disabled
Unknown command "cpu_frequency_monitoring"
Unknown command "cl_forcepreload"
Unknown command "mat_shadowstate"
Unknown command "mat_debugdepthmode"
Unknown command "mat_debugdepthval"
Unknown command "mat_debugdepthvalmax"
Unknown command "cpu_frequency_monitoring"
just removed all of those
Unknown command "cl_forcepreload"
I double checked my stability and quality pc one and both have this command removed not sure how you're still getting this to show up.
[quote=Victor]I'm still getting unknown command errors in the console for some stuff that's still in your config, dunno if it means anything[quote]
Unknown command "mat_shadowstate"
Unknown command "mat_debugdepthmode"
Unknown command "mat_debugdepthval"
Unknown command "mat_debugdepthvalmax"
HDR Disabled
Unknown command "cpu_frequency_monitoring"
Unknown command "cl_forcepreload"
[/quote][/quote]
Unknown command "mat_shadowstate"
Unknown command "mat_debugdepthmode"
Unknown command "mat_debugdepthval"
Unknown command "mat_debugdepthvalmax"
Unknown command "cpu_frequency_monitoring"
just removed all of those
Unknown command "cl_forcepreload"
I double checked my stability and quality pc one and both have this command removed not sure how you're still getting this to show up.
My bad, my autoexec still has parts from rhapsody's version, I guess I forgot to take it out when I was comparing it to yours.
My bad, my autoexec still has parts from rhapsody's version, I guess I forgot to take it out when I was comparing it to yours.