• 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.

why does seti make my comp run like a 233?

M

MikeMike

Lifer
1.9 p4 seti cli client set at low

when playing rtcw i had to set the graphics at 800x600 lowest quality and it was still choppy normally im at 1600x1200 and highest quality and no choppyness?

why?

setin it to high is just crazy! but i will do it over night

with cli my est. times are about 4 hours compared to the 22 it took on the gui
 


<< 1.9 p4 seti cli client set at low

when playing rtcw i had to set the graphics at 800x600 lowest quality and it was still choppy normally im at 1600x1200 and highest quality and no choppyness?

why?

setin it to high is just crazy! but i will do it over night

with cli my est. times are about 4 hours compared to the 22 it took on the gui >>



Did you install SETI Driver? It complements SETI@Home Command line.

SETI Driver

Set the radio button to "low priority"

In my experience, low priority let me use the computer like usual, normal makes it a bit sticky and completely unusable on high.
 
That's a known problem with SETI from way back. I know that whenever I've left it running while trying to play UT, nasty things were bound to happen - and this was even with the Linux SETI text client + the Linux version of UT!!! :Q

Only thing you can do is make that sacrifice - either in gaming or in crunching WUs.... 🙁
 
If I have it set to low priority, it doesn't really interfere with game playing. What happens is though that my crunching S L O W S way down!

So for the duration of the race I am not playing games, but thats my decision everyone has to make their own. 😀
 
I think it would be interesting to get some stats/info on different configurations and what games will and won't play nice with SETI.

For example, I have an Athlon 1.4 running at 1450Mhz on an ECS K7S5A with 512MB of Crucial PC2100 DDR and a Hercules Prophet II MX (GeForce2 MX) and I haven't seen any problems at all running SETI along with UT at very high settings. In fact, UT doesn't even seem to slow down SETI, since the estimated completion time (time to finish, not time remaining) only varies by a few minutes after I have played UT for more than an hour. I've tested this several times always with the same results.
 
Why don't you guys start to play Comanche 4? It's a very DC friendly game because when you are not playing (sitting in the menu and mounting your hellfires) the cpu use goes down to 0% 🙂
 
Fardringle - In my case, I have UT on an OC'd P3 600@972, and from what I've seen posted on some of the UT forums, some of this flakiness with SETI has to do with the SB Live! cards (which I use). Others have had issues with DirectX (various iterations) and SETI. Alternately, whenever I'd played UT on my dual Xeon running 2K AS (back before I got the P3 system), I didn't see the problem as much, if at all.

I agree that some experimentation and reporting of results here are in order, and figure it would probably be interesting to see how UT would fare on the system I'm on right now, a T-bird 1.2@1.4 with DDR running SETI. 🙂

[EDIT: Just wanted to add that I use Voodoo cards - mostly the V3 3000s, which UT was originally written for]
 
If you're having slowdowns with your system while the client is running then something's wrong. Aside from Outlook under Win2000 and Corel under any OS, I haven't heard of SETI hurting any apps. The only issue I've heard of as far as the SETI client interferring with games is the swing meter in one of those Golf games. I don't know which one it was (Tiger Woods, PGA, etc) but my bud, rleach2, told me if he had the client running while playing the golf game it would cause the swing meter to be jumpy instead of smooth.

I play all my games with the client running. As others have said, the games take most of the CPU so the client doesn't get much. I just don't like shutting it down because I sometimes forget to restart it. Oh, and if you're running a dual CPU box your second CPU pretty much runs at normal speed while your primary CPU handles the game. 😛 😀
 
its is set on low but i have a gf3ti500 so that shouldnt be a problem but the quake engine is pretty dependant on the cpu isnt it?

so in reality seti and the quake engine might not be very good together

ut is more dependant on the gpu? so i dont know why that would be slowing?

correct me if i reversed it
 
nourdmrolNMT1 - What I've experienced in my case was jerkiness... but not continuous.

Part of the issue is that the 3.03 client is doing a number of different analysis on the WU depending on the angle range. If you are running a WU with an angle range of ~.0.3 or lower, then a pulse search analysis kicks in which is pretty CPU intensive. I know there was a pretty interesting but technical discussion about this on both Ars and alt.sci.seti a year or so ago, by a few folks who are or were client porters. Something about rotates and such in the analysis that uses a good chunk of CPU.

[EDIT: Just as an interesting followup - you might want to note the angle range of the WU you're running while playing just to see if this theory bears out.]
 
You must log in or register to reply here.
Back
Top