Survival Log Controller Support Fix: Gamepad Not Working PC Solutions

Survival Log is the kind of game that can make you forget how much time has passed. You start by trying to keep a small safe house supplied, and suddenly you’re knee-deep in crafting materials, scavenging routes, character management, drones, storage problems, and a dozen different things that need your attention. Developed by Midnight Workshop and published by Lilith Games, the zombie survival strategy game has found a pretty interesting audience on PC since its August 12, 2026 release.

Personally, I think Survival Log is much more comfortable with a controller than its menus initially suggest. There is something satisfying about sitting back with a gamepad while managing a ruined city and slowly turning a miserable shelter into something that actually feels secure. The problem is that controller support in Survival Log can be surprisingly temperamental. Sometimes the gamepad isn’t detected at all, sometimes the buttons are completely wrong, and sometimes the controller works perfectly until you open one particular menu.

If you’ve run into that problem, don’t immediately assume your controller is dying. A lot of the trouble appears to come from the way the game handles different input systems, especially when Steam Input, Windows drivers, and controller software are all trying to interpret the same device. Here are the fixes I’d try, starting with the easiest ones.

Survival Log Steam Deck Guide: How to Play, Best Settings, and Controls

Why Is My Controller Not Working in Survival Log?

Before changing anything, it helps to understand why this game can be awkward with gamepads. Survival Log isn’t built around a simple console-style interface. A huge portion of the experience revolves around inventory windows, crafting screens, trading panels, character menus, greenhouse management, and other UI-heavy systems. Some of these interfaces rely on web-based components, which can make traditional controller input behave differently from movement and combat controls.

That is why you can sometimes have a bizarre situation where your character moves normally but the moment you open a menu, the controller becomes useless. I’ve always found these bugs more annoying than a simple “controller not detected” problem because they make you think everything is working until you actually need the buttons.

The most common symptoms include:

• The Xbox or PlayStation controller isn’t detected at all.
• The game recognizes the pad but assigns completely incorrect buttons.
• Analog sticks work in the world but fail inside menus or inventory screens.
• A radial menu opens but immediately disappears when you try to select something.
• Confirm, back, or interact commands don’t respond correctly.

The good news is that these problems are usually worth troubleshooting before giving up on gamepad play altogether.

1. Force Steam Input for Survival Log

This is the first thing I’d try, especially if you’re playing the Steam version. Steam Input can act as a translation layer between your physical controller and the game, and that can be enough to bypass whatever input conflict is preventing Survival Log from understanding the device correctly.

Open your Steam Library, right-click Survival Log, and choose Properties. Go to the Controller section and look for the controller override setting. If it is sitting on the default option, change it to Enable Steam Input.

After making the change, completely close Steam rather than simply closing the game. I recommend exiting Steam from the system tray as well, then launching it again before starting Survival Log. This gives Steam Input a clean chance to initialize instead of carrying over whatever controller state was active before.

This simple fix is particularly useful if you’re using a DualSense or another controller that the game doesn’t handle as naturally as an Xbox-style XInput device.

2. Try a Different Steam Controller Layout

If Survival Log recognizes your controller but the controls feel broken, don’t stop at enabling Steam Input. The actual layout can make a huge difference. Steam’s community controller configurations are worth checking because they can effectively translate mouse-style interface controls into something usable with analog sticks and buttons.

Enter Steam Big Picture Mode and open Survival Log from there. Once the game is running, open the Steam overlay using the appropriate Guide or Home button and enter the controller configuration screen. From there, browse the available community layouts and look for one based around Gamepad with Camera Controls or a similar configuration.

The important part is not necessarily the exact name of one particular layout. What you’re looking for is a configuration that combines normal gamepad movement with mouse-style camera or cursor controls. That can make a surprising difference when dealing with Survival Log’s menus.

If the game still shows old button prompts after applying the new configuration, restart it. Controller glyphs and bindings don’t always refresh immediately, and restarting is considerably easier than spending twenty minutes wondering whether the layout actually worked.

3. Check for Xbox Driver Conflicts

Windows and Steam can sometimes get into an argument over who is supposed to control an Xbox controller. This is especially worth investigating if you’re using an Xbox One or Xbox Series controller through Bluetooth or a wireless adapter.

Open Steam’s settings and go to the Controller section. Depending on your current Steam version and installed drivers, you may see options related to extended Xbox functionality or additional driver support. If an extra driver is installed and you’re experiencing strange detection or mapping problems, disabling that additional layer can be worth testing.

After changing low-level controller settings, restart Windows. Don’t skip this step. Driver changes can remain active until the system is rebooted, so launching Survival Log immediately after changing the setting may give you a false impression that the fix didn’t work.

I’d also test the controller directly in Windows before launching the game again. If the device behaves strangely outside Survival Log, the problem probably isn’t the game itself.

4. Clear Broken Configuration and Shader Data

Sometimes the controller isn’t the problem at all. A corrupted local configuration can cause a game to remember an old device, broken mapping, or invalid input state. This is particularly annoying because everything can look perfectly normal in Steam while Survival Log continues behaving as if you’ve connected a completely different controller.

Close Survival Log and Steam, then press Windows Key + R and enter %LOCALAPPDATA%. Look for a folder associated with Survival Log or Midnight Workshop and check for directories such as Saved, Config, or Shaders.

Be careful here. Don’t start deleting random folders just because their names look suspicious. Configuration and cache data can usually be rebuilt, but you should know exactly what you’re removing before doing it. If you’re uncertain, back up the folder first.

You can also clear Steam’s download cache through Steam > Settings > Downloads. Afterward, restart Steam and launch the game again. The first startup may take a little longer while fresh data is generated.

5. What If You Have a Third-Party Controller?

This is where things get more complicated. Many modern controllers work through XInput, which Windows games generally understand well. Older or unusual gamepads may instead rely on DirectInput, and that can cause compatibility problems with games expecting an Xbox-style controller.

If Survival Log completely ignores a third-party gamepad, an Xbox controller emulation utility such as x360ce may help. The basic idea is simple: the software makes the game see a compatible Xbox-style input device even though your physical controller isn’t actually an Xbox controller.

Install the appropriate version of the emulator, point it toward the game’s installation directory, configure the detected controller, and test every button and analog stick before launching Survival Log. Don’t assume the automatic mapping is perfect. Check the triggers, sticks, bumpers, face buttons, and D-pad yourself.

I’d consider this a last-resort solution rather than the first thing to install. Third-party controller emulation adds another layer of software, and when something goes wrong, it can make diagnosing the original problem harder.

Which Survival Log Controller Fix Should You Try First?

My Recommended Troubleshooting Order

I wouldn’t jump straight into deleting configuration folders or installing controller emulation software. In my experience, the smartest approach is to start with the least invasive solution and only get more aggressive if the problem survives.

1. Enable Steam Input.
2. Test another Steam controller layout.
3. Restart Steam and Windows.
4. Check Windows and Steam controller drivers.
5. Reset local configuration or cache files.
6. Use an Xbox controller emulator only if necessary.

Also, test one change at a time. If you enable Steam Input, install an emulator, delete configuration files, and change Windows drivers simultaneously, you may get the controller working but have no idea which change actually fixed it. That’s a headache waiting to happen the next time a Survival Log update breaks something.

Don’t Forget the Simple Hardware Checks

Before blaming the game, there are a few boring checks that are still worth doing. If you’re using Bluetooth, reconnect the controller or test it through USB. If you’re using a wireless adapter, try another USB port. You should also close other controller-related applications because multiple programs attempting to translate the same device can produce some truly strange results.

For example, if Steam sees your controller, another remapping application sees it, and Windows exposes a virtual Xbox controller at the same time, Survival Log may end up receiving input from the wrong device. That can create the classic situation where the game technically detects a controller but none of the buttons behave the way they should.

Getting Back to the Apocalypse

Controller problems are especially frustrating in a game like Survival Log because the actual gameplay is so well suited to sitting back with a gamepad. Managing a safe house, checking supplies, sending drones out for resources, and gradually expanding your little corner of the apocalypse feels much better when you aren’t constantly reaching for the keyboard.

The important thing is not to assume that a broken controller means broken hardware. Steam Input is the first fix I’d try, followed by a different controller layout. If that doesn’t solve the problem, move on to driver conflicts and local configuration issues. Only after those options fail would I bring third-party emulation software into the equation.

Survival Log is still a relatively new PC game, and controller compatibility can change as developers push patches and seasonal content. A layout that works perfectly today might need adjustment after a future update. For now, though, these troubleshooting steps should give most PC players a practical path back into the wasteland without having to abandon their gamepad.