Steam currently declares full controller support for Waterpark Simulator and lists PlayStation controller categories. If a pad fails, identify whether the problem is device detection, game focus, Steam Input translation, incorrect glyphs, one binding, or a particular construction screen. Those boundaries are more useful than a blanket statement that controller support is broken.
The controls guide provides a first-session baseline. Use this page after you can name the exact action that does not work.
Confirm Windows and Steam detection
Connect the intended controller before launching the game. Verify that Windows and Steam detect the correct model. Disconnect duplicate, virtual, or unused input devices for the first test.
Open Waterpark Simulator from the Steam library and keep the game window focused. Test menu navigation before loading a park. If no input works in the menu, the failure occurs earlier than any save or build-mode action.
Record wired or Bluetooth connection, controller model, and any remapping software.
Return to one controller path
Steam Input can help unsupported layouts, but it can also translate a device the game already handles. Check the Waterpark Simulator controller override in Steam properties and write down its current state.
Begin with the existing default. If input is absent, test one Steam Input state change and restart the game. Do not cycle through community layouts, driver tools, and in-game remaps at the same time.
If a community layout is active, inspect its bindings before removing it. Preserve a screenshot so you can restore a useful custom setup.
Separate global and single-action failures
If movement and menus work but one interaction fails, open the current binding screen and compare the live prompt. Restore only that action to its default where the interface permits it.
Test station interaction, tool use, pause, and cancellation separately. A held tool may need an exit action before another prompt becomes available.
If every action stops after clicking another window, refocus the game. Capture whether keyboard and mouse still work in the same state.
Test building as its own subsystem
Enter a disposable construction area and try selection, placement, rotation, confirmation, and cancellation. Then check custom slides separately. A controller that works in first-person play may expose a screen-specific pointer or focus issue in an editor.
Record the exact panel and selected object. Do not rebuild an important attraction to diagnose an input problem.
If mouse input completes the same action, include that comparison in a support report. It narrows the issue to controller navigation rather than the construction feature itself.
Resolve switching glyphs and drift
Prompts may change when the game receives mouse or controller input. Move the mouse aside, close software that emits virtual input, and inspect the controller for stick drift. Reconnect one device and test again.
For PlayStation pads, note whether displayed glyphs match the physical buttons and whether the connection is wired, wireless, or translated. Steam’s category declaration does not guarantee that every connection displays identical icons.
Adjust dead zone or sensitivity one field at a time and retest the same movement. Preserve the original values.
Avoid broad resets first
Do not delete save data, the complete game-data folder, or Windows drivers to solve one binding. Verify installed files through Steam only after preserving evidence, and keep personal configuration changes documented.
If the issue began after adding a mod, return to the unmodified baseline described on the mods page. A UI or input mod can change symptoms without the base game failing.
Steam Deck uses Proton and a separate compatibility context. Follow the Steam Deck guide instead of treating Windows pad support as native Linux support.
Build a precise controller report
Provide controller model, connection, Steam Input state, game version, Windows version, active layout, exact screen, failed action, displayed prompt, and whether mouse or keyboard succeeds. Include a screenshot or short non-private capture.
Say whether the issue occurs from launch, after alt-tab, after opening build mode, or only in one park. Submit reproducible public-build problems through CayPlay’s official support route.
Controller troubleshooting should end with one failing layer. Once you know that layer, a narrow configuration change or developer report is safer than a system-wide reset.