Keyboard & Mouse (KB+M) Remapping Issues
Sometimes your controller doesn’t work properly in a game, but that doesn’t always mean there’s something wrong with the controller itself. The issue could be caused by incorrect keyboard and mouse remapping or problems with the input handler in DS4Windows. It’s important to know whether you are dealing with a controller behavior issue or a keyboard/mouse mapping issue.
Before you start troubleshooting keyboard and mouse remapping in DS4Windows, first make sure that it’s an input issue and not a controller issue.
DS4Windows can remap the controller into keyboard and mouse inputs using its built-in input handlers.
There are two main input handlers for this: SendInput and FakerInput.
SendInput
SendInput is the default input handler in DS4Windows for keyboard and mouse mappings. It maps controller signals into simulated KB+M input.
However, some games (like Valorant) and Windows security systems can block or ignore SendInput, so those games do not receive the input.
FakerInput
FakerInput is the advanced input handler in DS4Windows. It maps controller actions into virtual keyboard and mouse devices, so the system treats the input as if it’s coming from real hardware (keyboard or mouse). You need to install a driver to use it. It can be used in games that block injected input. There are not many limitations like SendInput.
How to Check Which One You Are Using
Up till now, you have understood that using FakerInput can prevent this remapping issue. But how do you check which input handler your DS4Win is currently using? It’s very simple: if you haven’t installed the FakerInput driver, it means it is using the default handler, which is SendInput. You can further confirm it by visiting the DS4Windows Log tab.
- Open DS4Windows and go to its Log tab.
- It will show if you are using SendInput or FakerInput.
- If you haven’t installed anything extra, it’s SendInput.
- If you installed the FakerInput driver, DS4Windows will use FakerInput automatically.
When Should You Switch to FakerInput?
If you are having any of these problems:
- Games don’t respond to your keyboard/mouse commands.
- Windows ignores commands during admin prompts (UAC).
- The mouse moves, but nothing happens in the game.
- Macros don’t work properly.
- You are trying to play games with anti-cheat systems (like Valorant).
Then our recommendation is to install the FakerInput driver from DS4Windows settings and restart the app/tool.
Problem #1: Mouse Moves on Its Own or Keyboard Types Randomly
Quick Fix: Mostly this is because of stick drift, which can be fixed by increasing the dead zone. The Dead Zone tells DS4Windows to ignore tiny, unwanted stick movements.
What’s going on?
Your controller stick drifts a little even when you are not moving it.
Fix it:
- Go to DS4Windows and select your controller profile.
- Go to the Dead Zone settings under the stick controls.
- Increase the Dead Zone slowly until the drift stops.
Problem #2: Windows is ignoring DS4Windows KB & M Commands, especially in UAC Popups
Quick Fix: Use the FakerInput handler instead of SendInput.
Explanation:
The SendInput doesn’t remap the controls in a refined enough way to get past the Windows security feature called User Account Control (UAC). When we use this default input handler, this security system takes it as a malicious activity, and it blocks this.
So, if you are thinking about disabling your security system, it could be risky. Instead, use the FakerInput handler, which remaps the KB+M controls to make them appear as if they are coming from a real physical keyboard and mouse.
Problem #3: The Game Doesn’t Respond to DS4Windows Keyboard/Mouse Commands
Quick Fix: Install and switch to the FakerInput handler.
Explanation:
Some games with anti-cheat systems do not allow simulated input like what SendInput uses to prevent cheating. These games ignore commands that do not come from real devices.
FakerInput sends inputs in a way that tricks the system into thinking they are coming from actual hardware, and this makes games more likely to accept the commands.
Problem #4: KB/M Commands Not Working via Macros
Quick Fix: Add a delay between key presses/releases manually, or turn on Record delays when you record the macro.
Explanation:
When you create a macro, the keys are pressed so quickly that sometimes Windows doesn’t notice that a key is pressed.
To fix this, either:
- Manually add delays (about 100ms is recommended) between press and release commands,
- Or enable the Record delays option while recording the macro. When you are recording your macro, this option tells DS4Windows to remember the exact timing between your actions. So if you take a second between two key presses, it will include that pause in the macro to notice every key pressed.
Problem #5: Special Anti-Cheat Games Like Valorant Still Block Input
Explanation:
Games like Valorant have very strict anti-cheat systems. They detect which keyboard or mouse is used first when launching the game, and only accept input from those devices later. If your real mouse or keyboard sends a signal before DS4Windows does, the game will then ignore DS4Windows completely.
To get around this:
- Either unplug your real keyboard/mouse when you launch the game,
- Or do not touch them at all. Keep them still, with no clicks or movement, and use only DS4Windows’ KB/M until its commands are detected.
Once the game locks onto DS4Windows’ KB+M, it will ignore the real devices.
