Yes — over the hill supports gamepads at launch, and the developers treat gamepads as a first-class input method. Keyboard and mouse are supported alongside them, and those two are the input methods prioritised for release. Steering wheels and force feedback are explicitly not part of the launch build, and no future date has been confirmed for them. The Steam store page states the gamepad side of this in three separate places.
| Steam store listing | What it records |
|---|---|
| Full controller support | The store page lists over the hill as fully supporting controllers |
| Xbox controller | Named as a supported controller type |
| PlayStation controller | Named as a supported controller type |
| Developer recommendation | The page records that the developers suggest using a controller |
Full controller support. Xbox controller. PlayStation controller. The developers suggest using a controller. — over the hill Steam store page feature list
What that listing does not do is promise that any controller will work without configuration. The store page states support in the way store pages do. The detail about how to make a specific device work came from the developer directly during the demo period, and that sequence is the more useful half of the answer.
Keyboard and mouse remain a first-class option
It is worth stating plainly that the game is not controller-only. The developers describe keyboard and mouse, and gamepads, as the two input methods supported and prioritised at launch. A controller is a recommendation, not a requirement, so nothing on the store page or in the developer guidance says a keyboard-only player is excluded.
The store page user tags also carry a controller tag, which is consistent with the developer recommendation in the feature list. Nothing in the available material describes a controller-only UI, a console-style button prompt scheme, or any requirement that changes the interface depending on input method. The camera perspective is recorded as a bird's-eye view with direct control, which reads the same on either input method.
The five-step official troubleshooting order
When a gamepad was not working during the demo, the developer gave a numbered sequence in June 2026. The order matters, because each step can invalidate the result of the previous one.
| Step | What to do |
|---|---|
| 1 | Open the game's properties from your Steam library |
| 2 | Toggle the Steam Input setting — if it was on, turn it off; if it was off, turn it on |
| 3 | Restart the game completely |
| 4 | Before restarting, leave only the controller you are testing connected, and unplug other controllers, wheels and sticks |
| 5 | If it is still wrong, go to Steam Settings, then Controller, show advanced settings, and enable the matching controller type |
Step four is the one people skip and the one that isolates the problem. Plugging in a wheel, an extra pad or a stick alongside the controller you are testing means the game can enumerate more than one device, and the symptom you are chasing may belong to a device you did not intend to use. Unplugging everything else removes that variable before the restart, not after.
Step five is the last resort in the official order, not the first move. Steam's advanced controller settings sit below the default layer, so enabling the matching controller type there is a targeted fix for a device Steam is not currently presenting correctly.
Why there is no single universal setup
The developer has said explicitly that there is no single universal controller setting, and gave the reason: different devices expose different input modes. That is the whole explanation for why the fix is a sequence rather than a single toggle.
A universal setup would require every controller to present itself to the game in the same way, which is not true of the wider device market. What the sequence actually does is walk through the layers where a device can be misdetected — Steam Input, the process itself, the set of connected devices, and finally Steam's per-device-type enablement.
Change one thing, then test
The developer also advised against changing everything at once. The guidance is to make one change, then test the game again before making the next. Bundling several changes into a single attempt destroys the information you need, because a working result no longer tells you which change fixed it.
This matters here specifically because the official order contains four separate variables. One change per attempt turns four unknowns into four separate tests.
Rebinding buttons inside the demo
Button rebinding was possible inside the demo, with one significant condition attached. Rebinding only took effect if you navigated the Controls settings using the gamepad itself. Entering that menu by any other route would show the buttons as locked.
That detail matters more than it first appears. A player who rebinds with keyboard navigation and sees locked buttons has not found a bug — they have found the documented condition. The demo's own access method was treated as part of the input model rather than a convenience, and the gamepad was the expected way to reach that screen during a demo phase.
Whether the same requirement survives into the full release is not something the available material states. The demo closed to public access on June 30, 2026, so this is recorded as demo-period behaviour rather than as confirmed launch behaviour.
8BitDo and other devices
The developer named 8BitDo hardware as an example of a family that may need the corresponding controller type enabled in Steam. That is the specific step five of the official sequence, applied to a named brand rather than in the abstract.
It is important to read that as an example rather than a compatibility list. The developer did not publish a tested device list, did not confirm any specific model as verified, and did not rank devices. So the useful takeaway is that third-party pads from that category are known to appear in situations where Steam's per-type enablement matters, not that any particular product is certified.
Alongside it, the store page names Xbox and PlayStation controllers as supported types. Those two families are the officially listed ones in the feature bullet, which makes them the lowest-friction expectation.
Confirmed support versus device-specific reports
It helps to keep the evidence levels apart when reading controller discussion. The store page listing and the developer's five-step sequence are official. The 8BitDo example is also official, because the developer raised it, but it is an illustration inside the official guidance rather than a tested-device claim.
Community reports cover the rest — individual devices working or not working on individual setups. Those are useful for narrowing a search but carry none of the authority of the developer's own sequence. If a fix appears in a forum post, run the official five steps first and see how far that gets you.
What remains unknown before release
Several controller details are still 待确认. The launch-build control mapping is one: the demo sequence tells you how to get a device recognised, but the final layout of the controls is not published. Whether the demo's gamepad-navigation requirement for the Controls menu carries into release is also 待确认, as is the list of controller models the developers actually tested.
One item is genuinely open rather than merely undocumented: whether Steam Input's launch default value changes. The official sequence instructs you to toggle it in either direction, which implies the default is not reliable as shipped — but whether release flips that default is 待确认. Until these are answered, treat the five steps as the working procedure rather than expecting any device to work untouched.