Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.

Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Topic on User talk:Aemony

This page shows the changes between two versions of a post by Aemony in the topic "Keeping Timer Resolution" on User talk:Aemony. You can see other versions of this post at its history page.
Line 1: Line 1:
 
That "more information" note is only there to mention the fact that other applications '''might''' already be setting a higher timer resolution already, which will remain in effect until either those processes are terminated, or they request another timer resolution by making a follow-up call.
 
That "more information" note is only there to mention the fact that other applications '''might''' already be setting a higher timer resolution already, which will remain in effect until either those processes are terminated, or they request another timer resolution by making a follow-up call.
  
−
TimerTool itself only sets the requested resolution when clicking on "Set Timer" and then assumes the timer is set as requested until its process is terminated, since Windows uses the lowest value (that is, highest resolution) requested by any process.
+
TimerTool itself only sets the requested resolution when clicking on "Set Timer" and then assumes the timer is set as requested until its process is terminated, since Windows uses the lowest value (that is, highest resolution) requested by any process until said process is terminated (or the process requests the resolution unset or lowered).
  
 
Basically, that note is meant to highlight the fact that other applications can also requests various timer resolutions, and it is up for each user interested in knowing more to generate a power efficiency diagnostics report and determining whether another process is already setting a higher resolution or not.
 
Basically, that note is meant to highlight the fact that other applications can also requests various timer resolutions, and it is up for each user interested in knowing more to generate a power efficiency diagnostics report and determining whether another process is already setting a higher resolution or not.
  
 
For me, personally, I have no use of that tool since both Discord and Steam (as well as my sound card) requests a 1ms resolution constantly, which keeps the timer resolution on my system set at 1ms forever. I imagine in the case of Discord and Steam it might be their use of CEF (Chromium Embedded Frameworks) since [https://www.belshe.com/2010/06/04/chrome-cranking-up-the-clock/ Chromium used to love] to set the timer resolution to 1 ms and forget it.
 
For me, personally, I have no use of that tool since both Discord and Steam (as well as my sound card) requests a 1ms resolution constantly, which keeps the timer resolution on my system set at 1ms forever. I imagine in the case of Discord and Steam it might be their use of CEF (Chromium Embedded Frameworks) since [https://www.belshe.com/2010/06/04/chrome-cranking-up-the-clock/ Chromium used to love] to set the timer resolution to 1 ms and forget it.