this post was submitted on 25 May 2026
12 points (92.9% liked)

Steam Hardware

22159 readers
309 users here now

A place to discuss and support all Steam Hardware, including Steam Deck, Steam Machine, Steam Frame, and SteamOS in general.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Deck] - Steam Deck related.
[Controller] - Steam Controller related.
[Machine] - Steam Machine related.
[Frame] - Steam Frame related.
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

If your post is only relevant to one hardware device (Deck/Machine/Frame/etc) please specify which one as part of the title or by using a device flair.

These are not enforced, but they are encouraged.

Rules:

Link to our Matrix Space

founded 4 years ago
MODERATORS
Moxvallix@sopuli.xyz
Fubarberry@sopuli.xyz
12
(SOLVED) [Controller] SISR on Linux - how can I prevent a Wine app from picking up inputs from both the real and virtual controllers? (lemmy.world)
submitted 2 days ago* (last edited 2 days ago) by rtxn@lemmy.world to c/steamdeck@sopuli.xyz
5 comments fedilink hide all child comments
 

@who@feddit.org pointed me to the solution. Since XInput is implemented using SDL2, it can be told to selectively ignore devices by setting the SDL_GAMECONTROLLER_IGNORE_DEVICES environment variable. The value should be a hexadecimal VID/PID pair separated by /, or a comma-separated list of VID/PID pairs for multiple devices.

For the 2026 Steam Controller:

SDL_GAMECONTROLLER_IGNORE_DEVICES='0x28de/0x1304'

For other devices using a USB cable or dongle, the VID/PIDs can be listed using this command:

lsusb | sed -E 's/.*: ID ([a-z0-9]{4}):([a-z0-9]{4})/0x\1\/0x\2/'

There are some non-Steam games that I can't run through Steam because of its sandboxing (bubblewrap, Steam Linux Runtime, pressure-vessel and such). For those, I've set up SISR to capture the SC's input and remap it to a virtual controller.

While SISR itself works (and quite well with both the touchpads and the gyro), the game ends up receiving inputs from both the virtual and the physical controllers simultaneously.

Running wine control joy.cpl shows both the real SC and the virtual Xbox 360 controllers as DirectInput devices. The XInput list is empty, but the XInput tab shows that it receives input events from both the SC and the virtual controller. Disabling hidraw or the individual DInput devices has no effect.

I'd like to find a way to either hide the device from Wine's XInput driver, or to prevent the XInput device (within Wine) from sending input events to the game. So far, no luck. Any help would be appreciated.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] katze@lemmy.4d2.org 0 points 2 days ago (1 children)

Why do you need SISR for this? If he game is receiving input from the real stream controller (as you wrote), why not just disable SISR and go along with that?

Anyway, what you can try is to disable one of the controllers in the "Game Controllers" section of control, as outlined here: https://github.com/AntiMicroX/antimicrox/wiki/Methods-for-Disabling-Joystick-Reading-in-Linux

That website also include some more advanced methods, but I don't think they will apply to your usecase, unless you want to run SISR as a different user.

[โ€“] rtxn@lemmy.world 1 points 2 days ago* (last edited 2 days ago)

why not just disable SISR and go along with that?

Because I want to use all inputs on my controller, and (so far) only Steam Input allows me to do that. Without Steam Input, the SC is comparable to an Xbox controller.

I've tried most of the methods in the article, to no effect.