FSO causing result inconsistencies #367
Description
This is a copy of my comment in the closed issue linked below that this is related to, I am opening new issue to make sure this gets the attention, as I have found the cause of the issue.
Closed issue: #363
Copy:
Hey guys, I am currently still migrating between fresh windows installs, so I had some opportunities to test out different settings and I figured out the reason that causes the inconsistencies in the results. Anyway, on my last windows install, 1.7.8 was working great, today I reinstalled win once more and it is showing fake ms spikes once again, so I started testing different factors, as it did not make sense, and what it came down to was a registry command which controls “FSO and Game Bar” as part of the AtlasOS toolkit. When FSO/GameBar are disabled, the spikes and inconsistencies appear on the captures, and when I enable FSO/GameBar, everything works perfectly as it should. I should mention that I record FPS Benchmarks in CS2, which I always have in Fullscreen Exclusive. I also normally disable FSO as it worsens the 1% from what I see in my games. I believe this was the original reason for the issues I experienced in 1.7.7, and now had in 1.7.8. I hope this information gives you some insights and helps to resolve the issues for future versions. Keep up the grind!
P.S. Link to the setting code
https://github.com/Atlas-OS/atlas-toolbox/blob/main/AtlasToolbox/Services/ConfigurationServices/FsoAndGameBarConfigurationService.cs