Troubleshooting / symptom checklist
Machine Party controller double input
A single press skips a menu item, adds an extra player, or seems to control two seats. Use a one-controller baseline to find out where the extra input begins.
Close the game, disconnect spare input devices, and pause additional mapping tools. Relaunch through Steam with one controller and the default per-game setting. If repeated input remains, compare a standard gamepad layout and one Steam Input change at a time.
Separate double input from stick drift
Use one short press on a digital button, then release it completely. A repeatable two-step response is different from a stick that keeps moving after you let go. Neither observation proves the cause, but it tells you which comparison to run next.
Check whether the problem appears in Steam’s controller input test, the main menu, the Local lobby, or only one simulation. A controller that behaves incorrectly in Steam deserves a connection and hardware check before game-specific troubleshooting. A problem isolated to one trial should be described with that trial’s name and action.
If there are two physical players, ask the other person to leave their controls untouched during the test. Two simultaneous inputs can look like one duplicated command.
Create a clean one-controller baseline
- Exit Machine Party completely so the next test starts with a fresh device list.
- Disconnect spare pads, wheels, virtual-controller adapters, and unused handheld input devices.
- Pause tools such as DS4Windows or reWASD if they are active. Keep a note of their settings so you can restore your normal setup later.
- Check the remaining controller in Steam Settings → Controller. Use a known data-capable USB connection as a comparison if a wireless connection is unstable.
- Launch through Steam with the default per-game controller setting. In a fresh Local lobby, press a button once and count the joined player seats.
A successful baseline gives you a working comparison. Add devices or tools back one at a time, closing and relaunching the game between changes. Stop when the symptom returns; that last change is the next thing to investigate, rather than proof that the controller itself is faulty.
Compare Steam Input without stacking translators
Steam Input can translate a pad into a layout a game accepts. A separate mapper can also translate that same physical device. Depending on the configuration, the game may receive a physical device, a virtual device, keyboard commands, or more than one of those paths.
In Library → Machine Party → Properties → Controller, note the existing setting before testing an override. For an Xbox-compatible pad, compare the default setting with Steam Input disabled while other mappers remain closed. For a pad that needs translation, compare Steam Input enabled with the same single-tool baseline.
These are reversible comparisons, not a rule that Steam Input should always be disabled. Relaunch after each change and keep the configuration that actually produces one reliable input. If no change helps, restore the original setting before moving on.
Check whether the pad is sending keyboard commands
A community layout may assign keyboard keys or mouse actions to controller buttons. In a mixed-input Local session, that can make ownership harder to understand: you intended a gamepad seat, but its buttons may also act like the keyboard player’s controls.
Temporarily select a standard gamepad layout and remove unusual keyboard bindings from the test. Check actual player movement separately from menu navigation. Some shared menus accept input without establishing which device owns which player.
Once one pad is reliable, rebuild a keyboard-and-controller pair or use the four-player setup checklist. Keep each new device’s layout simple until all seats work.
If one controller still creates two players
Record the names or device types Steam displays and whether any virtual pads remain after you close your mapper. You do not need to uninstall every input utility to diagnose the issue; start by stopping its active translation and relaunching.
Try another controller, if one is already available, using the same port and settings. If the symptom follows one pad, inspect its profile and connection. If it follows the game regardless of pad, report that comparison with the game version and exact lobby steps.
If there is no repeated input but the next physical pad cannot join, switch to the second-controller not joining guide. That symptom needs a separate-device comparison rather than more double-input changes.
Double-input questions
Does this mean Machine Party has a confirmed input bug?
Not by itself. Duplicate mappings, hardware repeat, and game-specific input handling can look similar. This guide isolates those possibilities without labeling one as the confirmed cause.
Should I leave all mapping software disabled forever?
Use the smallest working arrangement first. Restore only the features you need and test after each addition. A tool that works in another game may still need a different per-game configuration here.
What should I report if it happens in only one round?
Include the simulation, the exact action, whether the lobby works normally, the controller model, connection, and Steam Input setting. Note whether the same action repeats with a standard gamepad layout.
This page provides editorial input-isolation advice, not a developer-confirmed universal fix. For the underlying local join flow, see the official couch co-op announcement. Use the Steam discussions to find the pinned current bug-report thread.