If you are playing Call of Duty titles—such as Warzone, Modern Warfare III, or Black Ops—on a PC with a PS5 DualSense controller, you might encounter a frustrating glitch where your inputs double-press. Menus will skip slots when you click once, your in-game layout will constantly swap between Xbox and PlayStation icons, or your controller will stop responding entirely.
This happens because the Call of Duty game engine natively reads your raw PlayStation controller via DirectInput while your mapping software simultaneously projects a virtual Xbox or PS4 layout via XInput. The game tries to process both signals at the exact same millisecond, causing the Double Input Issue.
To fix this completely and get clean, zero-latency inputs, always download your setup tools from the official site at ds5windows.dev. Follow this comprehensive guide to clear up your driver path.
1. Hide Your Physical Controller with HidHide
The only permanent way to fix double inputs in Call of Duty is to completely hide your physical controller from Windows, ensuring that games can only see the virtual controller created by your mapping app.
- Close your mapping application completely.
- Open the HidHide Configuration Client app on your computer. If you do not have it, you can safely download the latest architecture setup files from the official Nefarius GitHub Repository.
- Go to the Devices tab. Look for your Sony Interactive Entertainment Wireless Controller and check the box directly next to it. A Red Lock icon will appear over the name.
- Look at the bottom of the window and check the box that says “Enable Device Hiding.”
- Switch over to the Applications tab and add the executable path for your controller mapping
.exefile. This tells your operating system that only your mapping app has permission to see the raw PS5 controller. - Open your controller mapping software again and click Start.
2. Switch Your Output Protocol to Xbox 360
Call of Duty games on PC are built natively around the Microsoft Xbox controller framework. Forcing your software to output an Xbox 360 signal prevents the game engine from trying to remap your triggers or split your hardware ID.
- Navigate to the Profiles tab inside your application and click Edit on your Call of Duty profile.
- On the right side of the screen, click on the Other tab.
- Find the Emulated Controller dropdown menu and change it from DualShock 4 to Xbox 360.
- Click Save at the top right of the window.
3. Verify Your Call of Duty In-Game Settings
Once your background drivers are locked down, you must verify that the game is actively targeting your virtual layout rather than defaulting to your keyboard and mouse.
- Launch your Call of Duty game and open the main Settings menu.
- Navigate to the Controller section.
- Look for the Aim Input Device setting at the very top. If it is locked onto “Mouse,” toggle it over to Controller.
- Look at your menu screen prompts. If they display standard Xbox buttons (A, B, X, Y) and move one slot at a time, your double input issue is fully resolved.
4. Turn Off Controller Audio Redirection
When a DualSense controller is plugged in via a USB-C cable, Windows often mistakes its internal speaker for your main PC sound card. This audio conflict can cause your controller driver to stutter, triggering double input loops mid-match.
- Open your Windows Control Panel and click on Sound.
- Under the Playback tab, locate your primary gaming headset, right-click it, and select Set as Default Device.
- Scroll down to find the device labeled Wireless Controller / DualSense Audio, right-click it, and select Disable.
Final Thoughts
The double input issue in Call of Duty games can ruin your competitive edge, but cleaning up your input loop takes just a few minutes. By downloading your files directly from ds5windows.dev and using HidHide to secure a dedicated connection path, you eliminate controller stutter permanently. Always make sure to launch your mapping application and hit Start before opening Battle.net, Steam, or your game client to ensure Call of Duty builds a clean link with your virtual layout from the moment it boots.