So the first 1.37.0.1 patch I had no issues with. The update/fix on 7/2/2019 is when all the problems happened. For this post I’ll be using stats from training range as in-game stats vary a lot.
My setup: i7, 1070, ssd install. Custom settings low everything, medium shadows, 100% render scale, 1920x1080x240fps, 300fps frame limit, reduce buffering, everything else off or to the lowest it’ll go.
Previous patches: 300fps+ in training range wouldn’t even see dips below
Current(1.37.0.1 7/2/2019): 180fps avg
Right away. how? Like the patch was a few hundred mg which is a lot more than it should take to fix a baptiste bug, obviously there was something that happened in the background but okay.
Steps I have taken to fix/improve the problem.
Step 1: Update drivers. 10 fps I knew I was running some pretty old stuff back from when I first got my card, maybe 2 years old now. I saw a small improvement on average but nothing interesting.
Step 2: Scan and repair. Nothing installed on my ssd I figured it was worth a few minutes.
Step 3: Reduce buffer setting off and on again. 30 fps Huge improvements for a short while. This has been a thing in OW for a long time and you’ll see streamers do it all the time to “flush” the game.
Step 4: Playing around with video settings. Render scale from 100% to 50% saw a small improvement of 10 fps but is not worth it IMO. Epic to low settings had a huge impact of 100 fps but already playing on low/custom settings there was no fps gains to be had here only losses. Vsync, well I don’t play with vsync on for obvious reasons of a 240 monitor but turning it on and then off again netted me a gain of 10 fps? maybe it was something similar to the reduce buffer “flush”?
Step 5: Realtime CPU priority. 10 fps
Step 6: Disable anything I could in the background. I don’t have any razer, hyperx or logitech apps in the background(programs with known issues) but I thought I’d do what I can and didn’t see any notable gain.
Step 7: CPUID. After looking through the forums I’d seen plenty of dxdiag and msconfig files with nothing obvious cause problems and the common recommended next step was CPUID. I booted it up and ran OW. CPU#2 was being used 0-9% while all other cores were being used 15-45%. Close game and restart, how it’s CPU#4 being used 0-9%, now it’s CPU#6. This repeats everytime the game is completely closed and opened again, CPU#2\4\6.
Obviously I have no idea how OW programs it’s multi-threading and I’ve also not used CPUID before but I’d like to note down a lot of small adjustments that have improved the situation for me to others as well as possibly give some useful feedback to devs.
CPUID export:
pastebin Ahe5Bgwc
