mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 13:02:03 +00:00
[GH-ISSUE #185] Unable to make motion work on moonlight android #123
Labels
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#123
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RyuunosukeDS3 on GitHub (Mar 13, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/185
After a lot of tinkering and debuging it seems tome that wolf is not emulating or passing motion sensors to the host. Using the command
cat /proc/bus/input/devicesthe only wolf related device is:I am using the same configuration stated here: https://games-on-whales.github.io/wolf/stable/user/quickstart.html#_virtual_devices_support
I tried overriding it to xbox, to ps and no override at all. I'm using moonlight on android and emulating motion through it. Nothing seems to work... Any ideas?
@ABeltramo commented on GitHub (Mar 14, 2025):
Could you please share the Wolf logs, possibly with the env variable
WOLF_LOG_LEVEL=DEBUGenabled?@RyuunosukeDS3 commented on GitHub (Mar 18, 2025):
Sorry it took so long. I just had free time right now.
@ABeltramo commented on GitHub (Mar 26, 2025):
After a bit of digging, this seems to be an issue with Moonlight Android https://github.com/moonlight-stream/moonlight-android/issues/1377
I can replicate the same behaviour with Sunshine. Unfortunately, the client wouldn't send us the information about the added Gyro capabilities, and we end up defaulting to a Xbox joypad.
@RyuunosukeDS3 commented on GitHub (Mar 26, 2025):
Weirdly enough, even when I plug a DualSense directly into the PC, the gyro still doesn’t seem to work properly. You mentioned that the client defaults to an Xbox joypad, I’m actually using the Xbox override. Could that be messing things up?
I use the override so my controller works properly on Steam, but if that’s the issue, is there a way to apply it only for Steam while keeping the correct input for other apps (Like pegasus)?
@ABeltramo commented on GitHub (Mar 26, 2025):
This is definitely a different issue, how are you checking that? Via this Steam setting page?
If that doesn't work when plugging it in the host you are probably missing the required udev rules https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-input.rules how are you running Steam? Which distro do you have?
With the current code there's no way unfortunately to make Moonlight Android pass those motion events, I'm not even sure the client will actually send them to begin with..