You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NVidia Geforce Experience version:
Sunshine Moonlight Embedded version:
Moonlight Embedded 2.5.3 (SDL;X11;VAAPI;ALSA;PULSE;EMBEDDED) Moonlight Embedded source:repository/included in distribution/compiled from source/...
Compiled from source Moonlight Embedded running on:Raspberry Pi/Cubox-i/Hummingboard/Other linux device/...
x86 Moonlight Embedded running on distribution:Arch Linux/Raspbian/OpenELEC/...
Debian Sid
Verbose output -verbose of Moonlight Embedded:
N/A
What is the expected result? moonlight map -input /dev/input/by-id/usb-Valve_Software_Wired_Controller-if01-event-joystick to react to triggers pulled on Steam Controller. Nothing happens. What happens instead of that?
Only buttons at the end of the trigger pull are recognised.
I have found this as a potential cause, but the code in evdev.c goes way over my head. I understand that the Steam Controller is rather niche, so I don't expect a fix, but happy to test anything that might fix it!
By the way, this software is incredible, I've got it running with VAAPI, 1080p120 and it's virtually indistinguishable from sitting at my desk. Made playing in the living room possible, so thank you so much!
The text was updated successfully, but these errors were encountered:
Please provide the following info.
NVidia Geforce Experience version:
Sunshine
Moonlight Embedded version:
Moonlight Embedded 2.5.3 (SDL;X11;VAAPI;ALSA;PULSE;EMBEDDED)
Moonlight Embedded source: repository/included in distribution/compiled from source/...
Compiled from source
Moonlight Embedded running on: Raspberry Pi/Cubox-i/Hummingboard/Other linux device/...
x86
Moonlight Embedded running on distribution: Arch Linux/Raspbian/OpenELEC/...
Debian Sid
Verbose output
-verbose
of Moonlight Embedded:N/A
What is the expected result?
moonlight map -input /dev/input/by-id/usb-Valve_Software_Wired_Controller-if01-event-joystick
to react to triggers pulled on Steam Controller. Nothing happens.What happens instead of that?
Only buttons at the end of the trigger pull are recognised.
jstest can read the analog triggers fine, and it seems like someone else has mapped the analog output to the triggers(ID 03000000de2800004211000011010000), which means it should work in other software (I guess?).
I have found this as a potential cause, but the code in evdev.c goes way over my head. I understand that the Steam Controller is rather niche, so I don't expect a fix, but happy to test anything that might fix it!
By the way, this software is incredible, I've got it running with VAAPI, 1080p120 and it's virtually indistinguishable from sitting at my desk. Made playing in the living room possible, so thank you so much!
The text was updated successfully, but these errors were encountered: