Glad my laptop has a heat-surge protector. Starcraft crashed my system earlier, phew. Thanks for the fix, people.
The beta was only for the multiplayer. The campaign was beta'd in a much smaller group.Spectre39 said:Shouldn't they have caught such an error in the beta? Or were people so worried with playing multiplayer to notice?
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.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.
What?John Funk said:while you slaughter the hell out of those nasty Zerg.
QFTPhishfood 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.
Nova5 said:Wow. That's a pretty serious oversight. They happen, but... Ho-ly crap.
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.Spectre39 said:Shouldn't they have caught such an error in the beta? Or were people so worried with playing multiplayer to notice?
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.Carnagath said:Nova5 said:Wow. That's a pretty serious oversight. They happen, but... Ho-ly crap.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.Spectre39 said:Shouldn't they have caught such an error in the beta? Or were people so worried with playing multiplayer to notice?
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...