After the update i have extremely low fps (amd rx 6800) , like 10-20 max
3 Likes
I don’t have that problem so it doesn’t exists. Skill issue, git gud, mad because bad… (Sorry I just felt obligated to behave like clowns 
) Sorry for your bad experience bud. I hope you can find a solution soon
2 Likes
Just had something similar, played 7 matches (April Fool’s mode) and the game worked fine except for 1 Suravasa match where I had to fill for a leaver.
Mid-way through the match my FPS suddenly tanked from the usual 165 down to at first 70-something, then 60, 50, 40, 30… until I was eventually playing at 10-20 FPS when any visual effect was on screen. Some guy in chat asked if anyone else had low FPS so I wasn’t the only one to experience it.
My GPU was at around 57°C during this, whereas usually it hovers around 75°C, so for some reason it wasn’t being utilized properly. The framerate went back to normal once the match was over. Next match was fine.
Playing on Windows 10 using an RX 6700 XT.
4 Likes
Maybe it’s an AMD problem (and we both have Rx6000 series). Now the fps get better but after enough time (like after 20 minutes)
When the update gone live?
1 Like
This is somewhat common if you updated your gpu driver or the game inserted some kind of graphical improvement. Depending on the platform the shaders are loaded inside of the game or outside of it.
You’re playing through dx11 or dx12? Steam or bnet? What OS?
1 Like
Are your GPU drivers the latest version?
Yeah this sounds more like shader compilation or something. If after some time your performance gets better and stabilizes it could be that.
What I’m talking about was just completely random. Happened after a handful of games. Then went back to normal.
1 Like
You play through bnet or steam? Bnet usually had some issues tied to audio that could sometimes tank the performance or simply go mute.
While could be some randomness from windows itself, due several w11 features going towards w10 too.
Is not unlikely they(blizzard) making something bad on their own code, their testing methodology aren’t that great anyways. It appears that your gpu either enters on lower power state which is pretty common on rx 6000 series or the game itself having some kind of leak or hang in specific routines. Which they had several situations of this in the past.
1 Like
Seeing the same thing
2 Likes
Playing through Steam, DX11, latest drivers, Windows 10.
1 Like
Can inform the hardware (cpu, gpu, ram, storage), driver version and os version?
1 Like
Usually amd gpus perform better at dx12. I would give a try. Even if is experimental.
1 Like
5800X3D, RX 6700 XT, 32GB DDR4 @ 3200MHz, WD SN770 1 TB
Driver Version 25.3.1, Windows 10
1 Like
Yeah I gotta test that for sure, just posting here to document this weird thing that happened, let other people know.
1 Like
if they have a dependency that their game now needs to run, they should address it and tell players what those are.
I am sure everyone else is running newer drivers than I am.
Talking with other players that are running the newest drivers on their pc. They are getting full-on crashes. vs just frame drops.
Nvidia RTX 2060 Founders edition
Windows 10 operating system (im hearing people that run 11 are having way worse of a time online with this than 10 users)
Corsair 64GB of RAM
AMD Ryzen 5 7600 6-Core Processor 3.80 GHz
Those on AMD and lastest graphics driver.
Try no dynamic scale, set fixed something like 85-105, no fsr, try to fix 120fps and dx12. If no problems happens set fps towards your monitor capabilities.
If you didn’t previously. Try it out. Due amd made changes on hypr-rx and dynamic scale can have weird behaviors.
Usually newer drivers for older gpus can have issues when using relatively new tech.
That’s the thing, they usually do a poor job on it. Most likely would take awhile for them to find it. Could be tied to the event or something else. Pretty much all 2025 drivers from nvidia have problems accross several products, usually on 30,40,50 series. I wouldn’t doubt that 20 series also would be affected.
In your case if you’re on 572.83 try to revert to 566.36. Due nvidia recent drivers had several stability problems across several families like rx 30, 40 and 50’s.
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/560098/geforce-grd-57283-feedback-thread-released-31825/
Proper steps to downgrade the driver requires DDU.
2 Likes
I’m already using a fixed scale, set to 100, no FSR, capped at 157 FPS. Not sure what capping at 120 will do; I am going to try DX12 though.
Thank you for taking the time to help out.
1 Like
The same tip about scalling tech could be useful too.
Disabling dlss/fsr and setting a fixed resolution if is in dynamic.
Folks usually do stuff differently, but only slightly.
Usually I suggest capping at 120 due most cpus and gpus can deliver somewhat consistently at 120fps.
But was more akin to avoid dynamic scaling stuff and 120 fps being a reasonable value towards the SIM stat on the game. Is not a problem running above, was more tied to folks that could have overheating problem to “softly” avoid it.
If you were aready capped the fps, the scale was fixed, the fsr disabled. The only thing would be dx12 or consider revert towards a bit older driver.
Due windows usually updates itself at annoying rate and revert it is burdensome. If all those steps doesn’t fix it, most likely your end is fine and the problem lies on their game.
Because both you and dasaries have enough ram for the game with a fair margin.
2 Likes
It’s not usually about there being a new dependency, but just that there is some intersection of a bunch of things that just happened to break due to the way a change is made. There could be an assumption by the developers that a particular sequence of graphics operations should work, but maybe AMD driver abc.xy has a bug or race condition where this introduces a regression. No reasonable developer is going to try every change they make on every piece of hardware and every driver version for the past 5 years to ensure there isn’t some weird corner case when something is expected to work.
Sometimes there are also conflicts with other software. Antivirus, for example, is notorious for interfering with things. It could be something like an interaction with AMD’s drivers loading files from a shader cache, causing the AV filter driver to do a scan because suddenly it doesnt recognize the files.
There’s a lot of different reasons things can break that should be expected to work fine.
4 Likes