As the title says, I am getting huge FPS drop in some games.
Currently, I'm having issues in:
What's happening is, when I'm not moving my mouse, that the FPS is super consistent (280~300 in Apex Legends, 150~160 in Marauders, 140~150 in 7DtD). But when I move my mouse... it goes crazy. In Apex, it goes almost below 40, in Marauders below 60, and in 7DtD below 20 even though I'm just wondering in forest(when it's horde, it can go below 10).
Weird thing is, if I hold LMB or RMB, the game does not stutter. So it's not completely unplayable, it just forces me to ADS or shoot the weapons (so fighting is not so much of a problem for me, only looting is).
By the way, using the controller doesn't seems to trigger the issue. I can play the games fine with it, so I think PC specs are irrelevant.
Of course I researched what could be the reason, and I found a fellow friend that's experiencing the same thing (at least in Apex): Apex stutter lags when I move my mouse(reddit post).
I am having almost the exact same issue as the on mentioned in this post, and there people suggest lowering the mouse's polling rate to 500 or 250. I was on 1000 so I tried it. That seemed to fix the issue, but it was only temporal - the issue rose again after around 30 minutes.
I'm still searching for a fix, but every post that's having the same issue seems to be fixed by dropping their polling rate. Good for them, but it's not working for me.
I suspected that the culprit was Google Play Games, since the problem just happened right after I'd installed it. So I uninstalled it, and disabled Hyper-V (because Google Play Games needed it), but the issue still consists. I thought there might be some leftover files, so I've gone and completely wiped... formatted my C drive and re-installed Windows. It seems to have fixed the issue. Oh wait, no, it hasn't - the problem rose again in 1 hour.
At this point I'm completely lost. I seem to be stuck here, since even wiping the drive is not fixing the issue.
My PC's specs are:
- Windows 11 Professional
- Intel Core i7 12700KF (is not overclocked)
- nVidia RTX 3070 (more specifically, MSI's Gaming X Trio. Using the newest driver as of today, so 531.79)
- 32GB of DDR5-5200, made by crucial
- three M.2 drive (one 500GB drive for OS and some applications like browser, steam, etc(Crucial P2), two 2TB drive for data and games(both Solidigm P41Plus))
- Steelseries Apex Pro TKL 2023
- Steelseries Apex Pro (to test if TKL 2023 is causing the issue; no changes)
- Steelseries Apex M750 (same as above; no changes)
- Steelseries Prime+
- Steelseries Sensei Ten (to test if Prime+ is causing the issue; no changes)
- Steelseries Sensei 310 (same as above; no changes)
- and some other keyboards and mices that I don't know the name and manufacturer; no changes
- Xbox One's controller (usually not plugged in, just checked if the problem would occur with it)
- ASUS PG259QN (360hz monitor)
- BenQ Zowie XL2430T (144hz monitor, to test if PG259QN is causing the issue; no changes)
I don't use any software while playing games besides Discord (to talk with my friends) and nVidia's Share (to record the game and see FPS), and sometimes a web browser (Vivaldi).
Yes, I have tried it without them running (except nVidia's Share, as I needed to check the raw FPS value), but it didn't change the situation.
Everything on my computer is up to date including my Motherboard's (MSI MPG Z690 Force Wifi) BIOS.
Any suggestions and answers are welcome (of course, that is as long as it's not "set your polling rate to 500 or below", "re-install your OS or game or anything", or "update/upgrade your PC").
If you need more info, I'll provide it.
To answer @Vilx-'s question (changing settings such as fullscreen/windowed and such would fix or do anything to the problem?) :
Sadly, no. I've tried exclusive fullscreen and borderless/windowed in every game, but no changes. I've also changed graphics settings (texture, shadow, effect detail, v-sync, etc etc...), but no avail. Changing settings from nVidia's control panel also wouldn't do anything. Capping framerate to 300, 240, 144, 120, or even 60, didn't fix the problem.