Test the gamepad outside Ryujinx
Connect one controller by a stable USB cable or a known-good Bluetooth pairing. Confirm that the operating system sees button presses and both sticks before opening the emulator.
Gamepad setup guide
Ryujinx Controller Setup: Map a Gamepad and Test Player 1
Follow a clean Ryujinx controller setup from the physical gamepad to a saved Player 1 profile. This guide covers Windows, Linux, Steam Deck, and macOS, with separate checks for Steam Input, controller type, analog axes, and per-game overrides.
$ channel: canary
$ platforms: windows linux macos
$ source: ryubing releases
$ status: verify before download
Independent guide. No keys, firmware, ROMs, DLC or game files are hosted here.
Primary goal
A saved Player 1 profile
Best first test
One pad, one game
Steam Deck layer
Physical or virtual pad
Setup boundary
Map input before tuning graphics
Ryujinx Controller Setup in Five Controlled Steps
Open the Player 1 input profile
Open Ryujinx input or controller settings, select Player 1, and choose the device name that matches the pad you are holding. Leave other player slots alone for the first test.
Choose the closest controller type
Select the layout that matches the gamepad and map face buttons, sticks, triggers, and shoulders. Use a fresh profile when an old device mapping is confusing.
Save, close, and reopen the profile
Save the mapping, close the settings window, and reopen it to confirm the assignments persisted. A mapping that only works until the dialog closes is not finished.
Test one legal local game
Launch one title and test a repeatable menu or short scene. Add Player 2, motion controls, or per-game profiles only after the default profile works.
Think in layers when setting up a controller
Editorial illustration, not a live emulator screenshot. The reliable path is physical device, operating system, Ryujinx Player 1 profile, saved mapping, and one repeatable game test.
What Ryujinx Controller Setup Actually Configures
A Ryujinx controller setup is a chain of input layers rather than a universal button list. The physical gamepad sends an event to Windows, Linux, macOS, or SteamOS. Ryujinx then exposes one or more device names inside its input profile. Player 1 selects one of those devices, applies a controller layout, and stores the button and axis assignments. Finally, the game interprets those assignments according to its own menu and gameplay actions. Keeping the layers separate makes the first setup much easier to read. If the operating system never sees the pad, changing a Ryujinx profile cannot repair it. If Ryujinx sees the pad but the game ignores a button, the problem is usually the selected profile, controller type, saved mapping, or a per-game override.
- Physical connection: cable, Bluetooth pairing, battery, and hardware switches.
- Operating-system layer: the pad appears and reports buttons, sticks, and triggers.
- Ryujinx layer: Player 1 selects a device and stores a controller profile.
- Game layer: the title reads the mapped console buttons and may apply its own rules.
- Launcher layer: Steam Input or another wrapper can expose a virtual gamepad instead of the physical name.
Prepare the Gamepad Before Opening Ryujinx
Start with a stable connection. A wired test removes Bluetooth and battery variables, so it is usually the fastest first pass. If you use Bluetooth, pair the controller before starting Ryujinx and close other remappers that may reserve it. You do not need keys, firmware, ROMs, or DLC to test controller visibility; those are separate setup concerns.
Map Player 1 Without Mixing Profiles
In the Ryujinx input settings, begin with Player 1 and the device name that matched your outside-emulator test. Choose the closest controller type, then map the buttons the target game actually needs: directional input, face buttons, both sticks, triggers, shoulders, plus, minus, and capture when relevant. Map the core controls first and save a baseline before adding motion, rumble, or alternate layouts. If a profile contains old bindings from another pad, create a clean profile or clear the conflicting fields instead of changing ten settings at once. The goal is not to create a perfect profile for every game; it is to prove that one stable device can drive one title.
- Keep Player 2 disabled until Player 1 launches and responds correctly.
- Use the same device name for every binding in the first profile.
- Move each stick through its full range and press triggers gradually while mapping.
- Save the profile, close the dialog, and reopen it to confirm the values remain.
- Record the working controller type and device name before trying a new Canary build.
Windows and Steam Input: Pick One Device Path
Windows controllers may be exposed through XInput, DirectInput, Bluetooth, or a remapper. Xbox-style pads are often straightforward, while PlayStation, Switch Pro, and third-party pads can appear under more than one name. Steam Input adds another layer: Steam may present a virtual Xbox-style device while hiding or transforming the physical pad. For a clean Ryujinx controller setup, decide whether the game will launch directly or through Steam, then select the device exposed by that same path. If a controller works when Ryujinx is opened directly but fails through Steam, compare the device name and profile rather than reinstalling the emulator.
- Use a direct USB connection for the first Windows mapping when Bluetooth is unstable.
- Close duplicate remappers and overlays before selecting a device in Player 1.
- When Steam Input is active, choose the virtual device that Ryujinx actually lists.
- Keep one profile for direct launch and one only when the Steam path genuinely exposes a different device.
- Do not run multiple wrappers at once while deciding which layer owns the buttons.
Linux, Steam Deck, and macOS Notes
The Player 1 workflow is shared across platforms, but the launch path changes what device Ryujinx can see. On Linux, reproduce the test in the same desktop session and permissions context used by the final shortcut. Steam Deck has Desktop Mode, Game Mode, and Steam Input; a controller that works in one mode may be presented differently in another. Test the AppImage or archive build directly in Desktop Mode before adding a Steam shortcut, then repeat the same profile through Game Mode. On macOS, keep Ryujinx focused while mapping and check any input or accessibility prompt from the operating system. Record the platform, launch path, controller mode, and device name for a useful comparison.
- Linux: keep the same desktop session, permissions, and launch command while testing.
- Steam Deck Desktop Mode: confirm the physical pad before adding Steam Input variables.
- Steam Deck Game Mode: select the virtual device if Steam Input is providing one.
- macOS: keep the emulator focused and review system prompts that affect input capture.
- Across platforms: save a known-good profile before changing the Canary build.
When to Move From Setup to Troubleshooting
Use this page for a first-time or clean setup. If Ryujinx lists the device but no buttons respond, check the selected device, Player 1 slot, controller type, saved profile, Steam Input, and per-game overrides. If the device is absent, verify the operating system and launch layer first. If controls broke after a Canary update, compare the same profile on the previous build. The dedicated controller-not-working guide covers those failure paths. Keep graphics, keys, firmware, game directories, and ROM files as separate tests.
Keep Controller Setup Separate From Keys and Game Files
A controller profile does not require downloading keys, firmware, ROMs, DLC, or mystery driver packages. If a game boots and the buttons are wrong, stay inside the input workflow. If the emulator cannot boot the title, use the installation or compatibility guidance instead. Back up a working profile before testing a new build, and do not delete the whole user folder to repair one button. This site does not host copyrighted game files, keys, firmware, or DLC.
Official Documentation Checks
Menu names and input behavior can change between emulator forks and Canary revisions. Use these first-party references for current setup context.
Ryujinx Controller Setup FAQ
How do I set up a controller in Ryujinx?
Test the gamepad in the operating system, open Ryujinx input settings, select Player 1 and the matching device, choose the closest controller type, map the core buttons and sticks, save, reopen the profile, and test one local game.
What should Player 1 use during the first setup?
Use one known-good controller and one device path. Leave Player 2, motion controls, extra wrappers, and per-game overrides alone until the default Player 1 profile survives a save and a game test.
Why does Ryujinx show two controller devices?
A physical pad and a virtual device from Steam Input or another remapper may both be visible. Choose the device exposed by the launch path you will actually use, and avoid mapping through two wrappers at once.
How do I set up a controller on Steam Deck?
Test the controller in Desktop Mode first, then repeat the profile through the final Game Mode launch path. When Steam Input is active, select the virtual gamepad name that Ryujinx lists rather than assuming the physical name will remain visible.
Why do the buttons map but the analog sticks feel wrong?
Check the selected controller type, axis order, full stick range, and dead zone. Rebuild the profile from a clean device selection before changing sensitivity, and test one stick at a time.
Should I create a separate profile for every game?
Start with the default profile. Add a named per-game profile only when a title clearly needs a different layout or special input, and confirm which profile is active before changing it.
Does controller setup require keys or firmware?
No. Keys and firmware affect game boot and system content, while controller setup concerns input devices and profiles. Keep those troubleshooting paths separate and use only your own legally obtained files.