Can someone please explain “use GlobalTimerResolutionRequests”?
-
- Posts: 2
- Joined: Sun Dec 01, 2024 1:29 pm
Can someone please explain “use GlobalTimerResolutionRequests”?
Title. Is it worth using? What exactly does it do? Should I enable it for gaming on win 11?
- Wagnard
- Site Admin
- Posts: 1759
- Joined: Sat Jul 04, 2015 5:18 pm
- Location: 127.0.0.1
- Contact:
Re: Can someone please explain “use GlobalTimerResolutionRequests”?
The behavior of the timer resolution on Windows changed with the release of Windows 10 v2004 to be per-process instead of system-wide as previously. This resulted in processes not setting a specific timer resolution on their own falls back to using the default timer resolution of 15.625ms (64 Hz) which can have various effects in games which were developed with the mistaken assumption of the timer resolution being much higher. An example of a common issue of a game using the default timer resolution is an unexpected 64 FPS cap/limit.
Windows 11 received the ability to restore the previous behavior through a registry value, *the option you mentioned*. As far as I am aware this option is not available on Windows 10.
So technically in windows 11 there is no point forcing a timer resolution with ISLC if you do not tick that option too.
-
- Posts: 2
- Joined: Sun Dec 01, 2024 1:29 pm
Re: Can someone please explain “use GlobalTimerResolutionRequests”?
Thank you for the reply! I already had a reg edit command in place for global timers, I did not realize this setting just enables it for you thats pretty cool! Anyway thank you for the insight. Just wanted to make sure I wasn’t missing out
-
- Posts: 1
- Joined: Sun Dec 29, 2024 10:41 pm
Re: Can someone please explain “use GlobalTimerResolutionRequests”?
The benefit to this is minimal unless you have specific issues with older games. Everything is fine so I have no good reason to enable this just for gaming. Thanks for listening
- Wagnard
- Site Admin
- Posts: 1759
- Joined: Sat Jul 04, 2015 5:18 pm
- Location: 127.0.0.1
- Contact:
Re: Can someone please explain “use GlobalTimerResolutionRequests”?
The behavior of the timer resolution on Windows changed with the release of Windows 10 v2004 to be per-process instead of system-wide as previously. This resulted in processes not setting a specific timer resolution on their own falls back to using the default timer resolution of 15.625ms (64 Hz) which can have various effects in games which were developed with the mistaken assumption of the timer resolution being much higher. An example of a common issue of a game using the default timer resolution is an unexpected 64 FPS cap/limit.
Source: https://community.pcgamingwiki.com/file ... indows-11/
Source: https://community.pcgamingwiki.com/file ... indows-11/