search

libretro / RetroArch

Cross-platform, sophisticated frontend for the libretro API. Licensed GPLv3.
http://www.libretro.com
GNU General Public License v3.0
10.39k stars 1.84k forks source link

RetroArch on Ubuntu does not respond to input from Steam Link (Raspberry Pi) #7990

Open ReaperMantis opened 5 years ago

ReaperMantis commented 5 years ago

Description

RetroArch on Ubuntu is not responding to input coming from an Xbox 360 Wireless Controller via Steam Link on Raspberry Pi.

Expected behavior

Controller input should be recognized by RetroArch.

Actual behavior

RetroArch opens and detects a controller is connected. Buttons / directionals / joysticks are not being recognized by RetroArch.

Steps to reproduce the bug

  1. Configure Ubuntu
    • Add user to group input
    • Create udev rule with following contents: KERNEL=="event*", NAME="input/%k", MODE="666"
    • Reboot
  2. Install Steam on Ubuntu 18.10
  3. Create a non-Steam game shortcut for RetroArch
    • Games -> Add Non-Steam Game to My Library
    • Select RetroArch
    • Click Add Selected Programs
  4. Update Rasbperry Pi to latest Raspbian
  5. Install Steam Link app on Raspberry Pi
  6. Plug Xbox 360 Wireless Receiver into Raspberry Pi and sync controller
  7. Run Steam Link app on Raspberry Pi and connect it to Ubuntu
  8. Launch RetroArch from the Steam Library

RetroArch will launch. Yellow text on the bottom of the screen will display the text 100%: Xbox 360 Controller configured in port #0

Pressing any buttons / joysticks on the controller will not invoke any response in RetroArch.

Console prints the following lines related to detecting the controller: [INFO] [udev]: Plugged pad: Microsoft X-Box 360 pad (10462:4607) on port #0. [INFO] [udev]: Pad #0 (/dev/input/event16) supports 0 force feedback effects. [INFO] [Autoconf]: 2 profiles found. [INFO] [autoconf]: selected configuration: /home/ubuntu/.config/retroarch/autoconfig/Microsoft X-Box 360 pad.cfg [INFO] [Joypad]: Found joypad driver: "udev".

Ubuntu detects the control once Steam Link is connected as follows: I: Bus=0003 Vendor=28de Product=11ff Version=0001 N: Name="Microsoft X-Box 360 pad" P: Phys= S: Sysfs=/devices/virtual/input/input36 U: Uniq= H: Handlers=event16 js0 B: PROP=0 B: EV=b B: KEY=7cdb000000000000 0 0 0 0 B: ABS=3003f

Other steps I have taken:

Other Steam games are able to detect and make use of the control.

If I use Steam to launch RetroArch without the Raspberry Pi/Steam Link and have the controller plugged into the Ubuntu system, the controller works correctly, even in Big Picture mode.

Bisect Results

I do not know when this began.

Version/Commit

Environment information

orbea commented 5 years ago

Does the controller work without steam link?

ReaperMantis commented 5 years ago

Yeah, if I plug the controller into the Ubuntu system and launch RetroArch from Steam, the controller works correctly.

andres-asm commented 5 years ago

https://github.com/libretro/RetroArch/issues/4472 same issue with gamestream

ReaperMantis commented 5 years ago

I just found that the controller can work with the Steam Link, but only if I select sdl2 as the video driver. It seems that Steam is conditionally sending gamepad events based on the state it thinks it's in.

I tested this by having RetroArch already running on Ubuntu in the background with the remotejoy core loaded and allowing the interface to continue running when RetroArch has lost focus.

This shows that Steam is sending gamepad events on the condition that it thinks a game (as opposed to an application?) is running.

Out of curiosity, I changed the video driver from gl to sdl2 and launched RetroArch from the Steam Link. Input was passed successfully into RetroArch.

Something is happening with sdl2 that is not happening in gl that lets Steam know a game is running. I am unable to test Vulkan and xVideo drivers at this time.

Is this something that can be addressed on the RetroArch side?

ReaperMantis commented 5 years ago

Found a semi-workaround to get the controller working with GL...

eregnier commented 4 years ago

Hey, I meet the same issue using gamestream. I did one post here to explain my issue. I first thought it was related to gamestream system, but it looks like clearly now that it is related to retroarch project. I am happy to find there is already some folks investigating on this issue.

I will start do some extra search around content here to understand what is this problem real state. The better would be that is is already solved. In case this is not, I will try to help in any way to solve this issue. Here is my post on Nvidia forum related to this where I started my investigations.

Does someone have any more clue / information to share to think about a fix for this ? Low level code c/sdl/driver and such is not where I shine, but I really would like to help in any way to solve this issue. Is it really something related to some drivers ? is it related to window environment that does not handle things properly ?

For now, I don't really mind how to reproduce this bug in a development environment because the stack is quite complicated. I guess my best bet would be to compile retroarch and hot patch my emulation system (retrobat) for testing purposes.

The next step I think is to run my retrobat install through a steam process on the shield in case this is a viable workaround.

thank you for this project anyway !

Edit :

Well I tried what reaper mantis said about using steam as wrapper. It works just fine. This is enough as solution for me so it is ok for my usage.

The procedure I used for those interested and how to run a "clean" gamestream integration is described in my post on nvidia forums.

Thank you very much reaper for this sufficient working workaround !