08/31/2012 12:48 AMFunny only because I reported that bug in the first week of beta.
Posted by Felinae
I'm sure they had more pressing issues to deal with though. Asside from this cpu thread issue, which is understandably easy to miss (cause when they QA something, they fire it up and see if it runs, all functions work, and it's not crashing, I don't suspect they really stress test it like a gamer would for hours on end though, or they wouldn't ever code anything :) ). They really did a good job cleaning up the huge list of mac issues during the crunch time though, remember how big the mac issues list was about 10 builds ago? macros not working, addons not workingm, crashes that only affected, mac, etc. They shrank that list to almost nil. Give the devs more props.
I think D3's launch really pulled a lot of time from MoP beta work. beta sat in a standstill of zero progress for several weeks following D3's launch because D3 needed all hands on deck to fix some major issues of it's own. Things seem to be smoothing out again though with 5.0.4 finally shipped, D3 is fairly good shape (not perfect, it still stutters like stammering geek on his first date, ever. But coming along anyways). All they gotta do now is give 5.x a little bugfix patch then they can take on the next challenge: HoTS beta :)
That's great about the overheating, but there are many in this thread also complaining about suddenly very low FPS rates. What's being done about that?
I suspect the fix will go hand in hand with both. cpu that's wasted frivolously means less cpu used on actual important tasks, like keeping fps up. Hopefully next patch will address that for you too.
Although, do bare in mind, if you didn't port your config.wtf from 4.x to 5.x, and leave your settings at "custom" in new client version, your settings will never match old settings again. Reason w hy, the sliders were retuned. I can tell you from my own internal testing, 5.xes fair is like 20% more detailed then fair of old. for example, the old farclip value of "fair" on 4.x was like 670 or something. However, on 5.x, its 800. so side by side comparison you'd notice you can see further on 5.x client on fair then you could on 4.x, but it also means it's more demanding. This translates into the settings not being equivilent at all. It's an important thing to note when comparing before and after fps. that's why the best fps comparison is done by those that did not touch graphics settings on iniitial load of patch, then those sliders will say "custom" because they will still be at their pre patch 5.x values until moved.