The timer resolution(or tick) for Multimedia has improved in Windows 10 TH2

[BenYeeHua]

Yup, it is much more better, for now, it is 0.500 milliseconds as default(1.001 millisecond when it is build 10240), and only apply when the thread is running and needed.
(Performance and powersave! )

It is also because when I am running War Thunder, it will not set any Timer resolution in the Hanger, and thank for that, I found that it is dynamic apply in TH2 now.
I also tried Planetside 2, and it is also having the same behave, just it will jump back to 1 milliseconds as the game required it...

This is also the same for Adobe Flash Player(NPAPI) and MPC-HC(it will keep as 0.500, as MadVR is keep running while pausing...), unless you are running Edge or IE, which always running 15.6 milliseconds for better power save.

But it has a issues, you can't see it when you has run powercfg /energy, it will not showing any game/multimedia running and set 0.500 milliseconds timer resolution for them, and the current timer resolution is showing as 15.6 milliseconds.

[edkiefer]

Yup, it is much more better, for now, it is 0.500 milliseconds as default(1.001 millisecond when it is build 10240), and only apply when the thread is running and needed.
(Performance and powersave! )

It is also because when I am running War Thunder, it will not set any Timer resolution in the Hanger, and thank for that, I found that it is dynamic apply in TH2 now.
I also tried Planetside 2, and it is also having the same behave, just it will jump back to 1 milliseconds as the game required it...

This is also the same for Adobe Flash Player(NPAPI) and MPC-HC(it will keep as 0.500, as MadVR is keep running while pausing...), unless you are running Edge or IE, which always running 15.6 milliseconds for better power save.

But it has a issues, you can't see it when you has run powercfg /energy, it will not showing any game/multimedia running and set 0.500 milliseconds timer resolution for them, and the current timer resolution is showing as 15.6 milliseconds.

That is interesting but wasn't timer always dynamic , I never messed with it but followed this thread on it .
http://forums.guru3d.com/showthread.php?t=376458

[BenYeeHua]

That is interesting but wasn't timer always dynamic , I never messed with it but followed this thread on it .
http://forums.guru3d.com/showthread.php?t=376458

Yes, but software can apply the timer resolution, and when multimedia software are running and using some API, the Vista Multimedia Scheduler(as you can see inside the Process Lasso - Options - Tools) will set the timer resolution, but it seen like this registry settings has been not used, because the timer resolution still the same.....

And yup, the overhead has been greatly reduced in Windows 8, but still no one doing research on Windows 10 TH2, so I guess we need some time to know why Windows 10 change this behave to a much lower value/timer resolution.

https://randomascii.wordpress.com/2013/07/08/windows-timer-resolution-megawatts-wasted/
---
Just checked this one, nothing changed in Windows 10 10240 build, but as it is 10240 build, not TH2, so we might need to wait before we know did it changed or not.

http://www.windowstimestamp.com/description