CBF seems to be broken on Arch Linux

[3MPOW]

As the title states, the current cbf mod seems to be broken in a weird way. The game will not register any input at all during a level, but when you press at the start and release, the game will keep holding. Disabling the "Wine workaround" option seems to fix this, but since I play on a sayodevice, CBF functionally disables as the sayodevice seems to be grouped as a keyboard device. Has anyone encountered this issue before? I have looked around online and there seems to be no mention of it anywhere. Any help is appreciated. Thanks!

[zL4mpY]

I have the same issue and I believe syzzi knows that Wine workaround is broken on Linux and is working on a way to fix it (that's what I heard on the Geode discord server)

[Axtraa]

you can use proton 10.4 on steam to get CBF worked again but this is still very buggy

[zL4mpY]

you can use proton 10.4 on steam to get CBF worked again but this is still very buggy

i tried to do so but my game just doesn't run win proton 10 at all, it straight up crashes even without geode

[3MPOW]

you can use proton 10.4 on steam to get CBF worked again but this is still very buggy

I think you meant proton 10.0-4, but the fix you suggested seems to work. Thanks!

[MysticChromium]

Same issue here, now Proton 10 CBF also is breaking on StartPos copies of certain extremes.

[Axtraa]

@MysticChromium I think its when the game lag so much cbf crash and you have to restart your game

[MysticChromium]

Nope, it's actually because the "Wine Workaround" option is no longer needed for keyboard input starting with Proton/Wine 11, which I only learned after a discussion in the Geode Discord server. Disabling the workaround fixed all input problems and allowed use of the mod with Proton 11. They should really mention this in the readme, so that people don't do a bunch of extra troubleshooting and think they have to downgrade Proton.

[MysticChromium]

Update: it seems there's more to this story after further testing and discussion, for now it actually is just the safest bet to downgrade to Proton 10 and use the Wine Workaround

[kodirovsshik]

Can confirm experiencing the same issue, going back to proton 10 works

[TokuMSK]

Greetings, make sure to check #198 , as this a potential universal fix for linux input.