Blizzard Offers Fix for StarCraft Computer-Melting Bug

BobisOnlyBob

is Only Bob
Nov 29, 2007
657
0
0
Glad my laptop has a heat-surge protector. Starcraft crashed my system earlier, phew. Thanks for the fix, people.
 

Kirosilence

New member
Nov 28, 2007
405
0
0
Thank god my computer has monstrous cooling.. Although it explains why the comp at the LAN cafe by my house kept crashing.
 

GodKlown

New member
Dec 16, 2009
514
0
0
Starcraft 2 is finally here... and leave it to a company named Blizzard to create a game that melts your computer. I-ron-y!
They should jump on the bandwagon of all the other companies that put out semi-defective products and release an apology ad.
"We here at Blizzard know you've been waiting a long time to play this game. We've taken our time to work out all the bugs, but apparently one slipped past us. But we're releasing a DLC to fix this problem, the Terran Fire Extinguisher! Keep it next to your computer as a reminder of why you love this game, all whored up with the SC2 and Blizzard logo! This is a limited time offer, so be sure to reserve yours today! Only $89.99, and $149.99 for the Collector's Edition which features the nozzle as a Zergling face that pukes foam!"
 

Ken Sapp

Cat Herder
Apr 1, 2010
510
0
0
Spectre39 said:
Shouldn't they have caught such an error in the beta? Or were people so worried with playing multiplayer to notice?
The beta was only for the multiplayer. The campaign was beta'd in a much smaller group.
 

lomylithruldor

New member
Aug 10, 2009
125
0
0
Mackheath said:
Jeez, Blizzard, I thought you were flawless with programming. Forgetting the debacle of the Patch 3.2 graphical errors for WoW, this is the only oversight I have seen you make.
LOL, blizzard is far from flawless with programming. Most major patches in WoW have bugs in them. It's pretty rare that you can play on the day these patches are released.

WoW takes a really long time to alt-tab compared to most games. The issue is most likely because of a memory leak.

Have you been to Dalaran? It always takes a lot of time to load and after it loads, you don't see any NPC or PC for some time. I've seen a good number of WoW client crashing while entering Dalaran.

I'm not saying they're bad, they're just far from perfect.
 

Jandau

Smug Platypus
Dec 19, 2008
5,034
0
0
So THAT'S why SC2 crashed on me yesterday night! It was just loading the ship deck after a mission and it did a CTD, saying something about my graphics card having no memory. I didn't think much of it and just went to bed, but now it makes sense...
 

Centrophy

New member
Dec 24, 2009
209
0
0
I have the same issue with NFS: Prostreet. Glad at least one company is fixing this kind of issue.
 

Phishfood

New member
Jul 21, 2009
743
0
0
Skipped the last few posts, this is killing me.

1) Your average monitor has a 60-90Hz refresh rate, this means that anything over 100fps is not normally displayed (unless you bought a really high end HD screen with a higher refresh)

2) Your graphics card does a pretty much constant ammount of work while gaming. If a frame is hard to render it takes longer, if its easy it moves on to the next frame. 200fps will not kill your graphics card. I have made plenty of experimental openGL apps that ran at over 1,000fps because there was nothing in them. Point being - if your graphics card is overheating, it is improperly cooled. This is not Blizzard's fault. The fact they can fix it is irrelavent.
 

blankedboy

New member
Feb 7, 2009
5,234
0
0
John Funk said:
while you slaughter the hell out of those nasty Zerg.
What?

I AM the Zerg, fool!
In Starcraft 1, anyway. I don't have SC2, I might get it sometime.
 

gl1koz3

New member
May 24, 2010
931
0
0
I just force Vertical Sync through the Control Panel. Smoothing out much of the issues. Some lag at places... maybe... but I don't care caring.
 

veloper

New member
Jan 20, 2009
4,597
0
0
Phishfood said:
Skipped the last few posts, this is killing me.

1) Your average monitor has a 60-90Hz refresh rate, this means that anything over 100fps is not normally displayed (unless you bought a really high end HD screen with a higher refresh)

2) Your graphics card does a pretty much constant ammount of work while gaming. If a frame is hard to render it takes longer, if its easy it moves on to the next frame. 200fps will not kill your graphics card. I have made plenty of experimental openGL apps that ran at over 1,000fps because there was nothing in them. Point being - if your graphics card is overheating, it is improperly cooled. This is not Blizzard's fault. The fact they can fix it is irrelavent.
QFT

better cooling people.
 

kingmob

New member
Jan 20, 2010
187
0
0
I have a hard time believing this is an actual problem? Seriously, if your computer can't take a few hours of running at max speed you are doing something wrong.
 

Carnagath

New member
Apr 18, 2009
1,814
0
0
Nova5 said:
Wow. That's a pretty serious oversight. They happen, but... Ho-ly crap.
Spectre39 said:
Shouldn't they have caught such an error in the beta? Or were people so worried with playing multiplayer to notice?
This has been known for a long time in the beta and Blizzard did post this workaround back then, we all expected it would be fixed for the release version but apparently hotfixing 2 lines in a txt file is too much work for them? I don't even know and this is such a colossal bug, I can't believe it's still there... people deserve to sue if they got their hardware destroyed.

Edit: After thinking about it some more, it seems to me that they fixed it for the multiplayer (which was all the beta had of course) but they neglected to fix it for the single player too (since the article mentions it is only a problem during the Hyperion scenes). If so, well that's pretty stupid...
 

lomylithruldor

New member
Aug 10, 2009
125
0
0
Carnagath said:
Nova5 said:
Wow. That's a pretty serious oversight. They happen, but... Ho-ly crap.
Spectre39 said:
Shouldn't they have caught such an error in the beta? Or were people so worried with playing multiplayer to notice?
This has been known for a long time in the beta and Blizzard did post this workaround back then, we all expected it would be fixed for the release version but apparently hotfixing 2 lines in a txt file is too much work for them? I don't even know and this is such a colossal bug, I can't believe it's still there... people deserve to sue if they got their hardware destroyed.

Edit: After thinking about it some more, it seems to me that they fixed it for the multiplayer (which was all the beta had of course) but they neglected to fix it for the single player too (since the article mentions it is only a problem during the Hyperion scenes). If so, well that's pretty stupid...
I'm pretty sure in the EULA there's something among the lines of "The Company cannot be held accountable for any damage or data lost caused by a malfunction of the product" because they all have it.