Guides → Controller settings
The Sinking City 2 controller settings and not-working fix
Checked August 26, 2026: the Windows Steam listing currently shows Full controller support, DualShock Controller Support and DualSense Controller Support. If input is missing, isolate whether the controller, Steam or the game loses it before changing a second layer.
DualSense boundary: Team Frogwares says, “DualSense features don't work when the controller is connected via Bluetooth. Use USB connection only to ensure gamepad features work properly.” This does not say every Bluetooth controller is unsupported and does not prove that basic DualSense input always fails over Bluetooth.
What the current sources actually verify
| Layer | Verified evidence | Do not infer |
|---|---|---|
| Windows Steam listing | The store lists Full controller support, DualShock Controller Support and DualSense Controller Support. | Those capability labels do not promise a particular community layout, sensitivity preset or wireless feature set. |
| DualSense features on Windows | Team Frogwares says DualSense features don't work when the controller is connected via Bluetooth and instructs players to use USB. | That does not say every Bluetooth controller is unsupported and does not prove that basic DualSense input always fails over Bluetooth. |
| Steam Input | Valve provides global and per-game controller configuration through Steam. | Steam Input is a Valve layer, not a Frogwares-guaranteed cure. Test one state and keep a route back to the previous state. |
| Console versions | The game is sold on PlayStation 5 and Xbox Series consoles. | The Steam Input steps on this page apply to Windows Steam, not to console system menus. |
Button layout and in-game help
The current primary-source set does not publish a verified full button map for every supported controller. Open the Pause Menu → How to Play for the game's current tutorial, and use Steam's detected device view to identify the controller layer. Do not treat a third-party layout as an official default.
Choose the symptom first
A missing device, missing game response, wrong prompts and missing DualSense features are different failures. Route the observed symptom before applying a change.
| Observed symptom | Next check |
|---|---|
| Steam does not detect the controller | Stop before changing the game. Reconnect the device, test the cable or receiver and confirm detection in Steam first. |
| Steam detects it, but the game does not respond | Launch with the controller already connected, restore the per-game default, then compare one Steam Input state at a time. |
| Buttons work, but prompts or mappings are wrong | Record which device Steam reports and which prompts appear. Avoid copying an unverified button map; test the current per-game controller layer. |
| DualSense input works, but its features are missing | Use a USB data cable for the Frogwares-supported feature path. Do not turn the statement into a claim about every Bluetooth controller. |
| All game sounds are coming from the DualSense gamepad speaker | Use the Team Frogwares audio-output workaround below before changing controller drivers or game files. |
Reversible Windows Steam test ladder
- Record the baseline. Note the controller model, USB/Bluetooth/receiver connection, whether Steam sees it and what the game currently does. Photograph any per-game Steam controller setting before changing it.
- Connect before launching. Exit the game, connect the controller, wait for Windows and Steam to recognise it, then launch again. For DualSense features, use a known data-capable USB cable as Frogwares instructs.
- Confirm Steam sees the device. Open Steam's controller settings and confirm the controller is present and responds there. If Steam cannot see it, the failure is below the game layer.
- Restore the per-game default. Remove an old community layout or unusual per-game override and retest the same input from Steam's default state. Keep the recorded baseline so the change is reversible.
- Test one Steam Input change. Change one controller-layer setting, test the same input in the same place, and compare it with the baseline. Do not combine a new layout, driver utility and game setting in one attempt.
- Revert or escalate. If the test makes no difference or makes prompts worse, restore the previous value. Then capture the device, connection and failed step for Steam Support or Frogwares Support.
Safety boundary: this path does not require registry edits, security changes, deleting device drivers or installing an unofficial controller utility. Steam Input is a Valve layer; a Frogwares game issue and a Windows device issue can require different support routes.
Calibrate sensitivity without inventing a “best” preset
There is no universal best sensitivity or deadzone supported by the current first-party sources. Record the baseline, change one aim or camera control by a small amount, and repeat the same slow-tracking, turn and fine-aim test. If the result gets worse, restore the previous value before changing another control.
All game sounds are coming from the DualSense gamepad speaker
Team Frogwares says to open Windows sound output, switch the output to the gamepad and back to your preferred headset or speakers. Test audio again before changing controller software. This audio-output workaround is separate from the USB requirement for DualSense features.
Use the page that owns the next issue
Controller FAQ
Does The Sinking City 2 support controllers on PC?
Yes. The current Windows Steam listing marks Full controller support and separately lists DualShock and DualSense controller support. Those labels do not establish a universal button map or best sensitivity preset.
Why are DualSense features missing over Bluetooth?
Team Frogwares says DualSense features do not work over Bluetooth and tells Windows players to use USB for those features. The statement does not say every Bluetooth controller is unsupported or prove that basic input always fails wirelessly.
What should I do if the game does not detect my controller?
Connect it before launch, confirm Steam detects and responds to it, restore the per-game default, then test one Steam Input state at a time. Revert an ineffective change before trying the next layer.
Should I enable or disable Steam Input?
There is no single source-backed state for every controller. Start from the current per-game default, record it, test one alternate Steam Input state against the same symptom and restore the previous value if it does not help.
What are the best controller sensitivity settings?
No first-party universal preset was found. Start from your current value, change one axis or sensitivity control by a small amount, repeat the same camera and aiming test, and revert if tracking becomes worse.
Sources and verification boundary
- Official Steam product page — current Windows controller capability labels.
- Team Frogwares pinned full-game FAQ — DualSense USB and audio-output guidance.
- Valve Steam Input player documentation — global and per-game controller configuration layer.
Sources checked August 26, 2026. No current first-party page in this set supplies a universal sensitivity preset, deadzone value or complete game-specific controller map.