Maintenance / launch build

Fixes & troubleshooting

Start with the reversible checks below. Machine Party is newly released, so a clean bug report may be more useful than an unverified “fix” copied from another game.

Published August 1, 2026Last verified August 1, 2026Launch build

Common problems

Open an issue for a short, ordered checklist. Stop once the problem is gone.

Room ID fails or multiplayer will not connect
  1. Confirm the host is still inside the lobby; IDs are not permanent server addresses.
  2. Copy the full numeric ID again with no spaces before or after it.
  3. Both players should update the game and restart Steam in online mode.
  4. Have the host create a new room, then test with one guest before inviting everyone.
  5. Temporarily allow Machine Party and Steam through the operating-system firewall. Do not disable the firewall entirely.
  6. If one network consistently fails, test a different host. This helps separate a host/network issue from a game-wide issue.

There is no public matchmaking fallback at launch; you must join a valid private room.

Controller is connected but not recognized
  1. Connect the controller before launching the game and close other controller-mapping tools.
  2. In Steam, open Library → Machine Party → Properties → Controller. Test the default setting first, then try enabling Steam Input.
  3. For an Xbox-compatible pad, also test with Steam Input disabled; double translation can cause missing or repeated inputs.
  4. Disconnect extra pads, wheels, virtual controllers, and handheld companion devices, then relaunch with one controller.
  5. Confirm the controller works in Steam’s own input test.

At launch, local co-op is not available, so plugging in several controllers will not create several local subjects.

Game crashes on launch or during a round
  1. Steam Library → right-click Machine Party → Properties → Installed Files → Verify integrity of game files.
  2. Install the latest stable graphics driver, then restart the computer.
  3. Disable overlays one at a time: Discord, GPU recording, performance monitoring, and third-party injectors.
  4. Make sure the GPU supports Vulkan. The official minimum requirements explicitly require Vulkan support.
  5. Try a clean reboot and close heavy background applications. The Windows minimum lists 8 GB RAM.

If one specific minigame always crashes, include its name in the bug report.

Black screen, broken textures, or severe graphical artifacts
  1. Update the graphics driver from Nvidia, AMD, or Intel rather than relying only on Windows Update.
  2. Verify game files and remove any unofficial launch options.
  3. Switch between fullscreen and windowed mode if the menu remains readable.
  4. On laptops, force the game to use the discrete GPU through Windows Graphics settings.
  5. Check the pinned “Temporary fix for graphical issues” thread in the Steam discussions for the developer’s newest workaround, since launch fixes can change quickly.
Steam invite option does not appear
  1. Create the in-game room first, then open the overlay with Shift + Tab.
  2. Use the in-game numeric room ID if the overlay still offers no invite action.
  3. Make sure Steam Overlay is enabled for both Steam and Machine Party.
  4. Set Steam Profile → Privacy Settings → Game Details to Friends Only or Public.
How to report a bug to the developers

Use the pinned “Bugs & Issues — Report them here” discussion. Include:

  • A one-line summary and the exact minigame or menu where it happened.
  • Steps that reproduce the problem.
  • Expected result versus what actually happened.
  • Windows or Linux version, CPU, GPU, RAM, controller model, and game version.
  • Whether you were host or guest and how many players were connected.
  • A screenshot, short video, and the latest game log if available.

Do not post passwords, Steam login details, private IP addresses, or another player’s personal information.

System checks use the official requirements. Community workarounds are labeled conservatively because patches may make launch-day advice obsolete.