Check joystick support and setup problems · Early Access 0.1.1 reference
Groundwork Simulator: Joystick Not Working
Quick Answer
If your Groundwork Simulator joystick is not working, check that Steam has installed the official 0.1.1 hotfix before following launch-day advice. The developer names improved T.16000M detection and configuration, while still listing some joystick compatibility and input problems as unresolved. A zero-device count, one working stick, and incorrect bindings are different observations: record your exact models and what each device does. Do not assume the T.16000M change fixes FarmSticks, an X56, or every dual-stick combination. The same notice warns that connecting or disconnecting PS4, PS5 or Steam Controllers can cause crashes. Finish playing and close the game before changing that hardware setup. If the problem remains, report it through the developer’s linked Discord with V0.1.1 in the title and the device details below.
- Reading time
- 6 minutes
- Difficulty
- Device and version check
- Checked
- 2026-10-24
On this page
Guide details
Before you begin
Check the 0.1.1 T.16000M improvement, separate device detection from bindings, and identify joystick problems that remain unresolved.
Early Access 0.1.1 developer notice and dated Steam reports, checked October 24, 2026. No personal hardware test or universal repair is claimed.
- Status
- Developer 0.1.1 and dated player reports
- Edition
- Early Access 0.1.1 reference
- Platform
- PC · Steam Early Access
- Checked
- 2026-10-24
- Check note
- Version-specific statements checked against the original developer notice. No personal hardware test, complete axis mapping or universal repair is claimed.
Before you set out
Prerequisites#
- Use Groundwork Simulator by XYZ STUDIO, Steam app 5306540. Instructions for Construction Simulator, Out of Ore or a flight simulator are not evidence for this game.
- Record the installed game version and the full model name of each connected input device. Do not infer a version from the date of a video.
- Preserve a working control setup and save progress before investigating a different configuration. This checklist does not require deleting saves or installing a mapper.
Route 01
Groundwork Simulator joystick not working: first checks#
Start with the installed version and one clearly described symptom. These checks help distinguish an old launch report from the behavior you can actually observe now.
Check the released hotfix before changing bindings#
Let Steam finish any pending game update, then note the version you can identify in your installation. Use the official 0.1.1 notice as the named reference for this guide. An older complaint can explain the problem that prompted a patch without describing the result after that patch. If you cannot establish your installed version, keep it unknown in your notes rather than labelling the current behavior a confirmed 0.1.1 regression.
Write down the detection result and the movement result separately#
Record the number of devices the game shows, whether each stick moves machinery, and whether the expected axes or buttons can be assigned. A stick that moves something while the device counter remains zero is partially responding; it is not the same observation as no input at all. Keep those details together. They help avoid changing a working assignment while trying to solve a different part of setup.
Compare the named model, not just the manufacturer#
Check the full device name against the developer’s named T.16000M change. Two products carrying the Thrustmaster name are not interchangeable evidence of compatibility. Likewise, a report about a mixed pair does not establish what two identical sticks will do. For a dual setup, label your notes left and right, with the model of each. Record buttons and axes separately when only one kind of input responds.
Stop a risky test before reconnecting hardware#
The developer specifically lists crashes associated with connecting or disconnecting PS4, PS5 or Steam Controllers. Do not recreate that operation repeatedly during an important session to see whether it fails again. Save if the game is responsive, exit normally, and make any intended hardware change with the game closed. This is a precaution based on the warning, not a claim that a particular reconnection order repairs joystick detection.
Pocket list 02
What 0.1.1 does and does not establish#
- T.16000M: the developer says detection and configuration were improved in 0.1.1. This is the first version-specific check for that model. It does not provide a complete default-axis table or guarantee that every additional peripheral and dual-stick arrangement works.
- Other joystick models: some compatibility and input problems remain on the official known-issues list. Do not turn the absence of your model from the fixed line into proof that it is supported or unsupported. Record the actual result and use the official support route for the unresolved case.
- Walking with a controller: the notice separately mentions smoother camera movement. That statement is about walking-camera behavior; it does not demonstrate that excavator axes, a second joystick, or every machine binding was corrected.
- A later patch: the developer plans more controller and keybinding work. A plan is a reason to follow the official announcements, not a delivered fix or a reliable date for deciding when a particular device will work.
Why a zero-device count can coexist with partial input#
The original October 22 dual-joystick thread reports both a 0/2 counter and partial controls. Replies describe cases where one side moves machinery or buttons respond while the second stick cannot be configured. These are historical player observations, not a diagnosis of the input system and not proof that your hardware is defective. Their practical value is the distinction: report the displayed count and the actual response instead of compressing everything into “nothing works.” Because these posts began before the released hotfix, use them to describe a matching symptom, then compare your own current version. Do not use their launch-day date to conclude that no fix has since shipped.
Pocket list 04
Make one useful comparison without losing the baseline#
- Before changing anything, record the working and failing inputs. For example: left-stick axis responds, right-stick buttons respond, right-stick axis does not, and the displayed count is zero. Replace the example with your actual observations; do not assume those are the normal symptoms for every player.
- Change only the setting or hardware arrangement you intended to examine, with the game closed for hardware changes. Note what changed. If several devices, bindings and controller settings change together, a different result will not tell you which change mattered.
- After returning to the game, compare the same observable actions. Count successful assignments and machine responses separately. If the result is unchanged or worse, stop that branch rather than accumulating additional unverified fixes. Keep your previous settings available so you can restore the baseline.
- Do not label the comparison successful merely because a setup screen opens. The original problem may be a second axis, a particular machine, or a conflict while looking around. Describe the action that now works and any part that still fails.
What about Steam Input changes and joystick mappers?#
A suggested workaround needs an exact device, game version, setup procedure and confirmed result before it becomes a dependable instruction. The inspected temporary-mapper thread does not establish that complete chain, so this guide does not supply a mapper download or tell you to replace your normal input setup. For the same reason, disabling Steam Input is not presented here as a universal repair. If you already tried a setting, include it in your report with the result; a failed attempt is useful context. Avoid importing a configuration for another game simply because its equipment looks similar. Groundwork’s official known-issue status is a stronger starting point than an unrelated simulator’s control tutorial.
Pocket list 06
Record a useful 0.1.1 bug report#
- Identify the build you actually checked, your operating system, and the complete device list. Include the left/right model names in a two-stick setup, plus other input peripherals that are connected. If the build is uncertain, say so.
- Describe the smallest sequence that exposes the problem: starting the game, opening setup, attempting an axis assignment, or operating a particular machine. Say whether the game continues running, ignores the input, assigns a different action, or closes.
- Include the displayed device count and actual button/axis responses. A screenshot of the relevant setup screen or a short clip can explain the difference, provided it contains no private account information.
- List changes already tried and their results, including whether the same symptom remains after the official update. Keep a support reply separate from a confirmed fix: a request for more information does not establish that the issue has been resolved.
Field questions
Joystick support questions#
- Does 0.1.1 fix every dual-joystick setup?
- No universal result is established. The official notice names T.16000M improvements and also retains some joystick/input issues. Match the model and current behavior before drawing a conclusion.
- Should I follow an Out of Ore or Construction Simulator setup video?
- Those are different games. Such a video does not establish Groundwork’s current assignments or compatibility. Use its ideas only as separate research, not as verified instructions for this problem.
- Do I need to delete my save or reinstall Windows?
- Neither action is supported by the inspected sources as a repair for this task. This guide’s checks do not require either. Keep the device/build evidence and seek the developer’s advice for an unresolved case.
- Has the next controller patch already solved it?
- The inspected 0.1.1 notice describes further work as planned. Check a later official release note for your exact issue before treating that future work as delivered.