<cc_config>
<log_flags>
<http_debug>0</http_debug>
</log_flags>
<options>
<save_stats_days>360</save_stats_days>
<exclusive_app>farcry.exe</exclusive_app>
<exclusive_app>Z2.EXE</exclusive_app>
</options>
</cc_config>
I would highly recommend using the <exclusive_app> cc_config option for games .... more info on that file is at http://boinc.berkeley.edu/wiki/Client_configuration , if you need it. My (superficial) understanding is that Vista and Windows 7 changed the driver model significantly from XP & earler, which places graphics operations in a different execution 'ring' than before, which on some simplistic level enables win7 to give you driver restarts instead of blue screens of death.
For example, my cc_config.xml file currently looks like this:Quote<cc_config>
<log_flags>
<http_debug>0</http_debug>
</log_flags>
<options>
<save_stats_days>360</save_stats_days>
<exclusive_app>farcry.exe</exclusive_app>
<exclusive_app>Z2.EXE</exclusive_app>
</options>
</cc_config>
New sheduler from Vista(and Win7 probably) performs faster than older from WinXP, but it looks like it doesn't obey process priorities even in bigger degree than WInXP one.
I've seen negative effect of running CPU-only BOINC apps (idle priority!) on video playback under Vista on Core2 Duo notebook.
I don't see such effects on single core AthlonXP (much less powerfull CPU and maybe even GPU) under WinXP.
Never tried D2 under Win7, but under WinXP it was never bothered by BOINC.
SO exclusive tag could be the single option indeed...
Jason, can Lasso "manage" problem I sow on AMD comp: if Cool and Quiet is enabled then GPU crunching is slower about 20%Concurring with Raistmer, I've always found myself disabling these kind of features. They're designed to slow things down to save energy. I turn that stuff off even on machines I'm not using for crunching, except for notebooks where it helps save battery power. My rationale is if I wanted a slow CPU, that takes a while to get up to speed when I do something demanding, I could have bought a cheaper CPU ;)
I play much more intensive games that DII and I find I always need to snooze the GPU on BOINC.
I play much more intensive games that DII and I find I always need to snooze the GPU on BOINC.Well, considering that app distributed on beta is just my own binary rev280 build, I think we ARE allowed. BTW, this was discussed long ago for third parti application. Answer is YES, as long as group of third party app users small enough.
As Far as testing on Seti beta, I assumed they wanted to test the app that we downloaded from them. Are we allowed or should we be using the latest beta from Lunatics. the current version on seti beta works fine on my 5850.
I've been able to play my games quite easily without glitching on the seti hybrid without snoozing the GPU. I noticed while using GPUz that the GPU is infrequent and used less than 50% of the GPU when processing. I have to assume results may vary depending on the strength of your GPUThe speed of completion (of the Hybrid app) has a lot more bearing on the speed of the CPU, than it has on the GPU,
I play much more intensive games that DII and I find I always need to snooze the GPU on BOINC.
I hope you are aware I am already 'snoozing' the GPU, I was and am talking about the current impact of CPU processing.
Under WinXP32 I could also run much more intensive games _while_ BOINC was still crunching along (for instance Mass Effect, Bioshock, etc). No detectable impact from BOINC running these.
Regards,
Patrick.