Rem0o
Dropped frames whilst in SteamVR.
I noticed within the last 3 updates I'd see consistant purple spikes (dropped frames) in my frame times. After a week of testing I finally nailed it down to fan control being the issue as after closing i stop having dropped frames. I'm uncertain of what to look for to help narrow down the exact cause of the issue. Let me know what to look for if anything.
Here is my fan control setup just incase;
What GPU source are you using? NVAPIWrapper or the "GPU" from Libre?
Also, it seems like none of your control work properly as they all have a question mark. Either your calibrations are way off, or somethig else is taking over your fans.
NVAPIWrapper
Also, the calibration doesn't matter as previous calibrations that I had done manually still had the same issue (I had recently redone them to see if that was the case changed nothing)
Also another note I have no other software installed that would affect my fans I don't have Nivida g-force experience And I don't run MSI afterburner (it doesn't automatically open with windows) until I boot up VR so it can take over my GPU fans If anything It would be the motherboard. But again This only happened after a recent update of fan control and the only software that I had recently installed would be a Monitor control software called "Display widget" to of which during my testing uninstalling made no difference.
I guess the only variable left would be when I switched from portable to a full install but even then it didn't happen until a recent update as it was fine 1 or 2 versions ago. And the dropped frame that I mentioned are on the GPU
Please let me know if there is anything else to look for I can test I would love to use fan control again!
You could try and isolate which sensor source cause the frame drop. Check the one you one at a time.
Yes! I will do so it will take some time however as the only way for me to test this is to sit in wait for a purple frame time.
As the time it takes for one to appear is quite awhile (every 8-15 minutes) Reason I'm so bothered tho is bc it's quite jarring when you have perfect FPS then all of a sudden it's just a freeze.
If there is any other methods to try first that wouldn't take me hours to test that would be great as this will take quite awhile.
After much testing. I think just having the program open in general causes the issue.
I can have all controls disabled and the issue will still occur. Albeit with less consistency.
It seems that the less controls I have enabled the less often the frame drop occurs. just disabling both my 4060 fans has a substantial impact on the frequency of the frame drops.
Although just disabling both my graphics cards the issue does not go away.
The really interesting test is to disable the sensor source all together in the settings. Disabling the control still has all the monitoring enabled in the background.
Does it occur with the window opened or closed? Fancontrol still runs with the window closed.
Then I'm kinda lost. With every sensor source disabled and in the tray, you got no UI, and no sensor polling at all. The app does basically nothing.
Well that's where I'm at. I'm closing it in task manager makes the lag spikes go away. Sorry about this.
With closed sources, it's really hard to see. But I second what @candygamer-YT is experiencing, and its not just in VR. In CS2 its very noticeable.
If you go back a few versions does it still occurs? Identifying which version started it would help.
it seems to start around 212-215
Can't really tell but 210 seems to be more stable than the others. All versions of NET 8 have a lag spike but on versions 212 and up it's much worse All versions of NET 4.8 don't have any lag spikes on versions 210 and below but begin to have lag spikes on 212 and up
I never had this issue with the portable version! it's really odd
I'll see if the same issue exists with portable.
But it seems I'll be using NET 4.8 from now on for fan control.
After awhile of using 210 seems 100% stable no spikes Hopefully we can figure this out! @jepperc you think you can try 210 as well? maybe try different net versions with 210?
Interesting. v211 introduced the memory optimization when closing the UI window.
Could SetProcessWorkingSetSize be the source? I`ve been seeing some spikes too, just did not had time to troubleshoot them yet.
That's an interesting theory. Technically, if the app starts with your user logon and you don't touch it (you don't close the window), SetProcessWorkingSetSize() never gets called.