Timer Resolution - 0.497 ms

Everything about latency. Tips, testing methods, mouse lag, display lag, game engine lag, network lag, whole input lag chain, VSYNC OFF vs VSYNC ON, and more! Input Lag Articles on Blur Busters.
vhagar
Posts: 10
Joined: 27 Sep 2022, 05:10

Timer Resolution - 0.497 ms

Post by vhagar » 09 Jan 2023, 18:22

I've noticed Timer Resolution will read 0.497 ms with 'bcdedit /set useplatformtick no' instead of 0.5 ms.

Researching various threads here some have suggested that using 'bcdedit /set useplatformtick yes' will always lock in Timer Resolution to 0.5 ms - that being said this may not be favorable due possible inherit input latency that I've observed firsthand and agree the system is just not as snappy and responsive when it's at 0.497 ms vs 0.5 ms.
--
My question is, sometimes on first boots / reboots, timer resolution will read 0.5 ms correctly without using useplatformtick set to yes. I cannot pinpoint how this happens or if it's a timing thing when Timer Resolution is run...?

Is there a 100% method/way to consistently get 0.5 ms instead of getting 0.497 ms (without using useplatformtick yes) ?

abdelkadr13
Posts: 4
Joined: 11 Jan 2023, 12:28

Re: Timer Resolution - 0.497 ms

Post by abdelkadr13 » 11 Jan 2023, 12:33

I would also like to know, if anything under the max. supported timer resolution of 0.5ms causes any problems.

In Win11 for example, there seems to be fixed & I constantly get 0.5ms. Why is it messed up in Win10 then?

sherifmagdy32
Posts: 121
Joined: 08 Jan 2022, 23:43

Re: Timer Resolution - 0.497 ms

Post by sherifmagdy32 » 12 Jan 2023, 07:02

I donot remember where i saw this but someone recommended testing both
bcdedit /set tscsyncpolicy enhanced
bcdedit /set tscsyncpolicy legacy
that one of them gave him a consistent 0.5 try them out and see if it helps

vhagar
Posts: 10
Joined: 27 Sep 2022, 05:10

Re: Timer Resolution - 0.497 ms

Post by vhagar » 12 Jan 2023, 11:54

sherifmagdy32 wrote:
12 Jan 2023, 07:02
I donot remember where i saw this but someone recommended testing both
bcdedit /set tscsyncpolicy enhanced
bcdedit /set tscsyncpolicy legacy
that one of them gave him a consistent 0.5 try them out and see if it helps
Thanks for the suggestions, I've tested both enhanced and legacy and upon a fresh boot if starting timer resolution immediately it'll read 0.497 on max.

Now, if I leave the startup process for after a min or two... then launching timer resolution it'll 'sometimes' show 0.500 ms on max with either enhanced or legacy. More often it'll be 0.497 ms.

Again, unsure if something is running that causes it to not read .500 ms.

TheKelz
Posts: 136
Joined: 15 Aug 2022, 17:15

Re: Timer Resolution - 0.497 ms

Post by TheKelz » 12 Jan 2023, 13:15

vhagar wrote:
12 Jan 2023, 11:54
sherifmagdy32 wrote:
12 Jan 2023, 07:02
I donot remember where i saw this but someone recommended testing both
bcdedit /set tscsyncpolicy enhanced
bcdedit /set tscsyncpolicy legacy
that one of them gave him a consistent 0.5 try them out and see if it helps
Thanks for the suggestions, I've tested both enhanced and legacy and upon a fresh boot if starting timer resolution immediately it'll read 0.497 on max.

Now, if I leave the startup process for after a min or two... then launching timer resolution it'll 'sometimes' show 0.500 ms on max with either enhanced or legacy. More often it'll be 0.497 ms.

Again, unsure if something is running that causes it to not read .500 ms.
I don't think what you are experiencing is an issue at all. The timer varies like that all the time, I'm pretty sure it was designed to do that.

vhagar
Posts: 10
Joined: 27 Sep 2022, 05:10

Re: Timer Resolution - 0.497 ms

Post by vhagar » 12 Jan 2023, 16:13

After more testing it seems using legacy for tscsyncpolicy does indeed seem to give me .500 ms more consistently than using enhanced.

Steps:
- Boot
- Let it sit for about a minute and move the mouse around notice the delay and what not, then it just kicks in you can feel the smoother difference.
- Run timer resolution and it shows .500 ms max. (…so far on my machine)

Slender
Posts: 573
Joined: 25 Jan 2020, 17:55

Re: Timer Resolution - 0.497 ms

Post by Slender » 16 Jan 2023, 22:23

your motherboard is broken if timer shows 0.5ms on useplatformtick no/deletevalue.

User avatar
MadMark
Posts: 9
Joined: 06 Dec 2022, 21:49
Location: Poland

Re: Timer Resolution - 0.497 ms

Post by MadMark » 19 Jan 2023, 19:32

vhagar wrote:
09 Jan 2023, 18:22
I've noticed Timer Resolution will read 0.497 ms with 'bcdedit /set useplatformtick no' instead of 0.5 ms.

Researching various threads here some have suggested that using 'bcdedit /set useplatformtick yes' will always lock in Timer Resolution to 0.5 ms - that being said this may not be favorable due possible inherit input latency that I've observed firsthand and agree the system is just not as snappy and responsive when it's at 0.497 ms vs 0.5 ms.
--
My question is, sometimes on first boots / reboots, timer resolution will read 0.5 ms correctly without using useplatformtick set to yes. I cannot pinpoint how this happens or if it's a timing thing when Timer Resolution is run...?

Is there a 100% method/way to consistently get 0.5 ms instead of getting 0.497 ms (without using useplatformtick yes) ?
Propably you have disable HPET (High Precision Event Timer) in BIOS. That's why you get 0.497 ms timer resolution.
Go to BIOS settings and enable HPET. You should get 0.5 ms after that.

TheKelz
Posts: 136
Joined: 15 Aug 2022, 17:15

Re: Timer Resolution - 0.497 ms

Post by TheKelz » 20 Jan 2023, 14:59

MadMark wrote:
19 Jan 2023, 19:32
vhagar wrote:
09 Jan 2023, 18:22
I've noticed Timer Resolution will read 0.497 ms with 'bcdedit /set useplatformtick no' instead of 0.5 ms.

Researching various threads here some have suggested that using 'bcdedit /set useplatformtick yes' will always lock in Timer Resolution to 0.5 ms - that being said this may not be favorable due possible inherit input latency that I've observed firsthand and agree the system is just not as snappy and responsive when it's at 0.497 ms vs 0.5 ms.
--
My question is, sometimes on first boots / reboots, timer resolution will read 0.5 ms correctly without using useplatformtick set to yes. I cannot pinpoint how this happens or if it's a timing thing when Timer Resolution is run...?

Is there a 100% method/way to consistently get 0.5 ms instead of getting 0.497 ms (without using useplatformtick yes) ?
Propably you have disable HPET (High Precision Event Timer) in BIOS. That's why you get 0.497 ms timer resolution.
Go to BIOS settings and enable HPET. You should get 0.5 ms after that.
Not true, unfortunately. I have it enabled and it also shows 0.497ms for me.

User avatar
MadMark
Posts: 9
Joined: 06 Dec 2022, 21:49
Location: Poland

Re: Timer Resolution - 0.497 ms

Post by MadMark » 23 Jan 2023, 21:28

Do you have stock bcdedit settings or you changed something?
For example:
- useplatformtick
- useplatformclock

Post Reply