How to Fix Controller Not Working in Wuthering Waves on PC (2026)

Executive Summary and Wuthering Waves PC Input Architecture

Wuthering Waves has earned widespread praise among action RPG enthusiasts for its fluid traversal, fast-paced acrobatic combat, and deep mechanical complexity centered on intro/outro skills, aerial juggles, and frame-tight parry counters. Because high-level boss encounters (such as Hologram challenges and the Tower of Adversity) demand instantaneous defensive reactions, playing with a high-performance controller provides a clear ergonomic advantage over mouse and keyboard.

At the architectural level, Wuthering Waves PC executes on a heavily modified branch of Unreal Engine 4, distributed via Kuro Games’ standalone launcher and the Epic Games Store. The engine’s human interface pipeline evaluates gamepads through strict API hierarchies:

• Microsoft XInput Tier: Standardized polling for all certified Xbox 360, Xbox One, Xbox Series X|S, and native XInput third-party gamepads. Displays authentic Xbox button prompts ([A], [B], [X], [Y]).
• Sony Direct HID Tier: Native detection for Sony DualSense and DualShock 4 controllers when connected via direct wired USB-C cable. Displays PlayStation button glyphs.
• DirectInput Blindness: Generic USB gamepads, older DirectInput controllers, retro flight sticks, and Nintendo Switch Pro controllers (connected outside Steam) are completely ignored by the client. The game loop maintains zero legacy DirectInput polling threads.

Bridging generic hardware into Wuthering Waves without risking anti-cheat penalties requires deploying driver-level virtual device emulation via XOutput and ViGEmBus.

Why Unreal Engine 4 Ignores Generic DirectInput Gamepads

To diagnose why non-Xbox controllers fail in Wuthering Waves, one must understand how Unreal Engine 4 abstracts game controllers. In standard PC deployments, UE4 relies on the Windows XInput dynamic link library (xinput1_4.dll or xinput9_1_0.dll). DirectInput support is treated as a legacy Windows 98/XP fallback and is routinely disabled in modern competitive action titles to minimize frame latency and eliminate CPU polling spikes.

When you connect an unsupported third-party controller, Windows assigns it a standard DirectInput device handle. Because Wuthering Waves’ engine loop bypasses DirectInput, your button presses are never delivered to the game thread. The player is left with an unresponsive avatar, despite the controller testing perfectly inside Windows joy.cpl.

DualSense Wired USB Features vs Wireless Bluetooth Emulation

For players utilizing Sony’s PlayStation 5 DualSense controller, Wuthering Waves delivers an exceptional combat feel on PC. Squeezing triggers to unleash Resonator skills and feeling the metallic clash of parried boss blades enhances the visual spectacle.

The Wired Connection Requirement

To experience native PlayStation prompts and stable haptic feedback, the DualSense must be connected via a high-speed wired USB-C cable. When connected over standard Windows Bluetooth:

• Windows exposes the DualSense through generic Bluetooth HID reports, stripping the secondary audio-based haptic telemetry channels.
• The controller often fails to trigger the game’s automatic PlayStation UI detection, leaving prompts blank or defaulting to keyboard letters.
• Bluetooth packet drops during intensive 60+ FPS combat can drop crucial dodge inputs. For wireless play, virtualizing the device into a stable Xbox 360 controller via XOutput is the most dependable remedy.

Step-by-Step Configuration of XOutput for Wuthering Waves

To convert any generic PC gamepad, retro arcade fight stick, or unrecognized controller into a native XInput device that Wuthering Waves ingests effortlessly, execute the following verified setup:

Step 1: Install Core Driver Dependencies

1. Download and run the installer for ViGEmBus (Version 1.22.0). This kernel driver handles virtual bus instantiation.
2. Install the Microsoft .NET 7.0 or .NET 8.0 Desktop Runtime (x64).
3. Restart your PC. Windows must reboot to complete the registration of the virtual bus driver.

Step 2: Map Controls in XOutput

1. Connect your physical controller via USB or pair it over Bluetooth. Open joy.cpl (Win + R > joy.cpl) to confirm your controller is recognized by Windows.
2. Launch XOutput.exe with administrator privileges.
3. Under Game Controllers, locate your device and click Add Controller.
4. Click Edit to configure the mapping matrix:
   • Left Stick & Right Stick: Map horizontal and vertical axes to physical stick movement. Verify linear response without deadzone stickiness.
   • Triggers (LT / RT): Map Left Trigger (Utility / Grappling Hook) and Right Trigger (Resonator Skill / Echo). If your controller features analog triggers, map them under Axes; if using digital microswitches, map them under Buttons.
   • Face & Navigational Buttons: Assign A (Jump), B (Dodge / Sprint), X (Basic Attack), Y (Resonance Liberation / Ultimate), Bumpers (LB for Echo, RB for Lock-on).
5. Close the mapping configuration dialog and click Start. Windows will emit an audible peripheral connection sound, and a secondary “Controller (Xbox 360 For Windows)” entry will now be active in joy.cpl.
6. Launch Wuthering Waves from the Kuro Games launcher. The game will immediately acknowledge the virtual Xbox controller.

Eliminating Echo Menu Skipping and Double Input with HidHide

When bridging gamepads through emulation software in Wuthering Waves, players frequently encounter the double input glitch. When browsing your Echo inventory, tuning Sonata effects, or navigating dialogue choices, pressing the D-pad once causes the cursor to jump across two slots at a time, making preset tuning nearly impossible.

The Architecture of the Double Input

While Wuthering Waves’ 3D combat loop ignores DirectInput, its user interface menus listen to raw Windows low-level input messages (WM_INPUT). Because Windows simultaneously exposes both your physical DirectInput gamepad and the virtual Xbox 360 controller, every physical button press generates two separate input events.

For comprehensive documentation on filter driver mechanics, read our complete guide on resolving double input with HidHide.

Calibrating Deadzones and Sensitivities for Frame-Tight Parries

Wuthering Waves features one of the most rewarding parry systems in action gaming. Flashing golden rings on attacking enemies signal a parry window; striking with an attack command at the exact collision frame deflects the blow, inflicts massive Vibration gauge damage, and interrupts boss combos.

Eliminating Parry Input Latency

To ensure your attacks execute within the parry window:

• Stick Centering and Deadzones: Wuthering Waves’ camera sensitivity directly impacts situational awareness against aggressive boss mobility. Set in-game Camera Sensitivity to between 60% and 75%. If your thumbstick exhibits slight physical drift, do not compensate with wide in-game deadzones; configure a tight 5% deadzone offset inside XOutput under Edit > Axes > Deadzone. Consult our guide on calibrating stick drift and deadzones.
• Lock-On Responsiveness: Assign Lock-on to Right Bumper (RB) or Right Stick Click (RS) so you can swiftly cycle targets in multi-enemy wave encounters without lifting your thumb from combat buttons.

Resolving Launcher Hook Conflicts with Epic Games and Steam

Many players purchase or access Wuthering Waves through the Epic Games Store, or attempt to launch it as a “Non-Steam Game” via Steam to take advantage of custom controller remapping profiles.

The Detached Process Trap

When launched as a non-Steam shortcut, Steam hooks the Kuro Games launcher binary (launcher.exe). When you click “Start”, the launcher spawns the actual game executable (Client-Win64-Shipping.exe) in a detached thread. Steam Input immediately loses process focus and shuts down, leaving the game without controller input.

The cleanest and lowest-latency approach is to run Wuthering Waves directly via its native launcher and rely on XOutput at the operating system driver level. For a complete technical breakdown, read our guide on XOutput vs Steam Input.

Anti-Cheat Expert Runtime Verification and Driver Safety

Kuro Games protects Wuthering Waves with Anti-Cheat Expert (ACE). Given the severe anti-tamper penalties applied to unauthorized memory modifiers, players rightfully verify whether virtual controller software is safe.

The Anti-Cheat Compliance Breakdown

It is crucial to understand what Anti-Cheat Expert monitors:

• Prohibited Software: Memory scanners, debuggers, proxy DLL wrappers dropped into the game folder (such as legacy xinput1_3.dll), and automated macro scripts designed to automate combat rotations.
• XOutput Operation: XOutput operates strictly at the Windows device driver tier via ViGEmBus. It reads standard DirectInput telemetry and communicates with the kernel virtual bus driver to populate an authentic Xbox 360 controller device (`VID_045E&PID_028E`). It executes zero memory reading/writing, touches no game files, and contains no automated scripts.

To Anti-Cheat Expert, your controller is identical to an authentic Microsoft controller connected via physical USB. Read our comprehensive technical investigation into XOutput and anti-cheat compliance for further validation.

Upgrading to Hall Effect Hardware for Tower of Adversity Bosses

While software emulation via XOutput and ViGEmBus resolves all protocol translation hurdles, physical hardware limitations govern your combat ceiling in high-level endgame content like the Tower of Adversity and Hologram Bosses. Standard first-party controllers utilize carbon-film potentiometers. Under the repetitive, rapid thumbstick actuations required for continuous dodging, sprint cancels, and quick parries, mechanical wear rapidly introduces stick drift.

Stick drift causes your character to walk off platforms, break camera lock-on, or delay parry timing.

Upgrading to a dedicated controller equipped with contactless Hall Effect magnetic sensors and tactile microswitch face buttons delivers permanent immunity to stick drift, instantaneous button actuations, and native plug-and-play XInput compatibility on PC.

Frequently Asked Questions

Does Wuthering Waves support PS5 DualSense controllers natively on PC?

Yes, Wuthering Waves features native PlayStation 5 DualSense support with correct PlayStation button glyphs when connected via a direct wired USB-C cable. Over standard Windows Bluetooth, however, the DualSense reports as a generic wireless DirectInput device, which often fails to register in-game. For wireless play, virtualizing via XOutput or DS4Windows is recommended.

Why is my generic USB gamepad completely invisible to Wuthering Waves?

Wuthering Waves’ custom Unreal Engine 4 build is engineered around Microsoft XInput and first-party Sony HID interfaces. Generic PC pads, retro joysticks, and Nintendo Switch Pro controllers (outside of Steam) communicate via DirectInput. Because the game does not poll DirectInput APIs, it treats the controller as non-existent. XOutput solves this by translating DirectInput commands into an authentic virtual Xbox 360 controller.

How do I fix the Echo menu or dialogue skipping two entries per press?

This double-input glitch occurs because Unreal Engine 4 captures raw Windows input messages (WM_INPUT) while simultaneously reading the virtual XInput stream. As a result, both your physical DirectInput gamepad and your virtual Xbox 360 controller transmit input commands. Installing HidHide, cloaking the physical gamepad, and white-listing XOutput.exe resolves this issue completely.

Can using XOutput or ViGEmBus trigger an Anti-Cheat Expert ban in Wuthering Waves?

No. Kuro Games utilizes Anti-Cheat Expert (ACE) to detect process memory modification, injected DLLs, and automated macro software. XOutput interfaces with the Microsoft WHQL-certified ViGEmBus driver to instantiate a virtual Xbox 360 controller at the hardware bus layer. It touches no game memory, injects no DLLs, and executes no automated scripts, making it fully compliant with anti-cheat standards.

Why did my controller stop working after a major Wuthering Waves version update?

Major engine patches occasionally reset in-game control scheme preferences back to Keyboard & Mouse, or update game launcher hooks. Open in-game Settings > Controls and verify that Controller mode is selected. Furthermore, ensure XOutput is running with emulation active before launching the game from the Kuro Games Launcher.