Blur Busters Forums

No matter what CMD prompts i use or whatever i do, my timer resolution is always 0.0001 lower than what i set it to.
This is really really weird and idk if it affects anything, but i really wanna know how to fix that or the reason. Also in LatencyMon the latency is measured down to decimals 0.16546 0.56323 etc. and i remember before fresh windows install (i have windows 10) it was just natural numbers (im not sure though) I use SetTimerResolution following this guide: https://github.com/amitxv/PC-Tuning/blo ... -precision by amitxv

Looks like you need to disable synthetic timers and the high precision event timer. Make sure your running cmd prompt as administrator.

evmadic wrote: ↑

31 Jan 2024, 01:27

Looks like you need to disable synthetic timers and the high precision event timer. Make sure your running cmd prompt as administrator.

Yes brother i have HPET off in BIOS and device manager (On in bios + disabled in windows gives the same 0.0001 issue) and had synthetic timers disabled. "bcdedit /deletevalue useplatformclock" does nothing as i don't have it in my windows (AtlasOS) -

An error occurred while attempting to delete the specified data element.
Element not found.

However "bcdedit /set useplatformclock no" turns it off, but does not help with my issue or change anything(?)
I had HPET ON before in BIOS as Fr33thy said u should (source)
However this dude says otherwise so i turned HPET OFF both windows and BIOS and found out that now i can lower my resolution to 5060 instead of 5120 with even better delta. Still of by 0.0001 though

Disable HPET - bcdedit /deletevalue useplatformclock
I think this only works when you leave HPET on in bios?

My current and Max timers are both synced at .5 and I only used the above and:
Remove synthetic timers - bcdedit /set useplatformtick yes

evmadic wrote: ↑

01 Feb 2024, 05:14

Disable HPET - bcdedit /deletevalue useplatformclock
I think this only works when you leave HPET on in bios?

My current and Max timers are both synced at .5 and I only used the above and:
Remove synthetic timers - bcdedit /set useplatformtick yes

"Disable HPET - bcdedit /deletevalue useplatformclock" that's what i get in return: "An error occurred while attempting to delete the specified data element.
Element not found."
As you can see in my bcdedit /enum screenshot "useplatformtick" is set to yes
Turning HPET on/off in BIOS doesn't fix my issue

RealTweaker wrote: ↑

01 Feb 2024, 11:23

evmadic wrote: ↑

01 Feb 2024, 05:14

Disable HPET - bcdedit /deletevalue useplatformclock
I think this only works when you leave HPET on in bios?

My current and Max timers are both synced at .5 and I only used the above and:
Remove synthetic timers - bcdedit /set useplatformtick yes

"Disable HPET - bcdedit /deletevalue useplatformclock" that's what i get in return: "An error occurred while attempting to delete the specified data element.
Element not found."
As you can see in my bcdedit /enum screenshot "useplatformtick" is set to yes
Turning HPET on/off in BIOS doesn't fix my issue

If you turn HPET on in bios and then "bcdedit /deletevalue useplatformclock", do you still get the error?

I presume this be because of the great rule change that started in Windows 10 2004+. The tweaker Amit explains this in his Github as well.