Ryubing controller not detected

Steam is probably holding the pad

Ryubing talks to controllers through SDL, the same layer most emulators use. Steam Input sits above that layer and presents a virtual gamepad instead of the real one. When a title is added to Steam — which is how you launch it on a Deck — Steam wraps it in that virtual pad, and Ryubing sees a device it cannot map properly.

The tell is specific: the pad works in other emulators, and Ryubing’s input screen lists something like “Steam Virtual Gamepad” rather than your controller’s name.

Turn Steam Input off for that title

1. In Steam, right-click the game → Properties.
2. Open the Controller tab.
3. Set it to Disable Steam Input.
4. Restart the game from Steam so the wrapper is not re-applied.

This single step resolves most “controller not detected” reports on both desktop and Deck. Re-enable it only if you specifically need Steam’s trackpad or gyro layouts.

Map the pad in Ryubing

Open Options → Settings → Input and work top to bottom:

• Player 1 → Input Device: choose your controller by name, not “Keyboard”.
• Controller Type: match the hardware — Pro Controller for a Pro pad, Joy-Con pairs for split controllers, GameCube for the adapter.
• Buttons: map anything the automatic layout missed, then save.
• Relaunch the title rather than reloading a save state; input config is read at boot.

Known gaps that aren’t binding errors

Two behaviours keep getting reported and neither is a mapping mistake: gyro working while rumble does not (a driver gap for some pads, not a config issue), and controllers not being auto-assigned to player slots when several are connected — assign each slot by hand until auto-assignment lands.

If the pad never appears in the device list at all, the problem is below Ryubing. Check it in Windows’ game controller panel or a browser gamepad tester first, then come back.