|
Ever since the 1.5.3 patch came out, my framerate has became unusable.
Since 1.5.0, my fps has gone down slowly, but up to and including 1.5.2, it was still playable. At 1.5.3, things became totally unplayable, in the range of 0fps when the game gets long. Updated graphics drivers and still didn't help. Tried all of the variable tricks and didn't help. There was a correlation between gaining temporarily some performance by removing the programdata cache for SC2 and battle.net. But that increase was only temporary, basically running it right after removing the cache, that instance was ok. Subsequent runs was bad. My system: Core i7 940 AMD 5750 GPU 12 GB ram SSD hard drive Windows 7 x64 dxdiag report: |
|
|
|
|
i always have firefox open and i play fullscreen, all the same way before patch 1.5
i dont think this has anything to do with the fps drop. its easy, before patch 1.5 everything was perfect, after patch 1.5 many people are having problems with this and many other things. i dont get why is that hard to fix. |
|
Full screen mode, and no other applications. I used to be able to run video on a second monitor with extreme settings with no problems. With this new patch, lowest setting with no other programs still cause it to drop to 0fps.
I agree with spirit, nothing changed in our system from 1.5.2 to 1.5.3, but the 1.5.3 patch caused a 90% fps drop. Thats nothing to sneeze at. That is a BUG. |
|
So im trying to figure out whats the bottle neck in this fps issue. Guess what, my cpu never goes over 30%, and GPU never goes over 26% even though the fps at the time was in the teens. So its telling me my hardware is starved of stuff to process. So SC2 is having some software bottleneck going on, not able to supply enough stuff to process. Please fix this.
|
|
Edited by Spirit on 10/6/12 8:43 AM (PDT)
someone talked about this in another thread and said we have to put "processAffinityMask=" in the variable folder.
you have to put a number that depends on how many cores you have, but it didnt work for me. |
|
the processaffinitymask trick was tried, and it did not work. The processors were being taxed at least partially in 4 of the cores, and the other 4 cores had very little usage. This might be the affinity mask, or might be their thread usage. Either way, it means its taking advantage of at least 4 cores, but not 4 others. I've tried different masks to use all cores, or just the non hyperthreaded cores, but both had no difference. Its not the mask thats the limit. Its their graphics efficiency.
The cpu can take whatever sc throws at it right now, the gpu can also take it. However, since the gpu is using 0 to 26% processing power, it means their code is not efficiently sending stuff to the gpu for processing. |
