A complementary tool for ISLC

[Parisien_entraide]

The only downside of this is that if a game like Diablo 4 or Marvel Rivals (Or any other game) that request a timer resolution of 0.5, it will override the one you specified because Windows will always honor the lowest requested value first.

I dont konw for my principal game : Battlefield 6

Is in relation with that ?

2026-04-06_192254.jpg

[Wagnard]

The only downside of this is that if a game like Diablo 4 or Marvel Rivals (Or any other game) that request a timer resolution of 0.5, it will override the one you specified because Windows will always honor the lowest requested value first.

I dont konw for my principal game : Battlefield 6

Is in relation with that ?


2026-04-06_192254.jpg

Anything modern is probably already applying this to its own process.

[Parisien_entraide]

Anything modern is probably already applying this to its own process.

I thought it was 1ms... But I was wrong actually

[Parisien_entraide]

New version

https://forums.blurbusters.com/viewtopic.php?t=15427

Direct Download https://forums.blurbusters.com/download ... hp?id=6914

[Parisien_entraide]

New version (another)


Direct download https://forums.blurbusters.com/download ... hp?id=6930


-----------------
Another Update:

Code: Select all

-Added ability to turn off/on GlobalTimerResolutionRequests, and it will also read it's state.
-Added elevation detection for the tool. You need to be admin level to change GlobalTimerResolutionRequests. It also requires a restart if changed.
-Added additional deviation methods, raw/trimmed/winsor, so outliers don't skew your deviation results.
-Coupled the Sample amount to the benchmarking tool. If it's at 100, your benchmark will take test for 100 samples each. If it's at 500, your benchmark will test at 500 samples each.
-Cleaned up the interface a bit.
Made Focused mode default during startup.
-Cleaned up the jitter graph. The tighter the inside wiskers are the more stable your timer is. The red outside wiskers just represent the max/min outliers. So they'll always be big.

And

Final Update:

Code: Select all

-Added Power Plan switching with [k]
-Reduced the overhead even more by removing things from the main loop
-Added an about/help page
-Added a section for custom startup/benchmark settings in the batch file
-Fixed the buckets, still had bad mappings in the higher numbers

That's it. I think it's pretty polished now.

Reminder for people who don't understand the purpose of the tool. It doesn't fix your latency issues. It's a tool to help you visualize the problem if you do have latency issues. You can use it to test if the solutions you tried work or not. After you've solved your latency issues, you can improve your latency even further by setting your global system timer to 0.500ms with the app. Allowing for a better response time from your cpu/kernel.



Video : https://imgur.com/a/UyDrOCP

The top app you see is my first iteration of this tool. It does not hold a timer request. It only probes the kernel and measures how fast it responds. So it's not connected in any way to the second app. Watch it's measurements when I start up my updated timer bench tool. The measurements get better right away. The first app represents your game. The the tighter the measurements the faster the response time.

Then throughout the video, in the updated tool, I will cycle the "[T]imer Res." from windows defaults "10000us" to "5001us". You can see it's relationship to the kernel and the timer resolution and the other app and how it can positively impact your game.

Be mindful of the sample rate, use only 1000ms - 250ms only when gaming. Any lower than that adds overhead to your kernel. Use only lower values if youre benchmarking or stress testing things. The sample quantity doesn't matter, 500 means more data to smoothing out the numbers and the histogram. 100 gives you better view of what's currently going on and will jump around a lot. Make sure you have GlobalTimerResolutionRequests set to on if you're on windows 11. High Performance power plan, and in focused mode, which is it's default state now.