#new fast input maybe not registering very quick inputs,

1 messages · Page 1 of 1 (latest)

fervent rock
#

@forest minnow ka ob du bessere clips hast

neat field
#

okay are you saying you want it to not click?

fervent rock
#

jukki wasnt able to replicate this when fast input was set at 20ms

#

and some shenanigans going on between saiko vs tclient hook length

neat field
#

can't replicate

neat field
fervent rock
#

jukki actually noticed this on tclient and switched on vibeclient to test tclient vs saiko implementation

#

let me try to replicate

#

i will send clip

neat field
#

i just tried for 5min straight and i can't replicate this on any setting

true veldt
#

please make sure when reporting that you are on the latest offical tclient binaries

fervent rock
#

Im trying rn and cant replicate it aswell, maybe its something that only an 8k polling rate mouse can achieve?

true veldt
neat field
#

i have an 8k polling mouse too

true veldt
#

I am sure he is just using saikos modded client tho

fervent rock
#

ok idfk why this doesnt make any sense afaik

#

but when i turned off fast input i was able to replicate it for whatever reason

#

But fast input should only be visual right? (fastinput vs no fastinput)

neat field
#

without fast input this can happen if you click between ticks afaik

#

with fast input it should never happen

lone dome
#

I fixed this already dw

lone dome
#

if you click for less than 2 ticks nothing happens

#

also the hook length is only an illusion, the hook does not travel smoothly, it just gets visually interpolated between ticks, so the maximum length it reaches is based on the frame that you release your mouse and fastinput triggers to re-predict your hook never existing

fervent rock