Hi. I must play on low details but my weapons looks horrible especially bread brite. I only want to change weapons details in first person if it is possible. I really need help my weapons looks soo bad ;_;.
Oh and taunts details? for example Amputator taunt. i do not see violin
Hi. I must play on low details but my weapons looks horrible especially bread brite. I only want to change weapons details in first person if it is possible. I really need help my weapons looks soo bad ;_;.
Oh and taunts details? for example Amputator taunt. i do not see violin
maybe just hide your viewmodels?
maybe just hide your viewmodels?
mat_picmip, r_lod, and r_rootlod will affect how your viewmodels look
mat_picmip, r_lod, and r_rootlod will affect how your viewmodels look
r_lod 0
r_rootlod 0
You can actually set r_lod to -1 but because r_rootlod only goes down to 0 it wont affect your viewmodels detail regardless.
For higher quality textures use mat_picmip (it goes from 2 to -1 with -1 being the highest quality).
Although I recommend keeping mat_picmip at 2 because it's probably one of the largest framerate killers after Anti-Aliasing.
r_lod 0
r_rootlod 0
You can actually set r_lod to -1 but because r_rootlod only goes down to 0 it wont affect your viewmodels detail regardless.
For higher quality textures use mat_picmip (it goes from 2 to -1 with -1 being the highest quality).
Although I recommend keeping mat_picmip at 2 because it's probably one of the largest framerate killers after Anti-Aliasing.
r_lod 0
r_rootlod 0
mat_picmip 2
They doesnt work.
I will show you guys how for example gloves in first person looks with these commands active
http://wrzucaj.net/images/2014/12/28/asfafafO8Znv.png
r_lod 0
r_rootlod 0
mat_picmip 2
They doesnt work.
I will show you guys how for example gloves in first person looks with these commands active
[img]http://wrzucaj.net/images/2014/12/28/asfafafO8Znv.png[/img]
um yeah did you even read the thread
um yeah did you even read the thread
TwistedAlthough I recommend keeping mat_picmip at 2 because it's probably one of the largest framerate killers after Anti-Aliasing.
Depends on your video card and motherboard. Everyone should do their own testing. mat_picmip literally does not affect framerate whatsoever for me, even on maps that use way too many materials at once.
[quote=Twisted]
Although I recommend keeping mat_picmip at 2 because it's probably one of the largest framerate killers after Anti-Aliasing.[/quote]
Depends on your video card and motherboard. Everyone should do their own testing. mat_picmip literally does not affect framerate whatsoever for me, even on maps that use way too many materials at once.
Alright i posted this so i can save it, interested in this as well
Alright i posted this so i can save it, interested in this as well
wasylsteinbump
This has already been answered, why the hell would you bump
[quote=wasylstein]bump[/quote]
This has already been answered, why the hell would you bump
Deetrwasylsteinbump
This has already been answered, why the hell would you bump
Because this has not been already answered.
[quote=Deetr][quote=wasylstein]bump[/quote]
This has already been answered, why the hell would you bump[/quote]
Because this has not been already answered.
For higher quality textures use mat_picmip (it goes from 2 to -1 with -1 being the highest quality).
[quote]For higher quality textures use mat_picmip (it goes from 2 to -1 with -1 being the highest quality).
[/quote]
wasylsteinDepends on your video card and motherboard. Everyone should do their own testing. mat_picmip literally does not affect framerate whatsoever for me, even on maps that use way too many materials at once.
You are right. Although I personally I feel like I am getting very minor input lag with low picmip on 144hz even though my framerate is more or less the same at a solid 200+.
However I guess this could be because the game only uses the 3 cores it runs on to communicate between my gpu and cpu too which I suppose affects builds where your cpu has many slower cores rather than fewer fast ones. (fucking AMD pls)
Also OP change the mat_picmip to a lower value (1, 0 or -1), as I mentioned in my first post, until you find the highest value you feel comfortable playing with.
[quote=wasylstein]Depends on your video card and motherboard. Everyone should do their own testing. mat_picmip literally does not affect framerate whatsoever for me, even on maps that use way too many materials at once.[/quote]
You are right. Although I personally I feel like I am getting very minor input lag with low picmip on 144hz even though my framerate is more or less the same at a solid 200+.
However I guess this could be because the game only uses the 3 cores it runs on to communicate between my gpu and cpu too which I suppose affects builds where your cpu has many slower cores rather than fewer fast ones. (fucking AMD pls)
Also OP change the mat_picmip to a lower value (1, 0 or -1), as I mentioned in my first post, until you find the highest value you feel comfortable playing with.
cage-For higher quality textures use mat_picmip (it goes from 2 to -1 with -1 being the highest quality).
READ THREAD TITLE
bump
[quote=cage-][quote]For higher quality textures use mat_picmip (it goes from 2 to -1 with -1 being the highest quality).
[/quote][/quote]
READ THREAD TITLE
bump
use mat_picmip -1
if you have it set to 2 of course its going to look awful. Thats lowest quality.
please re-read this thread and be accepting of the help & solutions that have been offered.
use mat_picmip -1
if you have it set to 2 of course its going to look awful. Thats lowest quality.
please re-read this thread and be accepting of the help & solutions that have been offered.
wasylsteinclose this thread
Let me explain to you clearly what's the problem
You can't have high detail on viewmodels and have low detail on everything else at the same time. They are both controlled by the same command, which is mat_picmip. You either have to deal with it or hide the viewmodels if they look that awful to you.
[quote=wasylstein]close this thread[/quote]
Let me explain to you clearly what's the problem
You can't have high detail on viewmodels and have low detail on everything else at the same time. They are both controlled by the same command, which is mat_picmip. You either have to deal with it or hide the viewmodels if they look that awful to you.