It looks like there’s several options for low latency mode. Did you just disable entirely or choose another setting?
I believe I set that low latency menu entry to Disabled. I’ll check everything and post tomorrow when I get on my PC
We just want to know something is being done and its being looked into.
Maybe Twitter is a better way to get some sort of acknowledgement?
Yeah “Low Latency Mode” is DISABLED. I played for several hours, three characters, world content and delves. No issues so far.
1 Like
Yep, I know what everyone is asking for, but I feel like I already explained why that’s unlikely.
After switching to DX11, I’ve never had the problem again
1 Like
I’m going to try turning this off and playing for a few hours later tonight and tomorrow to see if it works. I actually came here for a completely different issue but I’m having this one too, so I’ll try it out and report back. If after a whole day it doesn’t happen I’ll chalk it up to that setting being the cause. I’m on current Nvidia drivers so if this doesn’t work I’ll go back to older drivers and test that out instead.
2 Likes
Please start populating this post on the actual Bug forms, so Dev/QA can see the problem.
They do not look at the Technical Support channel.
3 Likes
Same issue here. It doesn’t stop at just opening transmogs. Happens occasionally after hitting lust, and everything freezes for about 5-10 seconds. Or sometimes if a boss is about to do a special ability, or even in a trash pack, for example, right before Thrash goes off on one of the shards in HoA. Tons of situations that it sometimes might happen, much of the time it doesn’t, but it is at least once or twice per key.
Game breaking.
Everything is up to date including graphics drivers, use minimal addons (no weakauras), never have anything going on in the background, etc. I have ZERO issues playing any other games. GW2 plays just fine at ultra, BG3, all sorts without any problems. Played D4 for awhile also and that was fine.
Happening for a long time now, only in wow, and no matter how I tweak with the graphics settings nothing fixes it.
Edit: Last night the game locked up so frequently I couldn’t play at all, but today the game ran flawlessly.
Completely random.
On an NVIDIA RTX 4060 with 16gb of ram.
4 Likes
So no dev will ever see this and the 20 other forum threads on the same issue? Nothing will ever be acknowledged or done about it? Tell me now MvP so I can unsub.
2 Likes
Whoa! I thought it was my driver failing! Same thing happenign to me when I open collections.
4 Likes
I disabled low latency mode a few days ago and have not had the mog screen freeze/reload since.
1 Like
Aaaaaaand it looks like they disabled RT shadows again.
2 Likes
Just chiming in here to say disabling Low Latency has worked for me so far. I’ve been able to play for several hours with no driver crashes or other serious hitches.
I just checked and it’s still enabled for me. Are you running in DirectX 11 mode? Because RT Shadows are a DX12-only thing.
1 Like
The thing I heard is that they left the option for RT shadows in the configuration UI but disabled it in the graphics engine, disregarding the setting.
1 Like
I found this obscure post: apparently it dates back to a windows vista change and involves the way it swaps and overlays. Be warned it is a regedit change.
ht ps://www.reddit.com/r/Windows11/comments/1kgp7ar/cause_and_solution_to_windows_24h2_related/?share_id=tGw9xj2IOL9mSKnDRHFkE&utm_medium=ios_app&utm_name=ioscss&utm_source=share&utm_term=1
1 Like
No, I’m on DX12 and even verified with an overlay that reports the API being used. The RT option can be changed and isn’t grayed out or anything, it just doesn’t do anything right now. Which means the internal codepath is disabled or bypassed.
Yeah it was like that for months, but then somewhat recently, they re-enabled it again. But it looks like they disabled it yet again this week.
1 Like
Adding to this thread. I had this issue pop up for the first time tonight right as someone did a ready check and was pulling King Salhadaar. I finished out the fight, logged out and updated my drivers (My previous drivers are from 2024, 566.36) and was happy to see my FPS were improved but THEN I had the same re-render crash happen when using my transmog screen.
I’ve never had this happen before.
Looking over the thread, here’s a couple of the settings I have that were listed and still ran into this:
- Ray traced shadows disabled
- DX12 enabled
- Compatibility settings all checked
- NVIDIA overlay wasn’t on to start with
No clue what could be causing this, but I did a scan/repair of the game and when I went back in I summoned my transmog NPC and purposely opened and closed the window to see if I could force it to happen again, no dice.
If it matters the time gap between my first re-render bug in the raid and the transmog was almost exactly 4 hours.
AND when it happened, my youtube screen on my other monitor continued to run as if nothing happened when this crash bug occurs.
4 Likes
Try switching back to DX11, I know it will drop your FPS but some had better success, as also rolling back the drivers to 572.6 from February after a DDU install.
Ray tracing was disabled by the wow team recently after Nvidia reported it was fixed in a more recent driver, but the issue recurred.
Also turn off option gpu features.
1 Like
I probably will try DX11 if it gets any worse, I’m just surprised it popped up now and I’ve been playing regularly since late season 1 and then bam it happens twice in 4 hours lol.
I’m relieved that I found the issue on the forums though, it’s nice to narrow down that it’s likely a software issue at the very least.
3 Likes