I sadly do not have an SSD but thank you for the suggestion. You’ve been the most vocal and helpful blue on here. I am glad you guys have identified the problem. I can only imagine that’s just the minor part… figuring out how to fix a problem is a whole other thing 
Correct, however, it’s quite likely that those players either have a slower SSD/Hybrid drive OR they’re having a different problem they’re confusing with this known error. I checked some of those posts. Capital, for instance, is having GPU/CPU spikes. They’re probably having a normal performance issue and because we’re having this other problem, this is getting mistaken for the stutter. As I mentioned it may not fix it for everybody, and either way it’s just a work around. Not making any guarantees here but if this bug something you want to try to alleviate for the time being and you have the option, go ahead and give it a shot.
3 Likes
While I certainly appreciate the feedback, and the suggestions, this didn’t start happening until 8.2.5 dropped. So those people who do not have SSD’s (myself included), we had no problems up to that point. There is no “mistaking the stuttering for a performance issue”. Everything was running as it should, whether we had SSD’s or not. Suddenly blaming it on slower hardware is just a cop out. Whatever problem is going on on your end, is the only reason this is happening.
14 Likes
I don’t think he was blaming us. It is just a fact that non SSD’s are acting up for whatever new stuff they did this patch. I am not defending the fact that this bug got in… it’s pretty lousy that it did, but at least this blue confirmed a few things for us.
This makes me pretty angry. Way to pass the buck and responsibility. No this is not our fault b/c of older hardware. If that was the case, then why does the hotfix work? Do you guys even think critically? Just derp man, do not go full derp.
I swear to god the mods here sometimes act like nothing is blizzards fault, regardless of all evidence, common sense, proof that is presented in a logical easy to follow format. Pathetic…
5 Likes
Sorry if this caused confusion. I’m not saying the harddrives are the problem, just talking about a possible work around that may help some players while we fix the core cause. Let me use this post to compile all the relevant information for the investigation we’re doing on the bug in one location.
5 Likes
It is completely and totally on your end. Period. Do not try the side talking politician way of saying “Maybe maybe not…”
Accept responsibility and fix this in a timely fashion. Good lord man…
2 Likes
Question: why wow have to log actions in a file, that clearly dont break the game?
This is more of a debug setting, which is of no use for us (except dropping our performances)
1 Like
Well we know from player-made workarounds that the problem is excessive access on a certain file by the name of Hotfix.log. Note that SSDs have a limited number of writes before they crap out and this file seems to be written to dozens of times per second while the error is occurring. Using an SSD may make it less noticeable, but it’s still causing excessive long term wear if you’re not making the file read only.
Now, I know you don’t have a fix, but why don’t you enlighten the people as to what this file is intended for and why it’s being written to so much? Why was it not possible to just put out a hotfix to make the file read only by default until you come up with something more graceful?
9 Likes
What blows my mind is a random guy out there found the problem and came up with a solution fix pretty fast. So far nothing from blizz and they recommend to not use that fix so we are all waiting.
Maybe I don’t know, find him and hire him?
4 Likes
I just don’t understand why the hotfix file is needed at this point. Simply stopping it from working by putting it in read only (you can check it, it won’t record anything in your gameplay session in read only) sounds to me like this file needs to just be removed and halted on blizzards end so we can stop fixing it each launch.
1 Like
Any chance of confirmation that this will be fixed tomorrow while we’re already here?
I have been using the temporary fix (changing World of Warcraft_retail_\Logs\Hotfix.log to read-only) and it works very well. Even though understandably, Blizzard does not encourage users to tamper any default files unnecessarily, I believe it would not cause any harm in this case. Let me explain.
As a gamer, what are our concerns? They are:
- our gaming experience;
- our PC hardware’s lifespan;
- our game account.
By applying this temporary fix, we manage to restore our gaming experience and at the same time, mitigating the shortening of our PC hardware’s lifespan due to this bug (as pointed out above). So we solve (1) & (2).
So what really are the players’ concerns highlighted in (3)? I believe the concerns have to do with our game account in general - would we get banned for using this temporary fix for a bug that Blizzard doesn’t seem to fix? Would our game data be lost? Would my main suddenly disappear and become level 10 because of it?
So if you guys think carefully, there is a 0% chance that we are getting banned for it, since we are not doing any exploitation. We are merely using this fix as a temporary measure to fix the bug so we have (1) & (2) above. I believe the blizzard employee above is just following their SOPs when he or she advised us not to do anything on our end.
Then when we think about our game data carefully, the answer is obviously clear - none of the important data critical to our toons is stored on our PC! Everything is stored on blizzard’s servers! In a nutshell, whatever you do to your WoW client and its folders on your end would have absolutely no effect on your in-game toons!
In the worst case scenario (0.0001% probability) that your WoW folders somehow got corrupted beyond repairs, you can simply delete and download everything again within 30 minutes!
So it makes logical sense that we apply this temporary fix on our end while waiting for Blizzard to fix the bug. It is still better to revert the file back to its original state after the bug has been resolved because as someone pointed out above, the default settings must be there for a reason. But prior to the bug getting fixed on Blizzard’s end, I really see no harm in using this temporary fix on our end.
6 Likes
yeah. it keeps happening, but instead of 2 seconds is like almost a second, which is still noticeable. Not only doing quests but also killing raid bosses now.
In the other hand, with the logs “fix” is completely fine… and I don’t have a SSD at my disposal
1 Like
Come on folks… At least this blue is talking to us. Don’t take his words and turn them around on him. He plainly said it’s on their end but gave us a couple of things we could do to help. If we rip this guy apart the blues will never post here. Makes me realize now why they might not communicate much. Sure this is frustrating… I’ve been at my wits end, but at least we’re getting some communication now.
4 Likes
People that only play Blizzard games don’t have any idea how spoil they are… Almost any other company support is horrible compared to Blizzard
4 Likes
They increased the maintenance an extra hour… so maybe? I hope.
1 Like
The natives are getting restless waiting for a real fix. The time for this to be fixed in a timely fashion has past…and now the customers have been waiting PATIENTLY for almost a week. Not only that, but to fix a bug that has the potential to damage our system. I am sorry but no other word comes to mind besides “incompetent”.
This entire thread encompasses what is wrong with blizzard support. Start to finish read this entire thread. Seriously it is eye opening. At first they would not even consider this was their issue, and had people putting in hours of work going around and around chasing their tails getting nowhere. “O check your drivers! O update this, do that, post dialogs, ect ect”
When they finally admit that this issue “may” be their fault, a fix is all ready been posted on reddit. Then blizz says “No do not use that fix, we don’t recommend it” Well okay, what should we do then? Just ignore it and have it potentially break our hardware? U srs?
Then they backtrack, cop out, delay, shift responsibility and do some great double talk. Wow that was fun.
Actiblizz you got kids in Europe owning you for days at a time, people on reddit coming up with fixes before you, it is just one nonsensical blunder after another. Blizzard used to be smart about their product. Nowdays its literally dumbfounding what goes on in this company.
8 Likes
I think Blizz already made it non-fatal for PC’s. It was originally spiking my HDD’s utilization to 100%, but now it’s only reaching somewhere between 50-70%.
I’m no PC expert, but it sounds like it’s getting better every hotfix.
1 Like
Just wanted to throw my voice in here and say im still getting the issue after the hot fix. My Wife is as well.
1 Like