Gyro & Motion Controls on Steam Deck with Chiaki-ng
Chiaki-ng supports motion controls, and on Steam Deck you have two paths to gyro aiming: the Deck’s built-in gyro via Steam Input configuration, or a real DualSense connected over Bluetooth/USB whose gyro chiaki-ng reads directly. Both work — but exact behavior depends on your setup, so treat fine mapping details below as to be verified by testing on your Deck.
Path 1: Deck’s Built-in Gyro via Steam Input
- Follow our game mode setup guide to add chiaki-ng as a non-Steam game.
- In game mode, select the chiaki-ng shortcut → Controller icon → Edit Layout.
- Under Gyro Behavior, set it to As Joystick (right stick) or As Mouse, depending on what feels right for the game you’re streaming.
- Set Gyro Enable Button to Right Stick Touch or a grip button — gyro only active while aiming is the standard setup and avoids drift while navigating menus.
- Tune sensitivity in the same panel until flicks land where you expect.
Path 2: DualSense Gyro, Read Directly by Chiaki-ng
Chiaki-ng has native motion-control support for PlayStation controllers, including the DualSense’s gyroscope. If you pair a DualSense to your Deck (Bluetooth or USB):
- The gyro data travels the same path as on a real PS5 — no Steam Input translation layer in between.
- This is the most faithful option for games built around motion aiming.
- On Linux, pipewire is required for full DualSense haptics; gyro input itself doesn’t depend on it, but keep pipewire running anyway for the complete experience.
Which Path Should You Pick?
| Deck built-in gyro (Steam Input) | DualSense gyro (direct) | |
|---|---|---|
| Hardware needed | None — it’s already in your hands | A DualSense / DualShock 4 |
| Setup location | Steam controller layout | Mostly automatic once paired |
| Fidelity | Translated to stick/mouse — great, but translated | Native motion data, like a real PS5 |
| Best for | Handheld purists, travel | Doked play, competitive shooters |
Troubleshooting Gyro Issues
- Gyro does nothing: confirm you’re editing the game-mode controller layout for the chiaki-ng shortcut — desktop-mode and game-mode layouts are separate. Also check that chiaki-ng’s own controller mapping isn’t fighting Steam Input for the same device.
- Drift when not touching anything: tighten the gyro enable button (gyro active only while touching the stick) and raise the deadzone slightly.
- Steam Input seems to swallow the gyro: community-reported workaround is setting the shortcut’s Steam Input to Forced Off and letting chiaki-ng see the raw device — reported by the community, verify on your setup.
- Motion controls worked, then stopped after an update: upstream has repeatedly reworked motion-controller detection (including reset-detection fixes); re-check both the Steam layout and chiaki-ng’s mapping panel after updating. See also our controller troubleshooting page.
Frequently Asked Questions
Does chiaki-ng support gyro on Steam Deck?
Yes — chiaki-ng supports motion controls natively. On Deck you can use the built-in gyro through Steam Input configuration, or connect a DualSense whose gyro chiaki-ng reads directly.
Why does my gyro feel inverted or wrong?
Check the gyro direction and sensitivity in the Steam controller layout first, then chiaki-ng’s controller mapping panel. If you switched between the two gyro paths, reset the one you’re not using so they don’t stack.
Can I use gyro aiming and DualSense haptics at the same time?
Yes — they’re independent systems. On Linux, haptics need pipewire running; gyro input works regardless. Pair over Bluetooth (charged controller) or USB.
Gyro works in desktop mode but not game mode (or vice versa).
Steam keeps separate controller layouts per mode — configure the layout in the mode you actually play in. If Steam Input is interfering, try Forced Off for the shortcut and let chiaki-ng handle the raw device; verify what works on your Deck.