EPT
.If you want to reduce CPU usage, you can edit your Variables.txt in My Documents / Starcraft II and add the line "frameratecap=60". This also reduces CPU usage as well as GPU usage, contrary to how I thought it worked.
+ Show Spoiler [Waste of time] +
Since SC2 runs at full frame rate, I figured it might be worth trying something similar to my CPU Savior plugin for Brood War. The results weren't anywhere near as impressive, since SC2 needs a lot more CPU time for its own use, but it still provides a possible benefit if you are streaming or recording games.
![[image loading]](http://r-1.ch/sc2sleepy.png)
I forced SC2 onto CPU 1 (right hand side graph). Half way through the graph I loaded SC2Sleepy - you can see it reduces the CPU usage, but at the same time reduces the frame rate (the spike at the end is when I took a screenshot, so ignore that
). As SC2 units have infinitely more possible animations and frames than BW, this may be a lot more noticeable than a reduced FPS in BW was.
Also, rather than risk hooking Starcraft II itself (especially in beta where the versions are so volatile), this time around it hooks the Direct3D drawing interface, so it can guarantee a delay after each rendered frame. This works similar to FRAPS and other overlay programs, however hooking Direct3D reliably is not so easy, since the offsets differ between Windows versions. The current version only works for 32 bit Windows XP, which is why I'm posting it here rather than a more public place.
By default it introduces a 10ms delay, capping you to a theoretical max of 100 fps. Since SC2 also needs CPU time, your actual FPS will be lower than this. You can configure the delay by passing a number on the command line, eg 'loader.exe 5' would introduce a 5ms delay.
http://r-1.ch/Sc2Sleepy-0.1.zip
To use: Run SC2 Beta, then run Loader.exe. You will here a Windows beep sound if it loaded successfully. An error dialog will appear if it did not.
If you get a code -2 or -6 error, it means the program doesn't recognize your Windows or Direct3D version. To help me accommodate this, download HookShark and run SC2 with FRAPS open. Use HookShark to pick the SC2.exe files, Scan, then highlight the two lines mentioning d3d9.dll, right click, copy line and reply with them here including your Windows version, service pack, 32/64 bit, etc. Since this has limited use, I will likely only support 32 bit XP/Vista/7.
I forced SC2 onto CPU 1 (right hand side graph). Half way through the graph I loaded SC2Sleepy - you can see it reduces the CPU usage, but at the same time reduces the frame rate (the spike at the end is when I took a screenshot, so ignore that
). As SC2 units have infinitely more possible animations and frames than BW, this may be a lot more noticeable than a reduced FPS in BW was.Also, rather than risk hooking Starcraft II itself (especially in beta where the versions are so volatile), this time around it hooks the Direct3D drawing interface, so it can guarantee a delay after each rendered frame. This works similar to FRAPS and other overlay programs, however hooking Direct3D reliably is not so easy, since the offsets differ between Windows versions. The current version only works for 32 bit Windows XP, which is why I'm posting it here rather than a more public place.
By default it introduces a 10ms delay, capping you to a theoretical max of 100 fps. Since SC2 also needs CPU time, your actual FPS will be lower than this. You can configure the delay by passing a number on the command line, eg 'loader.exe 5' would introduce a 5ms delay.
http://r-1.ch/Sc2Sleepy-0.1.zip
To use: Run SC2 Beta, then run Loader.exe. You will here a Windows beep sound if it loaded successfully. An error dialog will appear if it did not.
If you get a code -2 or -6 error, it means the program doesn't recognize your Windows or Direct3D version. To help me accommodate this, download HookShark and run SC2 with FRAPS open. Use HookShark to pick the SC2.exe files, Scan, then highlight the two lines mentioning d3d9.dll, right click, copy line and reply with them here including your Windows version, service pack, 32/64 bit, etc. Since this has limited use, I will likely only support 32 bit XP/Vista/7.
.
