Blizzard confirms StarCraft II overheating issue - gives solution
- Thread starter Tinman
- Start date
niftyshorts
New member
My laptop definitely seems to have overheating problems...
Your laptop overheats when you open Outlook dude. I don't think it's SC2.
Leakysandwich
New member
niftyshorts
New member
Raven Gold
Local Boy Hunter
I just got the game and installing now, will do those things anyways, don't wanna take the risk.
HavocXphere
New member
That explanation is BS imo. If you write your own 3D app & make it render very little then it'll also “render the s**t out of certain screens when there is not a lot going on" at 1000+ fps and yet it causes no overheating.
Think of a PC barely handling Crysis. That means its rendering below Vsync and also rendering flat out. And yet there are not a bunch of PCs overheating with Crysis.
Something about this entire issues is very off.
None of the games do. They all just have vsync on or off.
Think of a PC barely handling Crysis. That means its rendering below Vsync and also rendering flat out. And yet there are not a bunch of PCs overheating with Crysis.
Something about this entire issues is very off.
Outlook isn't that far away from norton bloat-wise, especially if multi gig .pst files are involved.If you said "When norton loads" I would've understood, but outlook? You cut him deep!
Last edited:
Its definitely there. I have a 5970 and I'll hear the fan spinning up to 40% now and then while in the menus, it doesn't do this in-game. The menus are working like Furmark at the moment, letting the cards max out their draw rate.
Not a problem for me, I have more than sufficient cooling, but I can see how it could cause cards that have gathered a few years of dust or in poorly cooled laptops to overheat.
Not a problem for me, I have more than sufficient cooling, but I can see how it could cause cards that have gathered a few years of dust or in poorly cooled laptops to overheat.
I still can't see why the "fix" was given when they could have just said to turn VSYNC on. I mean, if your LCD only manages 60Hz it's going to cap your framerate at 60fps anyways. Unless you're still running a CRT monitor or a new 120Hz LCD...I don't see why VSYNC wasn't the obvious answer?
Avatar
New member
I think you've kind of answered your own question there..
This fix will cover everybody, while the VSYNC will leave out some users, so they've covered all bases with one simple fix, rather than publishing a (albeit very slightly) more complicated one saying 'if your hardware is this, do this, if your hardware is that, do that,' etc. Just less room for mistakes this, IMO.
ChameleonDevil
New member
Ok, I hope Im not too late... luckily I havent seen any graphical errors; which means my graphics card is still fine.
Nearly completed the single player campaign... never noticed problems.... everything Max on 1920x1200.
Well, Im going to [fix] the game tonight, just to be sure...
Agreed with others, just release a patch to fix it!
Nearly completed the single player campaign... never noticed problems.... everything Max on 1920x1200.
Well, Im going to [fix] the game tonight, just to be sure...
Agreed with others, just release a patch to fix it!
Xero
Official Zombie Slayer
Regarding Vsync
There are a lot of additional issues caused by enabling Vsync on certain Engines, including but not limited to jitter, Texture degradation, Performance lag etc
So although It might solve one problem, it will most likely cause performance issues if the engine does not support Vsync.
And lol, what do you guys want a patch for, fsk, I can whip up a self installer package that replaces the txt file with a new one containing the variables if you need one
They won't release a patch to fix a singular issue, but I can guarantee you that it will be included in the fix list for an upcoming patch addressing a few more issues
There are a lot of additional issues caused by enabling Vsync on certain Engines, including but not limited to jitter, Texture degradation, Performance lag etc
So although It might solve one problem, it will most likely cause performance issues if the engine does not support Vsync.
And lol, what do you guys want a patch for, fsk, I can whip up a self installer package that replaces the txt file with a new one containing the variables if you need one
They won't release a patch to fix a singular issue, but I can guarantee you that it will be included in the fix list for an upcoming patch addressing a few more issues
Last edited:
Just thought I'd throw this in here.
There is no such thing as an "overheating" bug, software other than drivers can't make your hardware overheat, it just doesn't have access to increase the volts, clock speed or fan speed of the card to do that. What software can do is make your hardware run at maximum load, which it should be able to do and have sufficient cooling to do anyway! If it can't, return on warranty for design flaw/manufacturing fault/fan damage, the responsibility lies with the card designer/manufacturer.
On Blizzards side, its probably not high priority for the reasons above. Its an inefficient use of hardware that needs to be patched, but it's not likely to get a hotfix dedicated to hit.
There is no such thing as an "overheating" bug, software other than drivers can't make your hardware overheat, it just doesn't have access to increase the volts, clock speed or fan speed of the card to do that. What software can do is make your hardware run at maximum load, which it should be able to do and have sufficient cooling to do anyway! If it can't, return on warranty for design flaw/manufacturing fault/fan damage, the responsibility lies with the card designer/manufacturer.
On Blizzards side, its probably not high priority for the reasons above. Its an inefficient use of hardware that needs to be patched, but it's not likely to get a hotfix dedicated to hit.