Potential fix for linux input

[TokuMSK]

Greetings, so as implied by the title, this is a potential fix for linux input not working (do remember that it only has a real effect if Wine Workaround is enabled), where, as seen in a log in the issue #185 , the user who shared the log showed that there was a missing library, or should i say, an unloaded one. So, because the mod depends on this library being loaded in order to register inputs, when he tried to run the game with the mod, the mod was not working because of it not being loaded when requested. To fix this, simply set this as an environment variable (or launch option, for example, if you are playing it through steam):

LD_PRELOAD="/usr/lib/libevdev.so.2"
(consider this particular location as a symlink if you encounter that, but nevertheless, it will still work, as long as it points to the corresponding library).

Edit: if the above does not work or stops working after a while, the following is preferable when preloading a library: LD_PRELOAD="$LD_PRELOAD=/usr/lib/libevdev.so.2"

Edit 2: if CBF is still not working, make sure to check on the System Monitor/Task Manager of your preference if "linux-input.so" is up and running along with the game, as CBF needs it to register inputs between frames on Wine.

Do note that, at least in my case, the order of the variables you use may affect the behaviour of the application, for instance, i have that variable set as the first option on the line, but if it still works regardless of the order, good then.

@theyareonit, greetings, hope you are doing well, make sure to test this potential fix i found out about, just so you could confirm that it effectively works and also warn about it, like when you warned about the input group.

[korzenroot]

thank you, this fixes CBF on proton experimental for me

[TokuMSK]

thank you, this fixes CBF on proton experimental for me

Nice! And that makes me remember something about proton, that, to further confirm it works, i was using the latest Proton CachyOS at the time of testing and writing the (non) issue.

Greetings.

[zL4mpY]

Thanks, I can confirm this works, even though the doubled inputs issue still can happen (at least it happened for me on Proton Experimental).

[TokuMSK]

Right, but as far as i know, that could happen on any piece of hardware when it has enough polling rate/low enough response time, now, if it is the mod, needs work out, indeed.

And, now that you mention it, i want to inform that i had an issue today too, where the mod won't work even if the library is preloaded, but that might be just a rare bug, because it got fixed by reopening the game until it responded back, so it is not a real issue from the mod.

Edit (read topic starter): it seems, the last issue i mentioned here, is a bug, indeed. It is a bug with the preloading command, and doing what i suggested in the edit of the topic starter is a way to work around it.

Edit No.2: @zL4mpY, greetings, here to tell you that the double inputs issue did happen to me some minutes before writing this edit, though, it seems to be as rare as the preload bug, i would say even more rare.
If it serves you good, i got the issue when enabling right click p2, though it might not be the main cause of it, and i have even tested the setting still on after reopening the game, but the issue was gone.
As i said, because of these bugs being so rare, they need to be traced accurately and handled very carefully, to the root if needed.

[MysticChromium]

The fix is not working on Bazzite for me, even after fixing library path to /usr/lib64 as it is on this system

[Diramix]

Thanks, adding LD_PRELOAD=/usr/lib/libevdev.so.2 %command% to the launch options fixed it for me

[TokuMSK]

Hi!
Ok, so i have an update on this fix; basically, some mods, for some odd reason, do not play well with CBF, to the point where, even if the mod is listening to your inputs, it will not work (basically, become useless).

Because of this, make sure to hard disable/uninstall any mods that, immediately after installing/enabling, make the mod stop working; for instance, the Death Tracker mod by abb2k proved to be the one mod that disabled CBF, so, once again, make sure to leave the mod hard disabled or uninstalled when trying to use CBF.

@MysticChromium , greetings!
Make sure to check if you have the other mod that i have mentioned, and if you have it, follow this advise.

Good day!

[MysticChromium]

Sorry, but disabling other mods when they turn out to conflict with the Wine implementation of CBF isn't really a workable solution, especially when the mod is another QoL-boosting mod that I use regularly, like Death Tracker. I appreciate the effort in getting this sorted out, but it seems I'll be using Windows for GD for now.

[TokuMSK]

Alright, i will be testing some more, just to see where could the cause be.

[TokuMSK]

@MysticChromium , greetings!
So, i got done testing, and, in summary, the disabling issue seems not to have anything to do with CBF, or other mods, for that matter.

Here is an explanation: So, first, when i have played with compatibility tools from Steam, it proved that, many times, the behaviour of the game towards mods, or the mod launcher itself, was very inconsistent, so much so that i once got a crash, on which message, pointed to Geode itself as the faulty mod.

Basically, when i turned off the "Force the use of a specific Steam Play Compatibility tool" for Geometry Dash, the mod started working as intended, but it was the other way around when i forced a specific tool under that setting, where, most of the time, i would not work at all.

Now, regarding Geode, there seems to be a weird behaviour with the mod loader, where, if you happen to have 255+ mods installed, some mods would not work properly, and for this, it is good to warn about this on the CBF repository too, as this is especially a mod which is affected by this bug in Geode.

Also, my bad if i have made wrong assumptions, this whole situation turned out to be very odd, indeed.

But still, many thanks for having a look into this, and for the patience.

Have a nice day!

[Evit08]

#205

[TokuMSK]

Greetings, once again!

First of all, thank you @Evit08 for the pull request and, thereby, the fork with the fix for a longlasting bug, i, personally, did not experience much from that issue, though i may be wrong, due to the fact that it has to do with linux-input itself.

Second, turns out, most of what i said the latest was wrong, it all summarized as this:

I checked on KDE System Monitor, and noticed "linux-input.so", the library which allowed the mod from registering inputs between frames through wine, was not running.

So, the issue is right there, plain and simple.

@MysticChromium , make sure to check if linux-input.so is running when the mod is started, if the mod does not work, now you know why.

@theyareonit , make sure to take the necessary fixes for the library not loading to the master branch.

And, as for me, i will check if there is anything i can do to work around this, and if i get anything, i will make you know.

Afternoon!

[zL4mpY]

I think the reason CBF sometimes disabling is due to its timeout when GD doesn't send any data that it is alive to it. That happened for me on BPATA MPAKA which is a really laggy level for my PC, so everytime I tried to play it it was loading for like 10 seconds, which was enough for CBF to quit.

[3MPOW]

@TokuMSK This does not at all work for me. I think linux-input.so isn't loaded when GD is started, but what do I do now? I would provide more information, but I do not know what logs etc. you actually need.