Small lag on quest turn ins and WQ completed

I know you posted this, that you guys are looking into it 22 hours ago (as I write this)
But everything is 1.000 times worse today.

Everything lags and bugs, both in open world, Dungeons and Battleground. People sais that Party synk doesn’t work and LFG doesn’t pop. There is lag on Spell and combat visual/sounds, and you have to wait for the sound and visuals to catch up before you can loot, and then you get lootlag. There is music lag, lag on each and any interaction you do in game, be it with NPC or ingame Character interfaces. You lag when you dis/mount, when engaging combat. It has gotten only worse and worse since this morning, and is allmost unplayable right now.
And when you zone, it takes EXTREMELY long time (packed with heavy lagspikes) for everything to appear.

Even the minimap, Map, popup quests, loot/item visual is bugging out now.
I can’t imagine how all this will get when we approach peaktime.

And speaking of the US forums, there seems to be a lot of frustration over there about the lack of communication and even more so, the seemingly lack of competence from the dev team supposedly working on this issue.

I’d just like everyone to remember the nature of this “bug”. This is something that doesn’t actually affect a lot of players and there seems to be 1 thing most people experiencing this has in common. Which is a low speed hard drive.

There’s many possible reasons why this issue is taking so long to get a clarification or an official fix but there’s a 3 main ones I can think of:

  • The first one is: Because of this workaround, which is seemingly pretty effective and doesn’t seem to cause any immediate harm to the game or have much if any negative side effects, this bug is just not being prioritized as heavily as it otherwise would’ve been. Blizzard has stated they do not recommend resorting to this solution but they’ve also acknowledged that it works and serves as a short term solution. Just long enough for them to be able to finish up previous hold ups before thrown into this one.

  • The 2nd is simple, this is all a coincidence and the bug has nothing to do with logging text files at all. Because the workaround is so effective, it’s easy to assume we have found the problem. Although, it’s very possible that isn’t the case and it’s purely coincidental that this fix works.

  • The 3rd is maybe the hardest to swallow but is the most likely in my opinion. It is not a bug. More so an oversight or miscalculation. Remember this issue is seemingly only really affecting people with low speed hard drives. That is why this fix is working. Writing tons of lines of text in real time while playing the game on a slow hard drive can and will give you reduced frame rate or freeze your game entirely while the lines are being written. That is why this little fix works. Because you remove the writing permissions from the log files.

    It is possible that some change was made to the game to intentionally log more information in real time but didn’t take into consideration or misjudged the effects it would have on older hard drives or external USB drives which a few of us are still using. In this case, it might take a while to get a permanent fix, as the dev team would most likely have to rewrite lots of code to fit a solution to an unexpected problem that is only really affecting a minority.

    It is also possible that there is a bug, but it’s not with logging but the logs are recording the bugs, causing the logs to appear as the problem. People with higher speed SSD drives are unaffected by this as the reading and writing speed of these can keep up with the amounts of information that has to be written quickly.

    In either case, the best thing to do is invest in a new SSD drive for faster read and writing speed. Because the core of the problem is actually not on Blizzard’s end. It’s on ours.

2 Likes

I got a new PC two weeks ago with an SSD… the difference is ASTOUNDING.

Hotfix log thing Worked for me and it also improved my loading times in some zones, Most likely going to move my WoW over to my SSD as it’s just alot better(Mainly used it for my OS) I do feel for some people though most people don’t have an SSD especially if it’s a budget built PC. if you do have the money though, it’s deffo worth picking one up and tbf you can get them quite cheap now, I know the Retail stores by me sell them quite cheap.

I did this “fix” with the Hotfix.log, I disabled all addons and I use SSD as well. I still have the very same issues constantly, though slightly less now since I did the hotfix thing.

After the update issued in EU just a while ago the issue still persists…

You can also consider this when here is day, devs in U.S. are sleeping well and dreaming about cool game, so most likely any fix will come when we will be sleeping, sounds logical to me. :slight_smile:

Actually, it isn’t on our end, something went wrong in the coding and caused the hotfix log file to mess up on HDD’s, as a company, especially Blizzard, you cannot -ever- expect your entire playerbase to invest in SSD’s, expecting people to have SSD’s as a standard with the minimum requirements for WoW doesn’t work.

You can’t release an update and go “Don’t you guys have SSD’s?”

4 Likes

I just logged into battlenet, and it downloaded a 600 Mb something patch. Logged into the game, it seems the frame drop has decreased, but I still had stuttering and frame drops while moving around in Nazjatar. Still seems to be an issue.

I can more actually hear my HDD dying rather than writing after this update.

I have tried to find a patch note for this hotfix…but i cant find one anywhere…I wonder what they fixed… :worried:

Wednesday the problem will most likely be fixed, atleast; I hope, game has been unplayable since 8.2.5 with the freezes.

Still happening to me, but not as bad as it was. Blizzard still aware of this issue?

Is not fixed by any means, the issue it’s still out there when returning a quest it keeps lagging…!

1 Like

Fingers crossed for Wednesday’s patching… :slightly_frowning_face:

1 Like

Use my batch file to launch the game. Not sure which thread I posted it in so I’ll add it here again.

Just create a text file in notepad called wow.bat. (not wow.bat.txt!) Put this text into it and save. Double click this file on your desktop to launch wow. It will take care of everything and wont screw up the launcher should you restart it.

Edit the ‘wowpath’ as appropriate for your system.

@echo off

set wowpath=C:\Users\Public\Games\World of Warcraft\_retail_

echo ---
echo wowpath : %wowpath%
echo ---
taskkill /F /IM Battle.net.exe /T > nul 2>&1
taskkill /F /IM Agent.exe /T > nul 2>&1
attrib +R "%wowpath%\Logs\Hotfix.log" > nul 2>&1
attrib +R "%wowpath%\Logs\Tooltip.log" > nul 2>&1
start "" /B /WAIT "%wowpath%\Wow.exe"
attrib -R "%wowpath%\Logs\Hotfix.log" > nul 2>&1
attrib -R "%wowpath%\Logs\Tooltip.log" > nul 2>&1
exit

If it is HDD related, I do optimize my C: in Windows 10.

It doesn’t take away the problem completely but decreases its effects. Problem is much less apparent when I optimize the disc.

If this issue still persists after the Wednesday reset, I’ll be getting myself an SSD as I’d like to play the game I pay for.

They said they may have found a solution on us forums.

Just wish to say I went around the issue by uninstalling the game and then re-installing it on my SSD. There’s no freezes at all now for me.

Of course this is not a solution, just a workaround because the game worked perfectly fine on the HDD prior to 8.2.5 update, but atleast it works this way now. Still hope they find a solution for the HDD.