[b]Edit: All problems I had have been solved, whether it be from assistance of various forum-goers, or through tedious trial-and-error troubleshooting. Read down.
Also, if you are thinking of using this, please read the entire post, follow the given instructions and suggestions to avoid bad stuff, and keep in mind this won't make it run on your old clunker of a box, just make it less laggy on your current half-assed setup[/b]
Afternoon, folks. Got a quick question that hopefully one of you can answer for me.
Just recently I've started using an FPS-boosting configuration autoexec file, and it's worked like a dream, boosting my FPS from an average of 25 (10 in heavy combat) to 50 (25 in heavy combat). I didn't write it myself, of course, I'm not that familiar with the console, but I have gone back and flicked a few settings back on. (To give such things as eyes and teeth back to the models, and remove the opaque water it added)
There are a couple of things left I want to try, but I'm not sure what settings are effecting them.
The first is to return facial movement to the models. I've tried switching up to Medium models with the config on, but to no avail. This isn't a huge deal for me, so it's not imperative that this get fixed.
[b]Edit:Totally freaking can be used with DX 8.1. Fixed, and bugger all to those who said otherwise. *coughRedBeret*[/b]
The second is returning gibbing. It seems like switching on the "agibs" setting would allow for this, but exploded models simply disappear. Might be some kind of model limit. I don't know.
[b]Edit: Fixed[/b]
The third, and what I care about most, is to return the Ubercharge's visual effects. As is, the configuration makes it so where an Ubercharge gives the medic and his target a dull red/blue coloration (with yellow eyes, of course) rather than the traditional metallic shielding.
[b]Edit: Fixed.[/b]
Here is the config itself. ([b]Note:[/b] This is the updated, and hopefully final version, that allows for shiny ubercharges, sprays, decent water, gibs, movement, etc.)
-----------------------------------------
//Netcode Settings
rate 25000
cl_cmdrate 101
cl_interp_ratio 1
cl_updaterate 101
cl_interpolate 1
//Actual Video Settings
mat_antialias 0
mat_forceaniso 0
mat_hdr_enabled 0
mat_hdr_level 0
mat_picmip 1
mat_trilinear 0
mat_vsync 0
r_rootlod 1
mat_dxlevel 81
mat_monitorgamma "1.6"
//FPS Settings
fps_max 0
cl_detaildist "0"
cl_detailfade "0"
cl_drawmonitors "0"
cl_ejectbrass "0"
cl_forcepreload "1"
cl_lagcomp_errorcheck "1"
cl_lagcompensation "1"
cl_downloadfilter "nosounds"
cl_ejectbrass "0"
cl_forcepreload 1
cl_smoothtime "0.01"
cl_smooth 1
commentary 0
mat_aaquality "0"
mat_autoexposure_max "0"
mat_autoexposure_min "0"
mat_bloomscale "0"
mat_bufferprimitives "0"
mat_bumpmap "0"
mat_clipz "1"
mat_compressedtextures "1"
mat_diffuse "1"
mat_disable_bloom "1"
mat_disable_fancy_blending "1"
mat_disable_lightwarp "1"
mat_disable_ps_patch "1"
mat_envmapsize "0"
mat_excludetextures "1"
mat_envmaptgasize "0"
mat_fastspecular "1"
mat_filterlightmaps "1"
mat_filtertextures "1"
mat_forceaniso "4"
mat_forcehardwaresync "0"
mat_forcemanagedtextureintohardware "0"
mat_framebuffercopyoverlaysize "0"
mat_hdr_enabled "0"
mat_hdr_level "0"
mat_hdr_manual_tonemap_rate "0"
mat_mipmaptextures "1"
mat_lightmap_pfms "0"
mat_maxframelatency "0"
mat_max_worldmesh_vertices "0"
mat_parallaxmap "0"
mat_queue_mode "-1"
mat_reducefillrate "1"
mat_shadowstate "0"
mat_show_ab_hdr "0"
mat_showlightmappage "-1"
mat_specular "1"
mat_texture_limit "-1"
mat_use_compressed_hdr_textures "1"
mat_showenvmapmask "0"
mat_showlowresimage "0"
mat_showmaterials "0"
mat_showmaterialsverbose "0"
mat_supportflashlight "0"
mat_wateroverlaysize "0"
mat_motion_blur_enabled "0"
mat_motion_blur_percent_of_screen_max "0"
mat_softwarelighting "0"
mp_decals "100"
muzzleflash_light "0"
net_maxfragments "1280"
net_maxfragments "1280"
net_showevents "0"
npc_height_adjust "1"
r_3dnow "1"
r_3dsky "0"
r_PhysPropStaticLighting "0"
r_WaterDrawReflection "0"
r_WaterDrawRefraction "1"
r_ambientboost "0"
r_cheapwaterend "1"
r_cheapwaterstart "1"
r_decal_cullsize "0"
r_decals "100"
r_dopixelvisibility "0"
r_drawbatchdecals "0"
r_drawflecks "0"
r_drawmodeldecals "0"
r_drawmodelstatsoverlaymax "1.5"
r_drawmodelstatsoverlaymin "0.01"
r_drawspecificstaticprop "0"
r_dynamic "0"
r_eyeglintlodpixels "0"
r_eyemove "1"
r_eyes "1"
r_eyeshift_x "0"
r_eyeshift_y "0"
r_eyeshift_z "0"
r_eyesize "0"
r_fastzreject "0"
r_flashlightrendermodels "0"
r_flex "1"
r_unloadlightmaps "0"
r_flashlightrenderworld "0"
r_forcewaterleaf "0"
r_lightaverage "0"
r_maxmodeldecal "0"
r_maxnewsamples "0"
r_maxsampledist "0"
r_minnewsamples "0"
r_mmx "1"
r_norefresh "0"
r_occlusion "0"
r_renderoverlayfragment "1"
r_queued_decals "1"
r_ropetranslucent "0"
r_shadowmaxrendered "32"
r_shadowrendertotexture "2"
r_shadows "0"
r_spray_lifetime "10"
r_sse "1"
r_sse2 "1"
r_teeth "1"
r_staticpropinfo "0"
r_updaterefracttexture "0"
r_updaterefracttexture "0"
r_visualizeproplightcaching "1"
r_waterdrawreflection "0"
r_waterforceexpensive "0"
r_waterforcereflectentities"0"
rope_averagelight "0"
rope_collide "0"
rope_shake "0"
rope_smooth "0"
rope_smooth_enlarge "0"
rope_smooth_maxalpha "0"
rope_smooth_maxalphawidth "0"
rope_smooth_minalpha "0"
rope_smooth_minwidth "0"
rope_subdiv "0"
rope_wind_dist "0"
echo FPS Config Loaded!
--------------------------------------
[b]Important Edit for those wanting to use this for whatever reason:[/b]
To properly use these settings, put everything between the dashes into a text file named "autoconfig.cfg" and place it in your Team Fortress 2's cfg folder. Open the file's properties and check the 'read only' box. Before loading, add "-dxlevel 81" (without quotation marks) to TF2's Launch options.
I do not guarantee that this will help you, as I've no idea how your box is set up.
You may notice that the Intel on CTF maps is black, without texture. This is due to the cubemap applied to it doesn't play nice with DX 8. There is an easy fix for this, though. Visit [url]http://www.mediafire.com/?xjjguxmiybw[/url] and download the flagfix file. Extract the folder within to your team fortress 2 folder. (Base path is: C:\Program Files\Steam\steamapps\*YOUR USERNAME*\team fortress 2)
(credit for this fix goes to 'Doctor ?' on fightingamphibians.com) This, unfortunately, will not work for servers that don't allow users to import their own models... Or something. Idk. It doesn't work with Lotusclan's 2fort server, so w/e. You figure it out.
The only real unresolved issue at this point deals with the flashing warning lights on Well. The exterior lights (those mounted on either side of the train's entrance) do not flash. The sound still plays, and the lights inside on the overhang still flash, so you won't be totally in the dark, but it's still worth mentioning. I may try to Troubleshoot this later, but for now, I don't care.
Removal of this edit should be as simple as deleting the created autoconfig file, and removing the -dxlevel 81 tag from launch options. To restore your game to DX9, add -dxlevel 9 to your launch options, much in the same way you did with the other tag.
If you screwed up your game experimenting with some settings, if you enter:
-autoconfig
in the launch options, rid of the offending autoexec, and then start the game, it will reset all of your options to default.
I accept no responsibility for what may or may not happen in your game as a result of using this configuration.
Possible side effects of using Effpiex include:
Higher Framerate
Feats of unadulterated badassery
Superman syndrome
Gamer's Finger
Leaky Colon
Heart Attack
Death
Blah, blah, blah
How shit will this make my game look? I see you have set it to DX8, say if I set it back to DX9 how shit will the game look with the rest of the settings?
I'm guessing it's easier to fix the uber-effects in the options (as in, it'll be configured automatically if you up the level of graphics in your options.) but these commands look a bit suspicious i think:
r_drawmodelstatsoverlaymax "1.5"
r_drawmodelstatsoverlaymin "0.01"
Nubz:
Well, not too crappy, if you ask me, but I've seen a lot of people call it that. Personally, I can deal with minor graphical details missing if it means I can play more efficiently. (My combat ability's improvement is noticeable. I kinda like to imagine my previous experiences as training with massive weights on, and now that I'm free of them, I'm practically unstoppable.)
And yeah, I've got it set to DX8. I wouldn't doubt it if that's what's causing the odd-Ubers. To be honest with you though, I'm not sure how it would look with DX9. Try it and see for yourself.
Cheezy:
I'm not sure that would change much. I was already running with the lowest possible option in every field, and I still got shiny ubers. Funny though, my friend got the dull effect on his old box just like this.
What do the two settings you mentioned do, precisely? Or generally. It doesn't matter, just some kind of idea what it changes.
Honestly it sounds like this takes the game and renders it with even lower settings than what the options say...
Try using
mat_picmip 10, instead of the config, it should give you a massive performance boost, if you don't mind the horrid textures.
10 is the lowest texture setting, but anywhere from 10-2 is considered low.
Shadow:
I've actually tried that, believe it or not. Noticed the "Make TF2 look Ubersweet" thread, and applied it in the opposite direction, hoping for improvement.
Didn't really do much, to be honest. Not enough to be worth the trade off, anyway. This works very well, and doesn't make it look near as bad as you'd think. Water could use some work, but it's still palpable.
Screens? :D
What the fuck, because of a quirk with Wine, the lowest my FPS can get is 66.
LOWEST. Any lower and the game starts slowing down - literally. It's like I've turned down my timescale.
[QUOTE=Nubz]How shit will this make my game look? I see you have set it to DX8, say if I set it back to DX9 how shit will the game look with the rest of the settings?[/QUOTE]
Apart from setting it to DirectX 8 mode, it also disables texture filtering (the floor and walls will look like crap the further away from you they are) and lowers the texture quality (to low I think)
So it'll look like crap, but run ok if your card is crap.
Edit: It'll also disable environment maps and bump maps, and it might disable specular highlights, not sure on that though.
What the fuck is that config? It turned my water black(Instead of white :() and it gives me 1fps when someone gets a headshot as a sniper... My config doesn't give me any problems...
[QUOTE=HubmaN V2]What the fuck, because of a quirk with Wine, the lowest my FPS can get is 66.
LOWEST. Any lower and the game starts slowing down - literally. It's like I've turned down my timescale.[/QUOTE]
If you really get "slowmotion" like you describe, playing sniper must be fun :D
The commands i posted have something to do with rendering model-overlays (Which the shiny uber-effects most probably are.)
The problem you're experiencing with the lack of shiny ubers could possibly be caused by having bad drivers, or an old card?
As in the card disables certain effects automatically when you decrease the level of graphics ingame.
Everyone fails. mat_dxlevel 81 causes this, because anything under directX 9 cannot support the metallic uber, therefore causing your flat shaded mess. This is also why you have no normal maps or phong. Plus when TF2 was in its beta no ground textures blended for you.
Being in dx8 mode also prevents you from having facial animations on characters.
So solution, get a better video card, and if your card does support dx9, then set mat_dxlevel 9. If your card doesn't support this, you'll probably crash your game or see no difference at all. But since you're using a config that has set you to mat_dxlevel 81, just set it to mat_dxlevel 9 (or mat_dxlevel 90, can't remember which).
[QUOTE=RedBeret]Everyone fails. mat_dxlevel 81 causes this, because anything under directX 9 cannot support the metallic uber, therefore causing your flat shaded mess. This is also why you have no normal maps or phong. Plus when TF2 was in its beta no ground textures blended for you.
Being in dx8 mode also prevents you from having facial animations on characters.
So solution, get a better video card, and if your card does support dx9, then set mat_dxlevel 9. If your card doesn't support this, you'll probably crash your game or see no difference at all. But since you're using a config that has set you to mat_dxlevel 81, just set it to mat_dxlevel 9 (or mat_dxlevel 90, can't remember which).[/QUOTE]
Yeah there is no way you can get those features in TF2 (and many other games) without at least direct X 9.
Small update, I suppose. I decided to do some troubleshooting this morning, to see if it wasn't this config and I'd just borked something up somewhere else. After ditching it, everything was back to normal. Reflections, gibs, and all. Still had the old FPS problem though. I decided to test something. (and I'm glad I did)
I went back, and edited things so that only the DX setting changes were changed. Got into the game, and had my gibs and such back, with a fairly significant boost to FPS. I believe I'm going to go ahead and ditch the rest of the crap, and see how well it gets on.
[QUOTE=RedBeret]Everyone fails. mat_dxlevel 81 causes this, because anything under directX 9 cannot support the metallic uber, therefore causing your flat shaded mess. This is also why you have no normal maps or phong. Plus when TF2 was in its beta no ground textures blended for you.
Being in dx8 mode also prevents you from having facial animations on characters.
So solution, get a better video card, and if your card does support dx9, then set mat_dxlevel 9. If your card doesn't support this, you'll probably crash your game or see no difference at all. But since you're using a config that has set you to mat_dxlevel 81, just set it to mat_dxlevel 9 (or mat_dxlevel 90, can't remember which).[/QUOTE]
Fun little thing here. After I'd tried 'just' setting things back to DX 8.1, the Shine of the uber was still there, as were the other bits you speak of. I'm not sure what what the deal is, or if you've just got erroneous information, but the game's running smoothly with all my features intact, and I'm happy with it.
And for the record, my card does support DX9, and I'd always run it in said mode beforehand, and previous to my trying this config, the Ubers were as shiny as ever. I'm not sure what possessed you to skip half my post, but I'd appreciate you paying better attention in the future. Don't get me wrong, I appreciate your input, but you are capable of doing so with better manners.
EDIT:
Right then. It was a total fluke. I'd screwed up a bit and it hadn't changed the DX level. Ran well for a few minutes though. Oh well. If it is the DX setting that gives those, then I suppose screw it. I can live with boring ubers for kill-power. Don't have to root through dead bits to find a gun for ammo either, so all's not crap.
[QUOTE=Megamarth]Small update, I suppose. I decided to do some troubleshooting this morning, to see if it wasn't this config and I'd just borked something up somewhere else. After ditching it, everything was back to normal. Reflections, gibs, and all. Still had the old FPS problem though. I decided to test something. (and I'm glad I did)
I went back, and edited things so that only the DX setting changes were changed. Got into the game, and had my gibs and such back, with a fairly significant boost to FPS. I believe I'm going to go ahead and ditch the rest of the crap, and see how well it gets on.
Fun little thing here. After I'd tried 'just' setting things back to DX 8.1, the Shine of the uber was still there, as were the other bits you speak of. I'm not sure what what the deal is, or if you've just got erroneous information, but the game's running smoothly with all my features intact, and I'm happy with it.
And for the record, my card does support DX9, and I'd always run it in said mode beforehand, and previous to my trying this config, the Ubers were as shiny as ever. I'm not sure what possessed you to skip half my post, but I'd appreciate you paying better attention in the future. Don't get me wrong, I appreciate your input, but you are capable of doing so with better manners.
EDIT:
Right then. It was a total fluke. I'd screwed up a bit and it hadn't changed the DX level. Ran well for a few minutes though. Oh well. If it is the DX setting that gives those, then I suppose screw it. I can live with boring ubers for kill-power. Don't have to root through dead bits to find a gun for ammo either, so all's not crap.[/QUOTE]
Before I got my 8800GTS I had a 5 series card, so that's how I knew it was dx8 causing all that. :D
And I said everyone fails as sort of a joke, since you shouldn't really give someone help with something you're not sure of.
Bump and a pretty big update!
It turns out that the directx settings didn't have much to do with my problems. Ubers are back, as well as many other bits. Hoping to get gibs resolved as well soon, which will round out my experience, and make TF2 look great, as well as being deliciously playable!
[img]http://img232.imageshack.us/img232/6761/graphicscl6.jpg[/img]
Don't fucking do it.
[QUOTE=ZestyLemons][img]http://img232.imageshack.us/img232/6761/graphicscl6.jpg[/img]
Don't fucking do it.[/QUOTE]
Good god, Lemon, what the hell is that? Should look more like this.
[img]http://img160.imageshack.us/img160/911/cpgravelpit0000ua4.jpg[/img]
Or this
[img]http://img68.imageshack.us/img68/2803/cpgravelpit0001us6.jpg[/img]
[b]Edit:[/b] Figured out what's up with Lemon's pic. He's enabled "mat_showlowresimage" This causes TF2 to look... Well... Like that, I suppose would be the best comparison. What a kidder.
Looks like mat_picmip 64bit, jesus.
phys props limiting is stopping your gibs. Turn it up to about 10 and you can probably get one set at once.
[QUOTE=Sh33p]phys props limiting is stopping your gibs. Turn it up to about 10 and you can probably get one set at once.[/QUOTE]
Neither your nor alkizmo's suggestions have restored gibs. (or model facial movement for that matter)
I'm inclined to think that RedBeret is at least partially correct, and that theses are due to the DX settings.
Change these settings in your config
For gibs
props_break_max_pieces "-1"
props_break_max_pieces_perframe "-1"
cl_phys_props_enable "1"
cl_phys_props_max "-1"
For shiny metalic ubers
mat_bumpmap "1"
The facial movement is disabled because you run the game in directx8
Also just so you know, having model detail at low or medium or high won't change how much fps you get due to a bug in the game. You can run at all high, and get 70 fps, while running at all low and get 72 fps. Why that config gives you more fps is because it changes to dx8.
Put these in launch properties: -autoconfig -dxlevel 81
It will reset the game to its normal state and run the game in dx81, remove them the next time you start the game or your settings will reset.
[QUOTE=NULLNAME]Change these settings in your config
For gibs
props_break_max_pieces "-1"
props_break_max_pieces_perframe "-1"
cl_phys_props_enable "1"
cl_phys_props_max "-1"
For shiny metalic ubers
mat_bumpmap "1"
The facial movement is disabled because you run the game in directx8
Also just so you know, having model detail at low or medium or high won't change how much fps you get due to a bug in the game. You can run at all high, and get 70 fps, while running at all low and get 72 fps. Why that config gives you more fps is because it changes to dx8.
Put these in launch properties: -autoconfig -dxlevel 81
It will reset the game to its normal state and run the game in dx81, remove them the next time you start the game or your settings will reset.[/QUOTE]
Right-o. Will try that, though changing those settings (for gibs) in the past hasn't fixed it. And for the record, I already fixed ubers (By setting "mat_specular" to 1. Though that did make my Intel black, that was fixed with a quick model replacement to make the cubemaps play nice in 8.1)
Also, that's a bit odd about the models. Are you absolutely sure about that?
[b]Edit:[/b] Tried your props settings, but gibs haven't returned. There's probably some fiddly little line in the config that's barely related what's causing it. Wish I knew more about this stuff than I do.
[QUOTE=Megamarth]Right-o. Will try that, though changing those settings (for gibs) in the past hasn't fixed it. And for the record, I already fixed ubers (By setting "mat_specular" to 1. Though that did make my Intel black, that was fixed with a quick model replacement to make the cubemaps play nice in 8.1)
Also, that's a bit odd about the models. Are you absolutely sure about that?
[b]Edit:[/b] Tried your props settings, but gibs haven't returned. There's probably some fiddly little line in the config that's barely related what's causing it. Wish I knew more about this stuff than I do.[/QUOTE]
I don't know those are the right commands. Try changing the number "-1" to 9001 or something.
Also you don't need the config. It won't help you. Just delete it, do those launch commands, start the game, end it, remove them. Now you have gibs and everything and running it in dx81 which gives you fps.
I lol'd
Does anyone have a list of the TF2 graphic commands, and their functions?
[QUOTE=Megamarth]Good god, Lemon, what the hell is that? Should look more like this.
[img]http://img160.imageshack.us/img160/911/cpgravelpit0000ua4.jpg[/img]
Or this
[img]http://img68.imageshack.us/img68/2803/cpgravelpit0001us6.jpg[/img]
[b]Edit:[/b] Figured out what's up with Lemon's pic. He's enabled "mat_showlowresimage" This causes TF2 to look... Well... Like that, I suppose would be the best comparison. What a kidder.[/QUOTE]
those pics look worse than default dx9
[QUOTE=John Edwards]those pics look worse than default dx9[/QUOTE]
That's because it's dx8.1
Did you even read the topic, man?
[QUOTE=Enth]Does anyone have a list of the TF2 graphic commands, and their functions?[/QUOTE]
No, and were there one extensive enough to be useful, this topic probably wouldn't exist.
Side note: Got Gibs back. woo.
I got 150 FPS with no action (woo-hoo!) but it crashes when I shoot as a scout.
Sorry, you need to Log In to post a reply to this thread.
