Slow Roads Steam Deck Controls

Why update first

The developer said early Steam Deck control problems were caused by a misconfigured Linux runtime that tried to run through Proton. The correction should default to the native Linux build going forward, so an old install can create false control failures.

Patch 1.0.1 added axis input support for binary actions and may have fixed controllers that worked in menus but not in gameplay. Patch 1.0.2 improved controller and keyboard navigation in music and radio listings.

Deck test routine

Start in a menu and confirm joystick, d-pad, A/B selection and back controls. Then enter a road and test steering, throttle, brake, camera and autodrive. A controller can pass one layer and fail another.

If driving inputs feel reversed or ignored, reset in-game controls before editing Steam Input. Reconnect only the Deck's built-in controls for the first test; external pads can change controller index.

Comfort settings on Deck

Use steer assist and a stable camera first. The Steam page confirms both are configurable, and they reduce the learning load on a small handheld screen.

Keep traffic low while learning Deck controls. Once steering and braking are predictable, restore your preferred traffic density, speed and lane settings.

Reporting and limits

No official Steam Deck button layout was captured. Do not assume a diagram from another platform is correct; label community layouts 待确认.

A useful report should say whether the issue occurs in native Linux, with Steam Input on or off, in menus or only while driving, and include the game build.

Steps

1. 1Update SteamOS and Slow Roads.
2. 2Confirm native Linux launch, not Proton.
3. 3Test menu navigation and back/confirm controls.
4. 4Map steering, throttle, brake and camera.
5. 5Test autodrive, indicators and media UI.
6. 6Save the working profile.

Conditions

FAQ