Massive stutters with DF client

I will keep ‘bothering’ responding as long as you keep posting and generalizing your single data point in any way that could lead to this issue, which is most certainly not resolved for all systems to the state before the patch, to seem solved enough to Blizzard to warrant no further fix from them than changing the default value of this CVAR.

I am data and accuracy focused, and toxicity will not scare me away.

Also, I should inform you that even when set via the config file, these values are still known as CVARs (console variables). And that in my own previous posts in this thread stated that I have verified it is set in the config.wtf file.

And in regards to your edit: About using the ‘tools’ to check the ‘spikes or wtv’ I am getting. Frankly, I simply don’t believe you did and/or know what you are looking for. That is a subjective character judgement call on my part, and it is possible you did, but based on your commenting style, I simply find it unlikely.

2 Likes

I’m just going to mute you lol. Have a good life!

A slight hiccup on character loading screen when I log on

Wintergrasp Offense - good through team fights, constant crashes during assault on east wall.

Ashran - slight lag throughout.

AV - slight lag throughout

Windows 11 build 2200
2TB SSD, 32GB Ram
Nvidia RTX 3080 TI, 32GB Ram
System settings, Graphics High/ Ultra

Same issues here.

i9, 2080 TI, 64gb of RAM, no add-ons installed.

With my graphics maxed and ray tracing on before patch, I was solid. Fast forward to now, and last night while in Bastion, I got three blue screens after some insane frame dropping.

I had to turn my graphics down for it to stop, which is something I’ve never had to do with WoW, ever. Lol.

I can run RDR2, FFVII Remake, etc, all maxed out, but freaking WoW causes my computer to explode. Awesome.

2 Likes

The latest PTR build (which should hit live soon™) changes the GxAllowCachelessShaderMode cvar to 0 by default so that should resolve it for at least a bunch of people (as manually changing it did for me, FPS still lower than before, but no stutters). Hopefully we’ll get an official update on this (and the lower FPS in general) soon.

9 Likes

Im glad blizz heard the outcry this time around but I truly hope theres a better fix down the road.

4 Likes

Same with me

This is not a real solution tho, and I hope so too. Maybe add DLSS as well if you can pass it on? I should have like 20 fps more than I have currently in Beta.

2 Likes

I tried;
/console cvar_reset gxallowcachelessshadermode
/reload
It did not work.
I installed the addon and the value was still 1.
Changed to 0 and no more stutters.
Thanks!

AMD Ryzen 9 5950X + 3080TI

I have the same stuttering issue. It seems to be worst when in areas filled with other players.

i9-12900KF
32gb ddr5 5200
3080ti
Samsung 980pro

The game runs between 150 and 350 fps most of the time at 4k, but these stutters appear regularly. At first, I thought it was laggy loading of assets when going to populated areas, but my latency is 14ms.

Yep, I was going to bring this up, but it’s pointless on the forums to try to argue this stuff. They’ll still be convinced that it’s not true.

Do you have any actual emperical evidence of this other than “just trust me bro” proof? Placebo and Nocebo are a helluva drug…

How are they set up and how stable is the test environment? Unless the refresh period is set to zero (updates every frame), then the numbers are kind of useless. Also, unless you’re in an area with a static environment, with no extra things popping in and out like players, then the numbers are useless. Use a garrison or an instance to test, that way the benchmarks can’t be tainted with random variables that are out of your control.

They will just change the value of the variable on the server and client end with the next patch and probably override any playerset values in the config file.

It is though, the default behaviour for games that use runtime shaders is to store a compiled cache, after they have been compiled. By not allowing that, you’re making the game have to rebuild them again every time it needs them. That’s where the hitching comes from, rather than taking advantage of a saved shader that has already been neatly folded for them (depending on the shader complexity, you’re talking magnitudes differences in time. Probably in order for 1k to 100k faster than recompiling the shader). Also, the game will perform garbage collection from time to time, getting rid of stale assets in ram, which means some shaders might be on the chopping block if they are low priority or if they’ve gone unused for a length of time.

That isn’t the correct command.
/console cvar_reset or cvar_default resets the game client
the gxallowcachelessshadermode has be run as its own command.

Solved for me. My FPS tho seens to be stuck at 48 fps. Prior to pre patch I could break 100 fps. Cant go up no matter what!

Redo your graphics settings. The patch reset them all to defaults.

Gonna try thx!

Again, not a solution as there’s still stutters and lower fps than the day BEFORE prepatch hit live using this “fix”. I use RTSS in various locations, also instanced ones for accurate numbering.

2 Likes

The lower FPS is due to the base requirements of the game going up. This has happened with almost every single expansion so far. That part is normal. If you’ve run the command in this thread, then any remaining stuttering is likely your system, addons or your graphics settings being changed from what they were a week ago before the patch. As I just told someone, the patch reset your graphics settings to the defaults. Go redo them exactly how they were before.

On my PC, there’s no frame rate difference and the stutter is gone now. I can cap to 144hz(gsync+vsync on) with a completely flat frametime curve and no stutters. It takes a ton of overdraw from dense/unoptimized particle effects to get it to dip at all, and even then, it’s maybe down to like 100fps. I frame lock to 90 though because there’s really no gain going beyond, except for an increased power bill and premature component wear.

WoW just downloaded a small patch and updated. I logged on just now to test and it seems most of the stuttering has cleared up! I’m cautiously optimistic , will test more later tonight to see if it’s truly been fixed! :slight_smile:

2 Likes

The RTSS graphs are my empirical evidence and yes I can post them, but it still doesn’t mean much other than verifying my own data point that stutters are still present with the cvar set. I do not however, have any screenshots/records of my typical Oribos graphs before the patch, as I had no reason to know I would need to keep them. So indeed, ‘trust me bro’ is all I have for that. I can only hope I come across as someone who does care about the veracity of data enough for that to be worth slightly more than usual, hah.

For the graphing period, the lowest you can set in RTSS is 100ms, which I have it set to. It is my understanding that this represents the highest value seen during that time window, but I do not know for certain if the measurement window itself is every single frame. I would guess that it is though, as RTSS also is commonly used and complimented as a more consistent and exact framerate limiter than even the one built into the Nvidia control panel.

As far as benchmarking in a stable environment like standing still in the garrison, yes that is useful of course for a baseline of ensuring that the stutters are -not- present in such a place, which they are not for me.

The stutters are definitely tied to asset loading in some way so the best place -to- measure them I find is mounting up and doing laps in a busy instance of Oribos. It is of course non-repeatable testing with all the random variables of other players involved, so the best that can be done is to compare average stutter frametime spikes to how they were before the patch.

I almost always have rtss graphs going on the second monitor when I’m gaming for wow or otherwise, so luckily I am well aware of the typical spikes I would get in Oribos/Org before the patch. They range up to 4x that long now after the patch… probably not any more -common- than the 20ms spikes were before the patch, but much more significant when they do occur.

1 Like

Its not fixed sadly, just logged rn and it appears to run a bit better at least.
But im still having micro stuttering and frames dropping that didnt happen before the patch.

1 Like

That’s great, I’m glad to hear you aren’t having issues anymore… but can you please stop dismissing everyone else’s experience? It’s not helpful.

11 Likes