Dark Souls Remastered Controller Not Working? Fix with XOutput

FromSoftware’s dark fantasy masterpiece Dark Souls Remastered remains one of the most revered and unforgiving action RPGs in gaming history. From parrying the Silver Knights of Anor Londo to dodging the relentless onslaught of Knight Artorias in Oolacile, victory in Lordran depends on split-second reaction times, flawless spatial awareness, and muscle memory. The combat architecture treats every input with life-or-death gravity: rolling invulnerability frames (i-frames) require microsecond release timing, heavy attacks demand full trigger travel, and camera alignment dictates target lock-on stability.

Yet, ever since the legendary 2012 release of the Prepare to Die Edition and continuing into the 60 FPS modern remaster co-developed by QLOC, PC players have confronted severe, game-breaking controller failures. Common symptoms include Dark Souls completely ignoring a plugged-in controller, the disorienting infinite spinning camera glitch that whips the viewpoint around your Chosen Undead at nauseating speeds, and duplicate input glitches that cause your character to double-chug Estus Flasks or roll into deadly chasms.

These issues are not random hardware bugs; they are the direct byproduct of FromSoftware’s legacy controller enumeration routines and rigid Microsoft XInput reliance. When confronted with non-standard DirectInput controllers, virtual HID peripherals, or multiple connected USB input devices, the engine frequently binds to an inactive device slot or misinterprets raw analog axes.

This technical engineering guide provides an exhaustive, benchmarked manual to diagnose and cure every controller failure mode in Dark Souls Remastered. We deconstruct the engine’s HID enumeration hierarchy, eliminate the spinning camera bug at the driver level, bridge legacy DirectInput pads using XOutput, enforce clean single-device arbitration via Nefarius HidHide, and configure drift-free Hall Effect hardware for flawless parry execution.

Executive Summary and FromSoftware Engine Input Architecture

To understand why controllers fail in Dark Souls Remastered, one must examine the internal input stack of FromSoftware’s proprietary engine (DarkSoulsRemastered.exe). The game’s input pipeline was originally conceived during the Xbox 360 era and continues to rely strictly on the Microsoft XInput API:

• Strict XInput Dependency: The game binary exclusively links against xinput1_3.dll / xinput1_4.dll. It does not query legacy DirectInput 8 interfaces. If a controller does not expose a certified XInput HID descriptor, Windows registers the device in joy.cpl, but Dark Souls Remastered completely overlooks its existence.
• Primary Device Slot Binding (Index 0): The engine queries XInputGetState specifically targeting dwUserIndex = 0. Unlike modern engines that dynamically assign player slots or permit manual in-game controller selection, Dark Souls binds exclusively to whichever peripheral Windows reports as the primary game controller.
• Analog Axis Deadzone Hardcoding: The engine expects standardized thumbstick normalization curves (\( -32768 \) to \( +32767 \)) with a small internal deadzone. If an uncalibrated device or worn potentiometer reports a resting center voltage outside this threshold, the engine immediately interprets it as continuous stick deflection.

Deploying XOutput backed by the ViGEmBus driver translates raw DirectInput packets into official Microsoft Xbox 360 XInput reports, guaranteeing immediate compatibility with Dark Souls Remastered.

The Primary Device Slot Flaw and HID Enumeration Hierarchy

The most pervasive reason Dark Souls Remastered ignores a fully functioning controller is FromSoftware’s infamous HID Enumeration Priority Flaw.

When Windows boots or when USB devices are plugged in, the operating system assigns an internal enumeration index to every device classified under Human Interface Devices (HID). During its initialization routine, DarkSoulsRemastered.exe scans the HID tree from index 0 upward. It binds to the first peripheral that reports joystick or game controller capabilities.

Triage: How to Cleanse Device Manager

1. Press Win + X and select Device Manager.
2. Expand the Human Interface Devices category.
3. Look for vJoy Device, Virtual HID Device, or any orphaned emulator drivers. Right-click and select Disable device (or Uninstall device).
4. Unplug any flight yokes, racing wheels, and graphics tablets before launching Dark Souls Remastered.
5. Ensure your physical controller (or the XOutput virtual controller) is connected directly to a rear motherboard USB port.

Resolving the Infamous Infinite Spinning Camera Bug

Few things are as disorienting as loading into the Undead Asylum only to watch the camera rotate violently at 300 RPM without touching the controller.

The Infinite Spinning Camera in Dark Souls Remastered is caused by axis mapping misalignment or severe potentiometer resting drift:

• Axis Mapping Cross-Talk: In standard XInput architecture, the Right Thumbstick controls camera movement via sThumbRX (horizontal yaw) and sThumbRY (vertical pitch). When using generic gamepads or misconfigured emulators, the engine often receives analog trigger values (Z-axis) mapped directly into the Right Stick X/Y registers. Because analog triggers rest at 0 or -32768, the engine interprets this as full stick deflection, spinning the camera endlessly.
• Potentiometer Stick Drift: If an older physical controller suffers from potentiometer carbon film wear, the right stick may report a permanent resting value outside the engine’s internal deadzone window, causing continuous slow camera rotation.

Driver-Level Resolution in XOutput

To completely eliminate the spinning camera bug:

1. Open XOutput as Administrator and click Edit on your controller.
2. Navigate to Right Thumb X and Right Thumb Y. Verify that they are mapped strictly to your physical right thumbstick axes (typically Axis 3 and Axis 4), and NOT to triggers (LT/RT).
3. Observe the real-time crosshair indicator while the stick rests in its neutral center position.
4. If the crosshair wavers outside the center target, adjust the Deadzone slider to 5% to 8%.
5. Navigate to Left Trigger and Right Trigger and ensure they are assigned strictly under the Triggers / Axes section with appropriate 0 to 100% calibration travel.

Cold Boot Enumeration and Startup Synchronization Rules

Unlike modern games that maintain active USB hot-plug event listeners (e.g. listening for WM_DEVICECHANGE Windows messages), Dark Souls Remastered executes controller enumeration strictly once during the cold boot sequence.

Step-by-Step DirectInput to XInput Bridging with XOutput

For players using PlayStation controllers, retro arcade pads, or generic USB gamepads, follow this verified setup procedure to establish a stable virtual XInput pipeline:

1. Install ViGEmBus and .NET Runtime: Download and install the ViGEmBus 1.22.0 driver and .NET 7.0 Desktop Runtime (x64) from our official download center. Restart your PC to allow Windows to register the kernel bus driver.
2. Run XOutput as Administrator: Open the XOutput application. In the device list, identify your connected DirectInput controller.
3. Create and Configure Virtual Controller: Click Add Controller, then click Edit.
4. Map Combat and Movement Inputs:
   • Left Thumb Stick (X/Y): Character movement and sprinting direction.
   • Right Thumb Stick (X/Y): Camera control and target lock-on cursor.
   • Left Stick Click (L3) & Right Stick Click (R3): R3 maps to Target Lock-on / Camera Reset.
   • Face Buttons (A, B, X, Y): A (Confirm/Interact), B (Dodge Roll/Backstep/Sprint), X (Use Item/Estus Flask), Y (Two-Hand Weapon Toggle).
   • Bumpers (LB, RB): LB (Block/Parry Off-Hand), RB (Light Attack / Spell Cast).
   • Triggers (LT, RT): LT (Parry / Weapon Skill), RT (Heavy Attack / Jump Attack modifier).
5. Save Profile and Start Emulation: Close the configuration window and click Start. The status will illuminate “Started”.

Calibrating Analog Stick Deadzones for Frame-Perfect Parries and Dodges

Combat mechanics in Dark Souls Remastered are governed by precise frame data. Understanding how the engine processes button presses and analog thresholds is vital for survival:

Calibrating Left Stick for Jump Attacks and Kicks

Executing a Kick (Forward + RB) or Jump Attack (Forward + RT) requires synchronizing a rapid analog stick flick from 0 to 100% deflection with a bumper or trigger press within a strict 2-frame window (33 milliseconds).

If your Left Stick’s analog sensitivity curve is sluggish or has a large outer deadzone, the engine will register the attack button before the stick reaches the required threshold, resulting in a normal light attack instead of a kick, leaving you wide open to enemy shield blocks!

In XOutput → Edit → Left Thumb X/Y, set the Outer Deadzone to 0 and verify that flicking the stick immediately commands 100% axis saturation.

Eliminating Double Inputs and Estus Chugging Glitches with HidHide

When running XOutput, Windows maintains two simultaneous representations of your controller: the raw physical DirectInput device and the virtual Xbox 360 controller.

Because Dark Souls Remastered scans the HID device tree, it may receive input packets from both instances at once. This results in the catastrophic Double Input Glitch:

• Double Estus Chug: Pressing X once causes your character to drink two consecutive Estus Flasks, wasting precious healing charges.
• Menu Skipping: Scrolling down through your inventory or equipment screen skips every second item slot.
• Roll Cancellation: The character stutters between beginning a roll and immediately halting.

Deploying Nefarius HidHide

To permanently resolve double inputs, use Nefarius HidHide to cloak the physical controller from the game:

1. Download and install Nefarius HidHide from our software hub. Restart your PC.
2. Open the HidHide Configuration Client as Administrator.
3. Under the Applications tab, click + and add XOutput.exe. Check the whitelist box next to XOutput so it retains permission to read your physical controller.
4. Under the Devices tab, locate your physical controller hardware.
5. Check the box next to your physical controller to apply the red lock icon.
6. Check Enable device hiding at the bottom of the client.
7. Open joy.cpl. You will now see only the virtual Xbox 360 Controller for Windows. Launch Dark Souls Remastered—all double chugs and menu skips are completely eliminated!

Resolving Steam Input Hook Collisions and Overlay Interferences

If you run Dark Souls Remastered through Steam, Steam Input often attempts to remap the controller simultaneously with XOutput, creating hook collisions and input stuttering.

Disabling Steam Input for Dark Souls Remastered

1. Open your Steam Library.
2. Right-click Dark Souls: Remastered and select Properties…
3. Navigate to the Controller tab on the left.
4. Under Override for Dark Souls: Remastered, select Disable Steam Input.
5. Restart Steam and launch the game. Dark Souls will now communicate directly with the clean XOutput virtual Xbox 360 controller without Steam’s remapping interference.

Upgrading to Tournament-Grade Hall Effect Hardware for Soulsborne Mastery

While software emulation via XOutput and HidHide eliminates all driver hurdles and input glitches, conquering FromSoftware’s challenging combat demands mechanical reliability.

Traditional gamepads utilize carbon film potentiometers that degrade with every intense boss fight. Potentiometer wear produces electrical jitter, causing the spinning camera nightmare and dropping frame-perfect parry commands. Upgrading to a controller featuring contactless Hall Effect magnetic sensors guarantees permanent zero-drift precision and ultra-fast polling:

Frequently Asked Questions

Why does my controller work in Windows but get completely ignored by Dark Souls Remastered?

Dark Souls Remastered uses strict Microsoft XInput polling inherited from the Xbox 360 architecture and does not query legacy DirectInput 8 interfaces. If your controller is a DirectInput gamepad, PS3 controller, or generic arcade stick, Windows detects it in joy.cpl, but the game engine completely overlooks it. XOutput bridges DirectInput to compliant XInput via the ViGEmBus kernel driver.

What causes the infinite spinning camera glitch in Dark Souls Remastered?

The spinning camera occurs when Dark Souls Remastered reads an uncalibrated analog axis reporting maximum positive or negative deflection (-32768 or +32767). This is typically caused by conflicting virtual devices (like vJoy), unmapped analog triggers registered as right-stick axes, or hardware potentiometer wear. Adding a 5% to 8% deadzone in XOutput or disabling rogue HID devices resolves it immediately.

Why doesn’t Dark Souls Remastered detect my controller if I plug it in after launching the game?

FromSoftware’s PC engine architecture executes controller enumeration strictly during the initial splash screen and title sequence (cold boot). It does not maintain active hot-plugging device listener threads. You must connect your controller and start XOutput emulation before launching DarkSoulsRemastered.exe.

Why does my character drink two Estus Flasks or jump when I try to roll?

This double-input glitch occurs when Dark Souls Remastered receives commands from both the physical DirectInput controller and the virtual XOutput Xbox 360 controller simultaneously. Installing Nefarius HidHide and cloaking the physical controller prevents duplicate inputs.

Does this XOutput fix also work for Dark Souls 2, Dark Souls 3, and Elden Ring?

Yes. All modern FromSoftware PC releases (Dark Souls: Prepare to Die Edition, Dark Souls II: Scholar of the First Sin, Dark Souls III, Sekiro: Shadows Die Twice, and Elden Ring) share the same underlying XInput architecture and device enumeration hierarchy. The XOutput and HidHide configuration pipeline resolves controller issues across all these titles.