• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

seti cli causes stuttering in CS?

M

mchammer187

Diamond Member
anyone know of a fix for this i guess i could just turn off seti while i'm play but i'm wondering if there is a workaround

specs

P4 1.8A @ 2.4 Ghz
512 MB Corsair Rambus PC800
ATI Radeon 8500 + 6043 drivers
MAXTOR 60 GB
SB Audigy OEM
Intel 10/100 Pro
Hauppaugue WinTv Radio
Diamond SupraMax 56 K modem 🙁


anyone else have this problem?

i think it might be radeon related but i luv my 8500 🙂

no. of crashes in 1.5 weeks = 0
 
Wow...great system!!

If you are running SetiDriver with the cli version of the seti client, then set the Priority to "Low." If not, then try that combo.

What times are you getting with your new rig?
 
priority is set to low

my avg time is about 2:57

i've seen times of 2 hours 21 minutes when i was not doing anything

10 WU a day possible 🙂

7-8 normally
 
I've had to shutdown the SETI CLI(used with SetiSpy) when I play Star Trek: Armada.
rolleye.gif

 
I've not noticed any slowdowns or stutterings in CS when running Seti CLI and SetiDriver (which i do 24/7).

Not sure what this problem is, and with a system that powerful i doubt CS would be slowed down by Seti much at all 😱

/me is confused

ConfusedBW
 
the thing about seti is it takes 100% of your spare cpu cycles so faster machines produce faster WU's



<< Not sure what this problem is, and with a system that powerful i doubt CS would be slowed down by Seti much at all >>



the point is seti should not slow any system down at all if there is enough memory since it only takes "idle cycles"

i have the thread priority set to low so i dont know what the problem is

i do believe it is R8500 related though for some reason

Warcraft 3 does not lag me at all which is weird
 
Ahh but here is the thing. Most games (including CS) are helped by having a large cashe. S@H may only be using spare CPU cycles, but it is still resedent in the CAshe which can slow performance with some applications. ( graffix editing is the other thatcomes to mind, besides gaming )

I usually leave SETI on when I play Tribes 2 without a problem, but CS requires as much of your cashe as possable. just stop SETI before you play.
 
My original Asus GeForce V6800 64MB DDR didn't stutter on me while I was playing CS and had SETI cli running. Maybe because I'm on a cable modem.
 
Some games pause with SETi some don't ,suck it & see ,if it causes problems shut SETI off whilst playing ,don't forget to turn it back on afterwards😉

NWM
You play Armada?😀 ,cool I only recently discovered it when my little bro gave it me for xmas!
I love the game but sometimes the slow mouse scrolling & its buggyness drive me mad!
 
Winmodem icky icky, seriously get a hardware modem, I have on occasion encountered odd stuttering on systems associated with software based modems, sometimes they just suck up the cpu cycles....
 


<< Winmodem icky icky, seriously get a hardware modem, I have on occasion encountered odd stuttering on systems associated with software based modems, sometimes they just suck up the cpu cycles.... >>



its not the modem i dont even use that now

i am on the campus T3 (notice the intel 10/100 pro NIC)

the modem is for when i go home and i usually dont online game except for starcraft when im home

i just wondered if there was a possible workaround

because it is not even that bad still playable

just a stutter about every 4 seconds that is about 200 milliseconds long
 
Seti is not actually as nice as it could be. 😱 It runs at priority 4, where normal is 8 and lowest is 1. I'd suggest when you want to play a game, use Another Task Manager to turn down the thread priority to 1. Unless of course you're running NT/2K...

If that doesn't work, maybe run a batch that kills and restarts SETI? BTW, I use PrcView to run kill in Windows.
 
What OS are you using?

I noticed that with the 6025 drivers for W2K with my Radeon 8500 do the same here, and I went back to 6014 as rec. by ATi and all works great now!

Don't forget about the HL ATi Patch.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top