Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sidewinder precision pro Joystick not detected in games when using Gamescope #1687

Open
3 of 6 tasks
Crystal4276 opened this issue Dec 28, 2024 · 0 comments
Open
3 of 6 tasks

Comments

@Crystal4276
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Are you using any gamescope patches or a forked version of gamescope?

  • The issue occurs on upstream gamescope without any modifications

Current Behavior

Gamescope Joystick Input Issue

Environment

  • Joystick: Microsoft SideWinder Precision Pro (USB)
  • Game: Elite Dangerous (Steam version)
  • Gamescope version: 3.15.15

Issue Description

The joystick is not detected by the game when running under Gamescope, despite working correctly without Gamescope.

Steps To Reproduce

  1. Joystick works correctly when launching Elite Dangerous directly
  2. While running under Gamescope, /dev/input/js0 shows the device is still present and readable:
    jstest /dev/input/js0
    Driver version is 2.1.0.
    Joystick (Microsoft Microsoft SideWinder Precision Pro (USB)) has 6 axes (X, Y, Rz, Throttle, Hat0X, Hat0Y)
    and 9 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3).

Attempted Solutions

  1. Using Steam Input configuration
  2. Launching with Steam integration enabled (gamescope -e)

Expected Behavior

The joystick should be detected and usable in Elite Dangerous when running under Gamescope, just as it is when running the game directly.

Additional Notes

The joystick remains detected at system level (verified through jstest) even while Gamescope is running, suggesting this is specifically an input passthrough issue within Gamescope.

Hardware information

- Distro: Arch 
- CPU: 9900K
- GPU: RTX2080
- Driver Version:  565.77

Software information

- Desktop environment: Qtile/hyperland/gnome
- Session type: Wayland or X11
- Gamescope version: 3.15.15 
- Gamescope launch command(s): gamescope -e -w 3440 -h 1440 -- %command%

Which gamescope backends have the issue you are reporting?

  • Wayland (default for nested gamescope)
  • DRM (default for embedded gamescope, i.e. gamescope-session)
  • SDL
  • OpenVR

Logging, screenshots, or anything else

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant