Team Fortress 2 + Rainmeter/Rainlender/ObjectDock = LAG

For the past few days I felt that my fps I was getting from TF2 is less smooth than I would hope it to be. I finally realised the problem was that TF2 was only utilising about 50% of my first core, whereas in the past it used to utilise >90% of the first core.

I decided to kill off some of my background processes, and somehow TF2 started to use up >90% of my first core again. Then I turned back my processes slowly and I found the culprit. Whenever I turned on Rainmeter, Rainlender2 or ObjectDock, TF2's CPU usage would automaticly half to 50%. There is nothing else using up the remaining 50%, but TF2 just refuses to use more than 50% of the first core. It's as if it's being reserved for the other applications and TF2 can't touch it.

Anyone else experienced anything similar or knows how to overcome this?

 

I play tf2 and have object dock and no issues that I have seen, sorry I wish I could help...

 

That's why whenever you are going to play an intensive game you shut down all unnecessary processes no matter how much RAM or how fast a CPU you have.

 

Yeah can't help either. Team Fortress is a game i used to play. So this past few years, i no longer have any regarding it and the recent events, walkthroughs and guidelines.

 

Try disabling all these apps during start up using msconfig.

Now perform a restart. Start up tf2. Whats your performance like now?

 

is there a way to hook up one of the game app buttons to turn on/off objectdock, rocketdock, rainmeter, rainlender2 and Xion player?

 

Work smart not hard:

http://www.inspectmygadget.com/2007/12/19/how-to-use-batch-files-to-create-a-working-environment/

You should also be able to link hardware buttons to a batch file so instead of having a "MCE Quicklaunch" button (like Gateway FX owners) you could have a "Gaming Mode Quicklaunch" I've been meaning to try it but I just haven't gotten around to it yet.

 

this probably wont solve the problem at hand here, but give this a shot:

type this in console "mat_queue_mode 2"

apparently, what it does is allow the game to use both cores of a dual core processor. However, some people will notice a drop in performance (one of those people being me), so if you do notice a drop in performance just go back to console and type "mat_queue_mode -1" to set it back to default.

 

Tried it. Crashes too often.

It runs very smoothly without any of these 3 applications running. Strangely, none of my other games have this problem.