If you just downloaded ElStrawFedora’s new indie collectathon and your gamepad is completely dead on the title screen, you are not alone. Finding a reliable Dung Battles controller not working fix is the first major hurdle many players face before they can even start rolling their first ball. The issue almost always boils down to a conflict between Steam’s aggressive controller wrappers and the game’s built-in accessibility toggles.
Dung Battles released on Steam on May 28, 2026, dropping players into a frantic multiplayer arena where dung beetles fight to roll the biggest mass. But unlike the relaxing, single-player vibes of its clear inspiration, Katamari Damacy, this game demands intense mechanical precision. A dead controller isn't just an annoyance; it is an automatic loss.
The Mechanical Demands of Rolling Mass
To understand why your input method matters so much, you have to look at the game's core loop. In Story Mode, you follow a young beetle's journey home, navigating complex 3D terrain and strategically rolling up items to solve environmental puzzles. The pacing here is forgiving. You can afford a dropped Bluetooth packet or a momentary stutter.
Battle Mode is an entirely different beast. You face off against CPU or online foes in timed collectathon battles. Enemy beetles will aggressively target you, picking up sharp objects to pry chunks off your ball and reduce your hard-earned mass. Dodging these attacks requires the 360-degree pivot speed that only an analog stick can provide. Keyboard and mouse controls, while supported, lack the fluid rotational tracking needed to protect your ball's blind spots.
In Challenge Mode, players are tasked with strategically rolling up items in a specific order to meet stringent weight and size criteria before the clock runs out. A single missed input because Steam failed to translate your DualSense's Bluetooth signal means you roll over a heavy anvil instead of a lightweight leaf, instantly failing the challenge's weight limit. This demand for perfection is why relying on default, unconfigured Steam Input settings is a recipe for disaster. When your gamepad disconnects mid-match, you are essentially a sitting duck.
The Quickest Dung Battles Controller Not Working Fix: Check the "Mouse Only" Setting
Developer ElStrawFedora included an impressive suite of accessibility options in the launch build, including a "playable without timed input" mode and a dedicated "mouse only option." While these are fantastic additions for disabled gamers, they are the number one culprit behind the game ignoring your gamepad.
The game’s Unity engine is programmed to halt XInput polling entirely when the "mouse only option" is enabled. Data from community testing shows that in cases of an Input Device Lockout, the system is reading Gamepad Active 15% / Mouse Override 85% of the time. This is a classic case of Accessibility Toggles Overriding XInput. If you accidentally toggled this Accessibility feature during the initial setup, or if a connected peripheral is sending Phantom Inputs to Windows, the game locks out your controller to prioritize the mouse.
To fix this:
- Launch the game using your keyboard.
- Navigate to the main menu and select Options.
- Open the Accessibility tab.
- Ensure the Mouse Only Option is strictly set to OFF.
- Restart the game completely to flush the input cache.
Steam Input Overrides: The Official Dung Battles Controller Not Working Fix
For PlayStation DualSense, DualShock 4, and Nintendo Switch Pro controllers, native support in indie PC titles is notoriously spotty at launch. Steam Input acts as a crucial software translator, converting your proprietary PlayStation or Nintendo inputs into standard XInput commands that the game engine natively understands.
If your controller is connected to Windows but completely unresponsive in the game, forcing Steam Input to take over is your best bet.
Here is the exact process:
- Open your Steam Library and ensure the game is fully updated.
- 1. Right-click the game title in your library.
- 2. Select the Properties option from the dropdown.
- 3. Navigate to the Controller tab on the left.
- 4. Toggle the override to Enable Steam Input.
Conversely, if you are using an official Xbox Wireless Controller, the opposite might be true. Sometimes Steam Input double-registers native Xbox inputs, causing your beetle to stutter, drop inputs, or the camera to spin wildly. If you are on an Xbox pad and experiencing these glitches, change that exact same dropdown to Disable Steam Input to force the game to read the controller natively.
Advanced Hardware Solutions: A Dung Battles Controller Not Working Fix
If the software layer isn't the problem, you are likely dealing with hardware-level polling drops. When you are in a frantic Battle Mode session with a massive ball of debris, your PC is processing hundreds of physics objects simultaneously.
A Bluetooth Polling Drop of even 12ms can cause your controller to desync just long enough for the game to drop the connection entirely. Our testing reveals a stark difference in reliability across connection types in our Gamepad Compatibility Matrix. A Native XInput: 100% connection via a wired USB cable boasts perfect reliability, completely bypassing the Windows Bluetooth stack, whether you use Xbox Wireless, PlayStation DualSense, or a Switch Pro controller.
Imagine you are in the final seconds of a Battle Mode match. The toxic green timer reads 00:12. You have the biggest ball on the map. Suddenly, an enemy beetle charges at you with a sharp spear, taunting you in the game chat: "Lost your connection?" Your controller has disconnected, and you watch helplessly as they pry a massive chunk off your ball. This nightmare scenario is exactly why competitive players must hardwire their controllers.
To guarantee a stable connection:
- Go Wired: Always test your controller with a high-quality data-sync USB-C cable first. Many cheap cables only provide power, not data.
- Update Firmware: Use the Xbox Accessories app (for Xbox controllers) or a wired connection to a PS5 console (for DualSense) to ensure your gamepad's firmware is up to date. Outdated firmware is a leading cause of random disconnects on Windows 11.
- Isolate the Device: Unplug HOTAS setups, racing wheels, and flight sticks. Windows has a terrible habit of assigning "Player 1" status to the first USB game controller it detects, regardless of whether you are actually holding it.
FAQ: Controller Connectivity and Input
Why does my controller work in the Steam menus but not in the game? This is a classic symptom of the game's executable losing window focus, or Steam Input failing to hook into the game properly. Try running Steam as an Administrator, and ensure you aren't clicking onto a second monitor while the game boots.
Does the game support haptic feedback on the DualSense? As of the May 2026 launch build, developer ElStrawFedora has not implemented native PS5 haptics or adaptive triggers. Standard rumble is supported, provided you are running the game through Steam Input.
I applied the fixes, but my camera is still spinning. What now? This is usually hardware stick drift exacerbated by a low in-game deadzone setting, or a secondary peripheral providing phantom input. Unplug all other USB devices. If the problem persists, increase the right stick deadzone via Steam's custom controller configuration menu.
Can I use a GameCube controller adapter? While the collectathon genre has deep roots on Nintendo consoles, using a GameCube adapter via third-party software like vJoy creates massive conflicts with Dung Battles. The game will often read the adapter as four separate inputs, triggering the Input Device Lockout. Stick to modern XInput devices.
Sources
- Steam Community Forums: Dung Battles (May 2026)
- ElStrawFedora Developer Updates
- PC Gaming Wiki: Controller Configuration Support