How to Fix Blades and Battles Controller Not Working on Steam: Full Troubleshooting Guide

So when the game refuses to see your controller on Steam, it kills the mood fast. Xbox pad, DualShock 4, DualSense, Switch Pro, or some no-name USB gamepad from a drawer, the result is the same: you mash buttons and your knight just stands there.

The good news is that your controller is almost certainly not dead. This is a software-layer headache, and I’ve put together every fix worth trying, in the order I’d try them.

How to Fix Blades & Battles Stuttering, Frame Drops, and Performance Lag

Why Steam Games Suddenly Go Deaf to Your Controller

Most PC games read controllers through one of two systems:

• XInput: the modern standard, built around Xbox controllers.
• DirectInput: the older standard, common on legacy and third-party pads.

Steam sits between your hardware and the game through Steam Input, which translates non-Xbox controllers into something the game understands. When that translation breaks, the game hears nothing. The usual culprits:

Now the fixes.

Step 1: Check That Windows Can Actually See the Controller

Rule out the operating system first. If Windows can’t see the pad, no Steam setting will help.

1. Unplug and replug the controller. If it’s wired, try a different USB port, ideally one on the back of the PC, not a front-panel port or hub.
2. If it’s wireless, open Windows Bluetooth settings and make sure it says Connected, not just Paired. Those aren’t the same thing, and this one has burned me more than once.
3. Hit the Windows search bar, type joy.cpl, and press Enter to open the “Setup USB Game Controllers” utility.
4. If your controller isn’t listed, you have a driver or physical connection problem.
5. If it’s listed, select it, click Properties, then move the sticks and press buttons. If the indicators react, the hardware is fine and the blame moves to Steam or the game.

Step 2: Turn On the Right Global Steam Input Settings

If you use a PlayStation or Switch controller, Steam needs to be told to handle it.

1. Open Steam, click Steam in the top-left, then Settings.
2. Go to the Controller tab in the sidebar.
3. Under External Gamepad Settings, enable the option that matches your pad:

• DualShock 4 or DualSense: Enable PlayStation Controller Support
• Switch Pro: Enable Steam Input for Switch Pro Controllers
• Generic pads: Enable Steam Input for Generic Controllers

4. Close the window, restart Steam, and launch the game.

Step 3: Override Steam Input for Blades & Battles Only

Global settings can be overridden per game, so force the issue on this title.

1. In your Steam Library, right-click Blades & Battles and choose Properties.
2. Open the Controller section.
3. Find Override for Blades & Battles and switch it from “Use default settings” to Enable Steam Input.
4. Fully close the game if it’s running, then relaunch.

Still nothing? Do the opposite. Set the override to Disable Steam Input. Some XInput-native controllers work better when Steam stops translating and lets the game talk to the hardware directly. It sounds backwards, but it works more often than you’d expect.

Step 4: Run Steam as Administrator

If the game runs with elevated rights and Steam doesn’t, Windows blocks Steam’s input from reaching the game window. Giving Steam admin rights often fixes it instantly.

1. Exit Steam completely (Steam > Exit, or end it in Task Manager).
2. Right-click the Steam shortcut, or find it in the Start Menu, and choose Run as administrator. Accept the prompt.
3. Launch Blades and Battles and test your controller.

If that works, make it permanent: right-click the Steam icon, open Properties, go to the Compatibility tab, check Run this program as an administrator, and hit Apply.

Step 5: Kill the Mapping Software Fighting Steam

If you run mapping tools alongside Steam, they’re probably arm-wrestling over your controller, and the game gets duplicate or conflicting signals.

• DS4Windows users: Close Steam first. In DS4Windows, make sure Hide DS4 Controller is enabled so Windows doesn’t see both the raw pad and the fake Xbox one. Better yet, shut DS4Windows down completely. Modern Steam handles DualShock 4 and DualSense on its own, and it does it well.
• reWASD users: Clear or unmap any profiles tied to your controller before starting Steam, or close the program from the system tray while you play.

Less software in the chain means fewer things to break.

Step 6: Use Big Picture Mode as a Diagnostic Tool

Big Picture Mode has its own solid controller detection, so it’s a handy test.

1. Click the TV-shaped icon in the top-right corner of Steam.
2. Navigate the menus with your gamepad.
3. If the pad works in the menus but dies in-game, the problem is in the game’s own input handling, not Steam’s detection.
4. While you’re there, highlight Blades & Battles and click the little controller icon next to Play. You can browse community layouts or apply an official one, which helps make sure every button lines up with classic beat ’em up controls.

Step 7: Reset Proton Files (Linux and Steam Deck)

Playing on a Steam Deck or Linux through Proton? A corrupted prefix can cut off controller communication.

1. Find Blades & Battles in your library.
2. Click the gear icon, choose Manage, then Clear Proton Files. Or manually delete the compatdata folder tied to the game’s app ID.
3. Relaunch. Steam builds a fresh prefix, which clears out hidden driver mismatches.

Quick Fix Cheat Sheet

Final Thoughts

Work through the steps in order: check that Windows sees the pad, set up Steam Input globally and per game, give Steam admin rights, and get rid of any mapping software that’s meddling. One of them will fix it. In my experience the per-game Steam Input override and stray mapping tools cause the most trouble.

Once your controller is responding, Blades and Battles gets fun fast. The combat is punchy, the retro arcade vibe is right on target, and it’s a great excuse to call a friend over for local co-op.