PC SPECS:
Intel Core i5 8400
ASUS Z370-I
2x 8GB Kingston Fury 2666 MHz
ASUS AMD Radeon RX 6600
700W EVGA PSU
1TB Kingston M.2 SSD
BASE:
I’ve played Overwatch 2 on High Setting since it was released and had no Issues overshooting the 75 FPS mark. CPU usage was usually in the fifties, since I mostly had Discord+Browsers open on my second Monitor. I always had the FPS uncapped so - as expected - the GPU capped out at 98%.
ISSUE:
Since I’ve updated to the newest Version of Overwatch 2 my CPU and RAM start acting wierd when launching Overwatch. When normally CPU usage was around 20-30% in menus it is now capped out at 100%. I also noticed the RAM incrementally filling up until it reaches about 10-11GB of system-usage. 6GB of that being overwatch. Note, that i have not launched a Match yet.
When joining matches it doesn’t make a difference which graphics-settings I choose, since even on the LOW-preset and manually setting everything to the lowest thing possible doesn’t make a difference in performance.
CPU at 100%, RAM slowly filling up, GPU at 30-50% on all presets. The complete opposite of what is expected.
TROUBLESHOOTING:
I’ve already reinstalled overwatch and individually benchmarked CPU with Cinebench, GPU with FurMark and 3DMark and the RAM with PassMark and everything was as expected. As previously stated changing the in-game graphics settings doesn’t change the performance.
Then, the unthinkable happened: While I let an Overwatch benchmark-loop running in the Workshop the performance normalized. RAM stopped filling up, CPU was at a constant 50% and GPU at 60%, while displaying a constant 75 FPS without stutters. Note that this took about 20 Minutes of running the loop and I didn’t yet have time to replicate this behavior again.
Does anybody else have a similar issue, or perhaps even a fix?
Kind regards, (first-time-poster) Jon
Takes at least a solid minute, up to 5, after launching the game for performance to be normal. Have a hunch it has something to do with shader caching (clearing shader cache makes the issue MUCH worse)
Game is unplayable until ~6.5GB Ram is allocated. After all that ram is used it runs perfectly fine.
I have since done some testing and it now also takes about 5-6 Minutes. After that Overwatch hovers at around 6,5 GB RAM and I can comfortably play on 100 FPS Ultra Settings. It only happens in Overwatch, so there’s gotta be a technical issue.
Guess I’ll just wait for my friends to finish the first game before I can join
Sounds like shaders are compiling each time you launch the game, which is not normal behaviour as shaders should only compile after a game update or possibly GPU driver update.
I used the --tank_WorkerThreadCount x command line option in the game options in the Blizzard Launcher to limit the game to x threads where x is the number of your physical cores NOT logical cores.
I then Reset Shader Cache in AMD Software: Adrenaline Edition.
After that my shaders compiled correctly and compilation shader stutters during gameplay went away.
Some anti-virus/anti-malware programs also seem to be stopping or delaying the game from launching after the 7th of March update, maybe these programs are also causing issues with shader compilation.
Before that the game was unplayable on a Ryzen 5 3600 + RX 6600.
Thx for the help, this actually fixed the problem!
Though I don’t know if it was clearing the shader cache or inputting the command, all wierd behaviour vanished after 3 game restarts.
Sincerely Jon
