Try my new app to fix input lag (cs2_timer_fix_by_yam1ke)

Everything about latency. This section is mainly user/consumer discussion. (Peer-reviewed scientific discussion should go in Laboratory section). Tips, 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.
Post Reply
User avatar
Slender
Posts: 1818
Joined: 25 Jan 2020, 17:55

Re: Try my new app to fix input lag (cs2_timer_fix_by_yam1ke)

Post by Slender » 10 Jan 2026, 12:58

Hyote wrote:
10 Jan 2026, 12:55
Slender wrote:
10 Jan 2026, 12:46
Hyote wrote:
10 Jan 2026, 12:39
Slender wrote:
10 Jan 2026, 09:32


1803 still work for new rtx.
also, try acpi timer, it smooth for me like wow.
lol, most browsers dropped support for that build by now but I think for the timers, I still got the best results with HPET off in BIOS+Win
bcdedit /set useplatformclock false
bcdedit /set useplatformtick true
This supposedly uses the PMT timer.
I use legacy settings for almost everything, even Windows 11.
@ :talking about qpc 10mhz
@ -give advice for good working build with old timer
@: talking aboud browser
Nevermind, I am confused at the moment. After running the A1 tweaks on my GitHub I can't even access bcdedit so I have no idea what timers I'm using.
But I don't know what you mean with the @
1803 doesn't work with most games now, I don't know what you want to use it for. Especially if you want to play something like FACEIT.
u can run cpuz, open timer clock, and if qpc be ~3580, it mean PMT timer.

Hyote
Posts: 665
Joined: 09 Jan 2024, 18:08

Re: Try my new app to fix input lag (cs2_timer_fix_by_yam1ke)

Post by Hyote » 10 Jan 2026, 13:05

So again, just because I checked what I know anyways. The kernel latency in LatencyMon means nothing and just shows whatever timer resolution is being used. It's "high" because Windows doesn't enforce a lower one but the DPC Latency Checker program, lowers it to 0.997 or 1 ms just like games or multimedia programs. Nothing special and nothing useful about it.

Hyote
Posts: 665
Joined: 09 Jan 2024, 18:08

Re: Try my new app to fix input lag (cs2_timer_fix_by_yam1ke)

Post by Hyote » 10 Jan 2026, 13:06

Slender wrote:
10 Jan 2026, 12:58
Hyote wrote:
10 Jan 2026, 12:55
Slender wrote:
10 Jan 2026, 12:46
Hyote wrote:
10 Jan 2026, 12:39


lol, most browsers dropped support for that build by now but I think for the timers, I still got the best results with HPET off in BIOS+Win
bcdedit /set useplatformclock false
bcdedit /set useplatformtick true
This supposedly uses the PMT timer.
I use legacy settings for almost everything, even Windows 11.
@ :talking about qpc 10mhz
@ -give advice for good working build with old timer
@: talking aboud browser
Nevermind, I am confused at the moment. After running the A1 tweaks on my GitHub I can't even access bcdedit so I have no idea what timers I'm using.
But I don't know what you mean with the @
1803 doesn't work with most games now, I don't know what you want to use it for. Especially if you want to play something like FACEIT.
u can run cpuz, open timer clock, and if qpc be ~3580, it mean PMT timer.
I can't run CPU-Z, my Windows is too broken for that.

darkbebe
Posts: 25
Joined: 10 Apr 2025, 07:11

Re: Try my new app to fix input lag (cs2_timer_fix_by_yam1ke)

Post by darkbebe » 10 Jan 2026, 15:07

Lev1n wrote:
18 Dec 2025, 05:29
This config gives me hope. I was about to quit gaming and throw away my computer. Yesterday saw this post and downloaded config on telegram channel. Placebo or not I had 1.5 kd on warmup dm servers and played 3-4 premier game(im at 28-29 k rating). Everygame i played i hit insane shots which i never had that feeling for 1 year. Before the config i couldnt even shoot back to enemys I was barely getting positive KD. While this config was running at backround my lowest score was 25 kills and that game finished 13-4.
They still ferrari peeks you but with this config i was able to shoot back. Dont know if its placebo or something else fixed on my computer but it did happens after using this thing.
still working for you?

DangerAhead710
Posts: 29
Joined: 27 Nov 2024, 07:46

Re: Try my new app to fix input lag (cs2_timer_fix_by_yam1ke)

Post by DangerAhead710 » 10 Jan 2026, 23:26

No bro it's temporary all the app versions its all temporary no matter how settings u fiddle .

MK92
Posts: 152
Joined: 06 Oct 2025, 15:11

Re: Try my new app to fix input lag (cs2_timer_fix_by_yam1ke)

Post by MK92 » 11 Jan 2026, 04:23

No shit? Imagine thinking that some "config" will fix you issues that are caused by EXTERNAL factors...STOP with software and bios "tweaking", the stuff is interference / electricity related.

Lev1n
Posts: 101
Joined: 17 Apr 2023, 05:40

Re: Try my new app to fix input lag (cs2_timer_fix_by_yam1ke)

Post by Lev1n » 11 Jan 2026, 07:46

darkbebe wrote:
10 Jan 2026, 15:07
Lev1n wrote:
18 Dec 2025, 05:29
This config gives me hope. I was about to quit gaming and throw away my computer. Yesterday saw this post and downloaded config on telegram channel. Placebo or not I had 1.5 kd on warmup dm servers and played 3-4 premier game(im at 28-29 k rating). Everygame i played i hit insane shots which i never had that feeling for 1 year. Before the config i couldnt even shoot back to enemys I was barely getting positive KD. While this config was running at backround my lowest score was 25 kills and that game finished 13-4.
They still ferrari peeks you but with this config i was able to shoot back. Dont know if its placebo or something else fixed on my computer but it did happens after using this thing.
still working for you?
I started playing faceit again and i dont trust the exe running at backround.

User avatar
6e657275
Posts: 1
Joined: 18 Feb 2026, 13:31

Re: Try my new app to fix input lag (cs2_timer_fix_by_yam1ke)

Post by 6e657275 » 18 Feb 2026, 14:19

had a few mins to spare so i threw it into IDA and here's what it does:
  • "burst" is literally just a thread on a loop pinned to one core at highest priority that constantly runs useless math (detrimental)
  • "TLB" allocates and locks 16mb, then writes to it in 4096 byte strides, since 4kb is the standard page size its made to cause TLB misses and PTWs on every write, literally choking the cpu's mem ctl (detrimental)
  • "wobble" and "drag" are just changing the sleeps on its own thread to create "jitter"? that just prints to console to make it look like its doing something lol (useless)
the only "real" thing it does is call NtSetTimerResolution at start to force a 0.5ms interval, which there's millions of far better programs for that without all the bs
besides that, it's genuinely detrimental and probably just makes 1%s worse because of cache pollution and the fact that its constantly messing with a core for no reason

that's probably why this dude refused to release the source

Post Reply