SOCD (or Snappy Tappy) getting voided* with CBF

[l1up]

Im using a Sayodevice o3c with SOCD[last input prority] (also known as Snappy Tappy for Wooting) set for space and up
on Vanilla GD if i hold a key and the press the other one without letting go of the first key, the wave (or input) would still be going up, but with CBF enabled and doing the act (which is basically holding the 2 keys at once) the input gets voided

video for visual:
https://github.com/user-attachments/assets/595b7b3c-e662-43d0-a5f2-88938da30e66

OS: Linux NixOS
Proton: 10.0-4
Steam launch options:
LD_PRELOAD="$LD_PRELOAD=/usr/lib/libevdev.so.2" PROTON_ENABLE_WAYLAND=1 DXVK_FRAME_PACE=low-latency-vrr-144 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __GLX_SYNC_TO_VBLANK=0 WINEDLLOVERRIDES="xinput1_4=n,b" %command%

native Steam
Input on my user group

CBF works fine otherwise

[TokuMSK]

Greetings!

So, regarding the issue here, i am also using SOCD on my keyboard, and, replicating your scenario, this seems to be not a problem with cbf, as i have also tested it with cbf hard-disabled, and the behaviour persists, but this may also have something to do with the gamemode itself; here, i was about to upload a short video about me playing with dual modes on different gamemodes, but the upload failed :/ .

But, to confirm it is not cbf (you can test it yourself), the wave will behave the same as in your video, but a gamemode like swing, with SOCD on, will be playable as if it was a ship (drop for normal gravity, and lift for upside down), and another gamemode that behaves like that is the ufo, where if you hold the first snap key, then press the other one, it will jump, but it will also do that if you lift the last snap key pressed while having the first one still held.

And, as for the wave, as it requires you to hold the key for it to move, if you alternate from one snap key to another, being these two attached to the same command in the game, it will result in it doing it immiedately, a.k.a doing it on the next frame/poll too, which results in it behaving as if you never stopped holding; the same applies for the cube and the ship.

Now, if you do want the wave (or any hold gamemode) to alternate direction/state with snap keys, consider attaching one of the snap keys to a key where it does not do any command in the game, a.k.a attach a snap key to a key that does nothing, this way, you will have a key that does nothing in the game, but serves solely as a snap key to the key you intend to use for your command.

Good day!

[TokuMSK]

Hi!
@l1up , let me make it clear, i, personally, did not actually face this issue, and, until recently, could not tell you anything to work around it properly, my bad.

But now, there is a pull request (along with a fork) which has the fix for doubled inputs.

Make sure to check the pull request #205 !

Have a good day!

[l1up]

@TokuMSK the bug im reporting is how when enabling CBF, the SOCD behaviour gets voided. I showed in the video exactly what the problem is: the LACK of the behaviour. The problem is not weird inputs or the "weird behaviour" you mentioned; the problem is the lack of the "weird behaviour" that occurs when enabling SOCD that disappears for some reason when enabling CBF.