Forum
TF2 Graphic Problem...
Created 16th March 2011 @ 23:47
Add A Reply Pages: 1
hehe
Basically when I use Chris’s max gfxs fps config I get this: http://i.imgur.com/Yx24L.jpg
Not high graphics, I have no eyes or anything!
What I have is 4 different TF2 launches, dx8 low, dx9 low, high (no AA,AF,or ragdolls etc.) then highplus which is completely full.
I’d normally run TF2 in various versions depending on how srs I want to be, however for some reason the high graphics one is just dx9 but with better textures or w/e :/
Is this because the commands are clashing? How can I stop them from effecting each other or how else can I fix this issue? Not sure what the command is to stop the matt white texture on the weapons, which is my main gripe.
But eyes, ragdolls and other things are not visible even with the highest gfx settings.
Any help is much appreciated.
dx9framerates?
high quality?
max quality?
anyway, the commands are these, taken from chris cfg.
// ------
// SPRAYS
// ------
// Enable sprays -- not enabled by default
cl_playerspraydisable "0"
r_decals "200"
r_spray_lifetime "2"
// -------
// SHADOWS
// -------
// Enable shadows -- not enabled by default
mat_shadowstate "1"
r_shadowmaxrendered "11"
r_shadowrendertotexture "0" // Set this to 1 for high definition shadows
r_shadows "1"
// ---------------
// FACIAL FEATURES
// ---------------
// Enable facial features -- not enabled by default
blink_duration "0.2"
r_eyes "1"
r_flex "1"
r_lod "1"
r_rootlod "1"
r_teeth "1"
flex_rules "1"
flex_smooth "1"
// --------
// RAGDOLLS
// --------
// Enable ragdolls -- not enabled by default
cl_ragdoll_fade_time "15"
cl_ragdoll_forcefade "0"
cl_ragdoll_physics_enable "1"
g_ragdoll_fadespeed "600"
g_ragdoll_lvfadespeed "100"
ragdoll_sleepaftertime "5.0f"
// ----
// GIBS
// ----
// Enable gibs -- not enabled by default
cl_phys_props_enable "1"
cl_phys_props_max "128"
props_break_max_pieces "-1"
r_propsmaxdist "1000"
violence_ablood "1"
violence_agibs "1"
violence_hblood "1"
violence_hgibs "1"
if you want these enable, try to enforce your client to restart your configuration.
You can do this by deleting the autoexec.cfg, and adding in the game prop.
-autoconfig
Then, you can add these in your autoexec again.
This might work.
Last edited by sovietdrunk,
ill do quick edit from previous post – you need to delete config.cfg before every start, not autoexec… autoexec changes with ur silly multi launch script i imagine
Add A Reply Pages: 1
content rss