It’s good to know that Blizzard hasn’t forgotten this problem - and it’s nice to get an apology for the poor communication surrounding this bug - but it would be better to know Blizzard was going to fix the problem. If we had more good news to share, we would, but the best we can really tell you is that we have people actively trying to unravel this complicated thread. None of our tweaks, however, have been successful enough (as indicated by the thread) which is why we aren’t out here telling you to re test things right now. Without going into the complete technical details, we’ve spent more time reproducing things with Quality Assurance, found more problems, and tried more code tweaks to fix the things we’ve found since the initial hotfix attempts. We thought we fixed the problem, we were wrong, and so we went back to the drawing board. On behalf of all of us at Blizzard I wanted to apologize that we set kind of a bad expectation earlier in the thread. Unfortunately, the problem was deeper than what we initially had identified. That was what we tried to fix with the hotfix we mentioned above. When we got the initial report of this bug, we had our Quality Assurance folks look into it, and they helped us find some scenarios where the crashes happened.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |