On some PCs, actual clicking rates (CPS) may differ up to 30% from the value set in the GUI.

[windows-2048]

(From Weeii user that emailed me)

I just wanted to ask you about an issue, where the numbers I put don't outcome the same. In my old laptop, I used to put 14.50 to get 14-15 CPS (clicks per second) now, when I set it to 14.50 I get around 10. And if I set it to 15, it gives me 10 still. Same for right click. I need to fix this because this program is necessary for me, and I really need to have accurate outcomes. Do you have any solutions?

Just to know: I switched to my new PC, installing the same version of the program, but my new PC has nvidia i don't know if Nvidia is slowing it down or something.

[windows-2048]

I've tried to reproduce this bug on my test PCs. I couldn't do that for CPS < 1000. The app works accurately. Nevetheless, there is possibility to decline from CPS set in the GUI due to use of arrayed SendInput() Win32 calls, when some 10-100 mouse events are being passed to the SendInput() at once. This behavior depends on the hardware you use. Also, CPS reached in virtual machines, shoud be much less than ones on bare hardware.