v1993 / evdevhook2 Goto Github PK

Unfortunately I think evdevhook2 binds the server to localhost (127.0.0.1) and I don't see the possibility to set this parameter in the config file. This could be the reason why I can't reach the UDP server from a remote IP address.

I would love to use evdevhook2 connecting from a different gaming PC and currently I'm not able to. Similar software that works with DS4 controllers let me connect from a remote IP if I set 0.0.0.0 as the server address.

Do you think I can achieve this with some extra configuration?

Thank you very much for this software, it's awesome!

Im using fedora 39 (specifically nobara) and im running into issues running the appimage. Ive tried the commands to build from source but either im too inexperienced or there is an issue. I install the apppimage evdevhook2-v1.0.1-x86_64.AppImage using gear lever and it fails and tells me to check the log. Heres the output:

thenINFO:root:Exctracting with p7zip
INFO:root:Installing appimage: /home/user/Desktop/evdevhook2-v1.0.1-x86_64.AppImage
INFO:root:Deleting original appimage file from: /home/user/Desktop/evdevhook2-v1.0.1-x86_64.AppImage

i do think that its much help. When i try to build from source using the commands in the description it tells me that the meson directory is not a build directory. Like i said im not too experienced troubleshooting building from source. I hope it is a simple fix or maybe just user error, either way some guidance on a fix would be much appreciated.

P.S. if i can get it working, do i just edit the exampleconfig.ini and change the name to just config.ini? Im trying to use this alongside SteamDeckGyroDSU for CEMU. Im sure I just need to change the port to 26761 instead of 26760 or something right? i was gonna play with it to figure it out.

I'm maintaining batocera-extra to improve motion support in batocera. Your other project linuxmotehook2 is already integrated, as well as joycond-cemuhook (Nintendo) and dsdrv-cemuhook (Sony). Now that you released v1.0.0 of evdevhook2 I thought I give it a try, too. The integration is available in branch feature/evdevhook2.

Tests with Citra have been successful - motion works, tested with a Switch Pro and a DS5 controller on a custom port. So evdevhook2 works - great!

Unfortunately, I didn't get it to work with Cemu. I tried the version bundled with batocera as well as an AppImage binary. Behavior is the same: I can pick a controller for API DSUController, but I can't map any buttons, and motion also doesn't work. I tried to add the same controller via SDLController API, but button mapping doesn't work either. This problem does not occur using joycond-cemuhook or dsdrv-cemuhook.

Do you have an idea what could be wrong here?

See joaorb64/joycond-cemuhook#72 for basic idea about implementation.

Relevant fields:

• Serial - corresponds to device's uniq, used to locate the correct object
• Percentage - main means of getting battery status
• Status - should be used to query if device is currently charging/fully charged

It seems that the optimal course of action is to write an async routine that uses a cancellable to track object's lifetime - it can poll interface for state changes once in a while.

See #9 for reasoning on this. Udev already allows to narrow down potentially interesting devices to accelerometers, so false alerts aren't expected to be a problem.

The main point is to add X-AppImage-Integrate=false so that CMD tool isn't attempted to be integrated, but it's also probably a good idea to set "Launch in terminal" entry (whatever it's called) to true.

I'm working on getting Gyro support added for the ASUS ROG Ally. We have a working kernel driver that outputs to iio, and I've created a program that translates the raw iio output into an evdev device using uinput (https://github.com/KWottrich/ally-motion-evdev). When trying to use my uinput device with evdevhook2, I'm getting an assertion failure because uinput doesn't support setting the uniq attribute of your device:

** (evdevhook2:16302): CRITICAL **: 11:36:45.907: evdevhook_config_get_device_config: assertion 'uniq != NULL' failed

I have verified that I can work around this by manually assigning a mac address (which doesn't seem to ever get used...?) and changing get_device_config to skip the lookup by uniq and always return allowlist_mode ? null : new DeviceConfig();

I started exploring this space as Steam Input (on my Deck OLED) does not have an option to simply "pass through" the gyro to the game (in this case moonlight.) I am not sure why this limitation exists (very new to all this, maybe because it cannot due to x-input?) but I was not satisfied using gyro "As a joystick" due to how it made TOTK behave (my setup is TOTK on Y*** streamed over Sunshine/Moonlight) to my deck.

If i disable "Steam Input" for my Dualsense Edge completely, then the gyro works as expected, but I lose a lot of functionality (like being able to map the FN and rear paddles, trackpad, etc.) which I was not ok with.

I was surprised how well https://github.com/kmicki/SteamDeckGyroDSU worked for the inbuilt gyro in the Deck, and start searching if something like had been already written for external controllers, and found your awesome project.

Now, I had to run the AppImage version of evdevhook2 using sudo, but Y*** test fails as it says it is not getting any motion data.

Is there some other tool i could use to validate if Y*** is at fault, or If I am running evdevhook2 incorrectly on the Deck?