Even some abilities on my Evoker causes stuttering, even in deserted areas.
5 Likes
Any updates blizzard? Any communication? Are you getting close? Hows the weather??
…
3 Likes
Me wondering the same thing its weird with how big this post is and no communcation from them yet.
2 Likes
Agreed. Gaslighting isn’t a fix for technical issues.
5 Likes
You know whats funny go one of threads about the error memory issue i swear when there responses to them they are working on it but if that does not fix it your computer does not meet the requirements to play either upgrade or dont play. I was like wow your really going to say that to your customers
1 Like
I’ve noticed some boss abilities cause it too, like when Melandrus casts Piercing Gale.
4 Likes
Well When I was getting stuttersd last night I checked the memory usage and the standby memory was just about maxxed and I cleared it out and boom went back to being fine again.
I am unsure if clearing Standby memory is really a good idea but I learned it from another game I play that uses Single core and such and that had fixed stutters in that game as well.
I am going to further test it but I think that is another root cause in the stutters. along with maybe overcrowded servers and limited CPU Usage/Core…
So far 3 things I found that might be the issue and wondering why the people from Blizzard can’t seem to find out what is wrong.
I am sure there are other smaller issues and others besides me have noted them but it all seems to be snowballing together…
IDK, I guess WoW has so many players they don’t care if a few here and there quit. IDK what it would take for Blizzard to finally come togetehr to fix these issues.
5 Likes
Nope. No updates :(.
This and it isn’t helping Blizzard fix this either. It’s not helping anyone at all. It just trolling.
Wait what seriously? 
I have seen players say this and well trolls…
I think it’s interesting what you just said. Because I think they are looking for one common issue… When in reality it might be a one common and bunch of little issues that differ. I mean some people playing with no sound helps… Yet others it makes no difference. People delete there WTF, Cache, Interface and it helps… and for others it makes no difference… So many instances like this. Blizz is legit looking for a needle or needles in a haystack.
2 Likes
Well I was hoping that the memory leak was just a WOW thing but I was just sitting here on Desktop and my Standby Memory was maxed so maybe not just an ingame thing but IDK…
I think the one common is the CPU core limit since this game is CPU Based it would factor in a lot of end users issues. The Overcrowded server I mena there is only so much Bandwidth a Server would be able to handle and I do not know what that limit is maybe it is fine IDK but it does seem to be worse on peak times…
Yes they are definetely looking for a Needle in a stack of Needles… I would like if someone came here with some official word and if they needed help with this issue what can we end users do to help instead of just bashin this that and the other thing…
There should be some official word on this at the minumum, I was looking at how much Blizzard has made with WoW alone and well it is in the Billions probally hundreds of Billions if you factor in all the extras like buying mounts and such…
There should be no Financial reason this could not be resolved… if they suffer manpower well time to hire would be in order…
3 Likes
Went back to World of Botcraft because of this issue. Retail is running so poorly for me.
2 Likes
Variable Rate Shading Graphics Options on the Patch 10.0.7 PTR - Wowhead News
Another useless setting added that REDUCES GPU load, which just makes this problem worse. It’s well known WoW is CPU bound, and putting as much load on the GPU as possible, would make things better.
Can’t tell if Blizzard is trolling us or if they’re incompetent, and try to look at every solution but their own game engine…
3 Likes
I haven’t bothered trying the 10.0.7 PTR given how ignored feedback was for previous PTR versions, however it might be interesting to see if there is any impact at all with the use of VRS in reducing stuttering by changing the load on the rendering pipeline. I’m not going to hold my breath though.
1 Like
Reflex doesn’t even really work with WoW either, so I doubt. They just keep adding things to an ancient engine, thinking it will perform like modern 2023 AAA games.
1 Like
Yeah, other than for PR spin I’m really not sure either. Reflex is designed to minimise the time between input on the mouse/kb and output on the screen, which all sounds great until you realise that you’re playing a server based game that has (at best) double digit millisecond latency from the server to the client.
5 Likes
I haven’t personally experienced this… Well yet at least lol… But I’ve seen people talk this tho. I’ve seen people say bnet and WoW just eating their memory….
Bingo… It’s the way WoW utilizes the CPU. And probably the engine itself.
This.
Yikes… The CPU needs the optimized and the load balanced on it…
I think fuglymugly said in a forum I saw that high end pcs notice it more… I think because the better your hardware is the more you are gonna notice how unoptimized the game is. (Something a friend was talking with me).
My sibling said WoW engine came out a little after PS2… We are on PS5. The engine needs an overhaul so those with higher end pcs and hardware can optimize the game for our system… And maybe have setting for those running it on less optimized pcs or older pcs… I dunno.
Edit: All I do know is this particular stutter and fps issues in this forum started with that pre patch… From all I’ve read and seen.
2 Likes
Yeah, if we were still playing with vanilla WoW requirements, we’d all be on 1-2ghz cpus(most not even dual core yet), 512mb to 1gb of ram and 32-128mb of VRAM.
This is correct. The “CPU time per asset” has increased this expansion, like it usually does each expansion, except this time they might have gone a little further than intented. It almost adds up like a log(n) vs n. It could be a number of different factors like the base materials increased in instruction counts like from 150 to 300, it could be something in the culling passes that are eating up a bit too much time, it could be the skinned meshes having increased work done, it could be actual bugs, etc etc, but it leans mostly toward either something on the material end or the culling end that are causing the bottlenecking.
I ran a lot of testing the other night and found that while skinned meshes are pretty heavy on the CPU (definitely higher than before), it’s mostly looking like the material instruction or culling end of things are what is causing the bottlenecking. I lean more toward the culling side of things because it coincides with the dragonriding system and the need for changes to handle the high travel velocity. If they are using hardware occlusion queries, the CPU might be stalling while it waits for the GPU to finish the task, which will still show up as load on the CPU side if it’s spinning in place waiting for the data to return. Meanwhile, the CPU still doesn’t know what assets it’s going to need to batch for things like IO operations (loading models, textures, sounds, etc). Then, when it finally does get the information back on what it needs, it then has to quickly load it or maybe stagger it out over a few frames.
Probably some trade off between performance and not being able to even allow those kinds of movement speeds. This is already evident if you look at the popins issues with decorative scene pieces like bushes, lamps and doodads that sometimes load in at uncomfortably close distances. Every engine has a floor level of performance even in an empty scene, so it’s possible Blizzard raised it, but might have gone a hair too far and didn’t have a choice to compromise to some middle ground between performance and functionality. Sometimes you have to pull a ripcord on some bump up in the hardware requirements for an engine and sunset support for older hardware and versions of Windows.
So if there are any non-wow variables thrown into the mix, that hinder any of the back and forth of information, as in the three body problem of wow-windows-gpu drivers, it’s going to affect the client much more strongly. Which is why they’ve stated that this fix is going to take an effort from all three sides, to fix any remaining stuttering issues people have, but I also suspect that it factors into the CPU bottlenecking as well.
2 Likes
It’s definitely a bottleneck of some sort. More likely than not; CPU-side.
The wait for an improvement continues…
2 Likes
Pawgwalker again with a wall of text, partly admitting yet again it’s the game. Wonder when he purely blame it on hardware again.
Patch 10.0.7 doesn’t have any stutter fix as of yet, don’t hold your breath.
2 Likes
He keeps going back and forth huh? He keeps going from its our computers> to its all in our heads> to there is a problem> loop back to the start.
Definitely a pattern lol.
2 Likes
It’s exactly the way wow uses the cpu. I was playing ff14 earlier and I was doing an activity that had another 30 - 50 players around me and it was butter smooth. Not a single hiccup. Wow, I fly anywhere near another player and the game hiccups while loading that player.
7 Likes