Unsure if GPU drivers, the rework, if it’s a bug or just a symptom, but whenever I eyebeam more than 1 target my framerate drops by ~10%, and it scales with more targets. I was doing the Superbloom event and I hit like 7 enemies with eyebeam and it dropped from ~70 FPS to around ~10, jumping back up the MOMENT eyebeam finished.
Was not an issue before 10.2, CPU is a 5800 X3D, GPU is a 3070 ti
Can confirm, happening for me too since 10.2
This happened on my DH as well.
Yep, can relate. I thought it was time to upgrade my device but I had hope to find more gamers with the same issue.
I’m running MacOs with a AMD card, so it seems to me it is not drivers related.
You’re not alone. I also use a 3070 card. Are you using the latest Nvidia driver 546.01? If so, I think it may be the driver.
I’m having a lot of stuttering issues with WoW ever since updating the drivers. Even turning the settings all the way as low they go do not help. My game still stutters and the graphics are extremely choppy.
Exact same issue. No problems whatsoever before 10.2 then after 10.2 launched, complete lagfest when using eyebeam.
Having the same exact issue using my 3060. Using Eye Beam just drops a massive frame drop. Never had this problem until the latest patch came out.
4080 on driver 546.01, same issue with Eyebeam. Drop from ~130 FPS to low 20’s at 3440x1440.
Confirming here too. Same shieet lmao. Even on target dummies in Valdrakken.
144 FPS to a complete lockup while Eye Beam is casting on multiple targets.
RX 5700 XT
Yeah, it’s really bad, as low as 3 targets will drop fps.
You guys might want to try clearing the shader caches out. Nvidia moved the locations in the last driver and it’s possible the game is getting confused with a stale shader or something.
The old location was in %localappdata%\NVIDIA\ and now it’s in %localappdata%low\NVIDIA\PerDriverVersion\
You can copy those, press start+r, paste them and it should take you right to the directories you need. Close out of the game completely and delete any folders in those that say cache
There’s also the %localAppData%\D3DSCache folder as well, you can clear everything out in there.
I just tested eyebeam out on my DH and it made absolutely no difference in my FPS while AoEing, so it sounds like you guys have a broken shader or something. Try clearing all three of those out and test again. You might get a prompt about files being in use, but that’s okay, just tell it to skip those files (windows DWM is using them), but it will delete anything game related.
Same here. Also when I use Immolation Aura with 2+ enemies nearby. It’s so terrible.
I haven’t had any issues on training dummies or in the open world. But the very first key I did, I dropped to 0-5 fps for a couple seconds while eye beam was channeling on the first pack. Once the channel was done it slowly resumed back to normal (100+fps).
Seems a common complaint among DHs. Restarting the game apparently temporarily fixes/alleviates a lot of the stutter/lag.
I’m curious if this is when the combat log engages? I know they changed how combat logging works this season. bugsack/bug grabber didnt produce any errors at all.
I have the same problem with Eye beam. Feels heavy related to the patch.
Anyone found any fixes or seen if bliz is going to do anything about it?
Every problem with Blizzard games is on the users end right? Get real.
Would you like me to waste some time posting clips of it then?
No thanks mate. Because every single problem posted on the forums, you don’t experience any of them. I guess the rest of us are imagining things, and WoW is bug free and fully optimized.
No, you’re just over reacting about it… The fact that only SOME people are experiencing the problem is indiciative that SOMEthing is being shared between those having the problem. The fact that it’s only happening for you guys with a very specific spell means it’s likely one of two things in this case: Drivers or addons.
A broken shader can easily lead to a massive frame rate drop, until it’s no longer being drawn. Nvidia recently changed their shader*(don’t know why the hell I typed addon) folder structures, so it’s very reasonable to assume it might factor into the problem.
A broken addon can easily lead to a massive frame drop if it’s no longer up to date or if something on the LUA backend changed. I’ve demoed before that two lines of bad LUA addon code can hitch 1000 dollar GPUs down to seconds per frame.
So rather than intentionally being difficult, start posting things like DXDIAGs and logs…