InputMapper Legacy Archive: Free PC Controller Mapping Hub

Advanced Input Translation

Converts DirectInput signals from your DualShock 4 and other supported controllers into XInput, so games and emulators that only understand Xbox 360 controllers can read your pad. The PS5 DualSense is a different story — InputMapper’s final build predates it — so DualSense owners should see our DualSense on PC guide for tools that do support it.

Macro & Remapping Engine

Go beyond basic emulation. Create highly complex controller profiles where single button clicks trigger intricate macro sequences, keystrokes, or mouse movements, giving you full control over specialized simulation setups or competitive loadouts.

Hardware Customization

Unlock the full secondary feature set of your controller on Windows. Take absolute control over the DS4 Lightbar color states, configure precise motor rumble intensities, change dead zones, and even utilize the native touchpad as a fully functional desktop mouse cursor.

💻 Software & OS Requirements

• Supported OS Windows 10 / Windows 11 (64-bit)
• System Architecture x64 Baseline Environment
• Required Framework Microsoft .NET Framework 4.x
• Core Emulation Driver ViGEmBus Driver (required for 1.7 output)
• Input Hiding Companion HidHide (modern successor to HidGuardian)
• Connectivity Mode USB Cable or Bluetooth 4.0+ Adapter

🎮 Supported Hardware Controller Input

While engineered primarily as a DualShock 4 utility mapping tool, InputMapper supports several controller profiles out-of-the-box:

Is InputMapper open source or free to use?

InputMapper is closed-source freeware by DSDCS (DSD Consulting Services). It was always free to download and use for personal purposes, supported by donations rather than a paid edition — no Pro version ever existed.

Why does my system require an emulation driver?

Windows does not inherently understand how to read a virtual controller profile via standard software code alone. InputMapper bridges this by routing your commands through a system driver—most notably the ViGEmBus driver architecture—which mimics an actual hardware bus connection.

What should I do if my game still detects double inputs?

This happens when a game tries to read both your physical PlayStation controller and the emulated Xbox 360 profile at the exact same time. Utilizing the “Exclusive Mode” toggles within InputMapper configurations hides the original hardware controller, making sure only the emulated XInput profile registers.

Install Dependencies

Before launching InputMapper, install the ViGEmBus virtual bus driver (InputMapper 1.7 outputs through it) and make sure a .NET Framework 4.x runtime is present. Restart your operating system to allow driver registration.

Hardware Tethering

Connect your PlayStation device via a high-quality micro-USB cable or establish a connection via Windows Bluetooth options. Launch InputMapper with administrator privileges to ensure successful hardware hooking.

Create a Profile

Navigate to the “Profiles” sidebar menu selection. Select “New Profile” and designate your output type as an Xbox 360 controller layout. This assigns the native XInput axes rules to your custom triggers automatically.

Apply & Verify

Link your active gamepad tracking module to your newly configured mapping rules. Launch any PC game storefront and confirm your virtual button configurations are registering without input lag or ghosting.

Root Cause: The application cannot establish a communication line with the required virtual layout controllers because the underlying ViGEmBus framework driver is either missing, outdated, or blocked by modern Windows kernel-isolation integrity.

Root Cause: Windows treats active controller inputs as open hardware. If an application like Steam, Epic Games Launcher, Chrome, or an active game client runs in the background before InputMapper initializes, they lock the pad channel, causing double-input anomalies.

Root Cause: High latency states (exceeding 10ms spikes) occur due to aggressive Windows power-saving management throttling the USB Bluetooth receiver or local signal interference on the 2.4GHz wireless frequency.

Works at the OS level: Microsoft Store and Xbox App games expect XInput, and InputMapper presents a virtual Xbox 360 controller they can read. Some titles with kernel-level anti-cheat may still block virtual controllers.

These launchers ship without their own controller remapping layer, so running InputMapper in the background bridges the detection gap for games that only accept XInput.

Emulators can bind directly to the virtual Xbox 360 controller InputMapper creates, which is often simpler than per-emulator plugin setups.

Requires Attention. Steam has its own controller mapper (Steam Input). To avoid double inputs, turn off PlayStation Configuration Support inside Steam settings while using InputMapper.

🛡️ No Repackaged Installers

Download links point to established public archives (FileHorse) and official GitHub releases (ViGEmBus, HidHide). Our own download mirror is clearly labeled as a mirror — never disguised as an official source.

🔍 Understanding False Positives

Because InputMapper installs a virtual bus driver and hooks controller input, some antivirus heuristics flag this whole class of tool. That is one more reason to verify the checksum: a file that matches the published hash is the file the archive distributed. Note that the older 1.6.10 build has a publicly recorded buffer-overflow vulnerability (CVE-2019-25464) — which is why we only recommend the final 1.7 build.

🔒 Cryptographic Verification

Both headline downloads carry SHA-256 checksums verified by direct download on 2026-10-23, and the InputMapper installer also matches the MD5 published independently by FileHorse and FileCroco.