Eh..TF2 slower than Crysis?

WhiteGuardian

Limp Gawd
Joined
Feb 15, 2008
Messages
421
I got a Q9300, 4 gig ram w/ 64 bit vista, and Visiontek 4870. But I notice in a lot of open spots, TF2 runs in the mid 30s, sometimes even slower than Crysis at Very High. I run CoD4 at 100+ average FPS and same with Bioshock, but TF2 is just acting weird. Is it the source engine that causing this?
 
My 280GTX sometimes bogs down to about 40-50 in open areas with lots of players around. Don't be deceived by the cartoonish demeanor, it's a pretty demanding game - beautiful, too.

PS: This is at 1920x1200 maxed.
 
eh....I run TF2 at 1900x1200 with high AA & AF(cant remember exactly what settings) with custom ultra high details, and do not notice any slow down whatsoever. That being said, I do not normally run FRAPS in the background so frames may be dipping but it is not something I have noticed.
 
TF2 is a very demanding game in certain spots. I have a gtx 260 at evga supersuper clocked speeds 626 core whatever the rest is. With an E6400 running at 2.5 ghz and in tf2 at 1600x1200 with full aa/af in a large area with 10 pyros running around like there seem to be it can drop to a minimum of like 28 - 30 but in all other spots it is normally around 70 fps.

So yeah no worries man it does slow down in certain large areas of the game with the whole 32 people there shooting. As for the poster above running at 1920x1200 and never noticing a slowdown you must be running an expensive setup.
 
TF2's performance is frankly shitty. There's a 150 page post about performance issues on the official TF2 forums.
 
TF2 is a very demanding game in certain spots. I have a gtx 260 at evga supersuper clocked speeds 626 core whatever the rest is. With an E6400 running at 2.5 ghz and in tf2 at 1600x1200 with full aa/af in a large area with 10 pyros running around like there seem to be it can drop to a minimum of like 28 - 30 but in all other spots it is normally around 70 fps.

So yeah no worries man it does slow down in certain large areas of the game with the whole 32 people there shooting. As for the poster above running at 1920x1200 and never noticing a slowdown you must be running an expensive setup.


Q9450 stock, GTX280 pre-overclocked and 2 gig DDR3 1333 stock. Must admit though that I have seldom been in a firefight where all 32 people are in close proximity, will have to keep an eye out for it.
 
TF2 benefits greatly from having a fast processor. Overclocking should boost your frame rates a good bit.
 
TF2 benefits greatly from having a fast processor. Overclocking should boost your frame rates a good bit.
Ding! Source engine games are very CPU dependent. If you want faster framerates in almost any source game, get a faster processor or overclock yours more.
 
Ding! Source engine games are very CPU dependent. If you want faster framerates in almost any source game, get a faster processor or overclock yours more.

Valve games have always been that way for whatever reason. I remember original HL and CS being very CPU dependent.
 
With the system in my sig I get 100fps pretty much constant with the occasional dip into the 80's with my settings completely maxed 16xAA 16xAF 1920x1080 and quality settings maxed in the control panel. I lock my fps at 100.
 
I get slow downs as well in TF2. Fastlane, the wide open middle area, at the very beginning of the game when everyone is there, I drop to the 30s fps. It's fairly disconcerting, since that kind of drop is very noticeable from the typical 70-100fps I get.
 
What are your AA settings?

I have a 4850, and get similar performance drops only under some very specific AA settings. I can't remember exactly what they were, and am not at my computer, but I think it was when using CFAA. The game runs beautifully on box 8xAA at 1680x1050 with full AF. If I remember correctly, I think 12xCFAA is where it started showing some slowdown and 24xCFAA is where it starts dropping into the 30s.

I think TF2 is a shader heavy game and, since CFAA uses shaders, even these GPU powerhouses simply aren't fast enough.

Edit: I'm speaking aside from CPU limitations, by the way.
 
TF2 and the source engine is more CPU bound than it is GPU bound.

Here's some commands to hopefully help you out:
r_threaded_renderables "1"
mat_queue_mode "2"
r_threaded_particles "1"
r_threaded_client_shadow_manager "1"
cl_threaded_bone_setup "1"
cl_threaded_client_leaf_system "1"
 
Same with me. E8400@stock, Gtx260@700/3000/1500, 1920x1200 everything maxed aa/af. Lowest I've seen was 24 fps.

You gotta admit this is one BEAUTIFUL game though.
 
My TF2 screams in XP, but was slower than snot in Vista 64, no idea why.
60-100fps avg, occasional dips into the 40's when 50tybillion stickies go off and 20 people are on fire, etc.
 
My TF2 screams in XP, but was slower than snot in Vista 64, no idea why.
60-100fps avg, occasional dips into the 40's when 50tybillion stickies go off and 20 people are on fire, etc.

You may be running the 64bit executable in vista, which is known to have terrible performance. Add -32bit to your launch options for TF2 in steam, get all your perfomace back :).
 
Hrm weird, my TF2 runs better in Vista than in XP...

Edit: Waffletron beat me to it, that must be it.
 
You may be running the 64bit executable in vista, which is known to have terrible performance. Add -32bit to your launch options for TF2 in steam, get all your perfomace back :).

could be. between that and the terrible latency, I wrote it off. I didn't feel like trying to work all the bugs in all the different games/software I used, and went back to XP32
 
avg frps with sig rig is 80-120 lowest would be 45 at stock. when i oc'd my cpu to 3.6 i gained about 7-10 frps. WIll be interesting to see what happens when my new board and gpu get here this week. X48-Ds4 and 2 4870. SHould help me oc to at least 4.0, can't wait
 
Keep in mind a lot of customized maps are designed poorly and have performance issues.
 
eh....I run TF2 at 1900x1200 with high AA & AF(cant remember exactly what settings) with custom ultra high details, and do not notice any slow down whatsoever. That being said, I do not normally run FRAPS in the background so frames may be dipping but it is not something I have noticed.

Type 'cl_showfps 1' in the console and you can view your fps.
 
Well I can run TF2 smoothly on my PC everything maxed at 1680x1050, however I can't run Crysis even on "high" with smooth performance, let alone very high. Running 8800GTS 320mb, E6600, 2gb 667mhz ram, stock speeds on XP, so you shouldn't be having any trouble with TF2 if my PC can run it sweetly.
 
Eh, I saw some good gains going from 3Ghz (stock) to 4Ghz. I'm sure you guys with quads should see a similar boost, especially if your starting so low (sub 3Ghz). As others have said, Source LOVES Mhz.
 
TF2 and the source engine is more CPU bound than it is GPU bound.

Here's some commands to hopefully help you out:
r_threaded_renderables "1"
mat_queue_mode "2"
r_threaded_particles "1"
r_threaded_client_shadow_manager "1"
cl_threaded_bone_setup "1"
cl_threaded_client_leaf_system "1"

These commands are good for two things: upping your framerate by about 50% on a multicore system and making your game crash every 15 minutes at the same time. Seriously, Valve needs to put something up about what these commands actually do, why they aren't stable on 75% of systems, and if they ever intend to make them stable.
 
Well I can run TF2 smoothly on my PC everything maxed at 1680x1050, however I can't run Crysis even on "high" with smooth performance, let alone very high. Running 8800GTS 320mb, E6600, 2gb 667mhz ram, stock speeds on XP, so you shouldn't be having any trouble with TF2 if my PC can run it sweetly.


ur vid card is holding u back in crysis to start
 
this game like all source games are cpu dependent. when i went from a amd 2.5ghz to a
c2q 3.0ghz and there was a big improvement. to the OP i would oc your cpu, you'll see the fps even out.
 
These commands are good for two things: upping your framerate by about 50% on a multicore system and making your game crash every 15 minutes at the same time. Seriously, Valve needs to put something up about what these commands actually do, why they aren't stable on 75% of systems, and if they ever intend to make them stable.

I've used those commands on my new rig I just built and I'm 100% stable with them turned on. Never had any issue. I have heard that some people have problems with them but I've never had a problem.
 
I've used those commands on my new rig I just built and I'm 100% stable with them turned on. Never had any issue. I have heard that some people have problems with them but I've never had a problem.

I may have to try them to see if I crash, although its running plenty fast as it is.
 
Those commands do cause crashes for me if I'm running the 64bit executable. With the -32bit tag I'm fine.
 
Hmm... interesting. I think I may try Vista again. The reason I went from 64-bit Vista back to XP was because the performance in TF2 was terrible--around a 25% overall decrease.
 
Im fairly sure it's because the Q9300 is quite slow per core only 2.0Ghz, but has 4 cores.

Crysis can make use of all 4 cores where as HL2 will not, the HL2 engine is still very CPU heavy and since it cannot use all 4 cores it has much less power to work with. If both games are CPU bound on your machine but one makes much better use of 4 cores then you'll get better frame rate in that game.
 
Im fairly sure it's because the Q9300 is quite slow per core only 2.0Ghz, but has 4 cores.

Crysis can make use of all 4 cores where as HL2 will not, the HL2 engine is still very CPU heavy and since it cannot use all 4 cores it has much less power to work with. If both games are CPU bound on your machine but one makes much better use of 4 cores then you'll get better frame rate in that game.
Crysis? um you picked the wrong game to claim 4 core support for. 4 cores really doesnt do crap for Crysis and a slightly faster dual core will beat 4 cores. here you can see that a 2.93 dual core beats a 2.66 quad so even clock for clock a quad core is basically useless in Crysis.

http://www.gamespot.com/features/6182806/p-6.html

also the Q9300 is 2.5ghz not 2.0 and it is hardly a slouch.
 
Main problem in TF2 is that it's multi-threaded support is nearly non existant. Most of the work is being done on a single core.
 
theres a bug in the current crop of amd drivers
ppl with nvidia cards run the game fine atm.
update to the latest drivers, and if that doesnt work, be patient and wait for newer drivers.
i dont believe the op is referring to situations where tons of crazy things are happening on a custom map, i think he's genuinely running into an amd driver issue.
 
Back
Top