Why Game Pass Games Cannot See a Bare DualShock 4

The Xbox app and Microsoft Store games on PC expect XInput controllers. XInput is Microsoft’s controller standard, used by Xbox 360 and later Xbox pads, and it is the input language those games are built to listen for. A DualShock 4, by contrast, speaks DirectInput when connected to a PC. It is a perfectly good controller, but it is speaking a different language from the one the game is checking for, so the game ignores it.

This is not a broken driver, a faulty cable, or a setting you missed in the Xbox app. There is no built-in remapping layer in the Xbox app that translates a DualShock 4 into something its games will accept. Until something translates that input at the operating system level, a bare DS4 or DS4 V2 will stay invisible to most Game Pass and Microsoft Store titles, even though the same pad works fine in other software.

What InputMapper Does Differently

InputMapper is freeware from DSDCS, with its final build 1.7.7452.13622 released in May 2020. It takes input from supported controllers — including the DS4 and DS4 V2, Xbox 360 and Xbox One pads, and generic DirectInput and XInput devices used as inputs — and maps that input to a virtual Xbox 360 controller. That virtual controller is created through ViGEmBus 1.22.0, the final, now archived version of that virtual controller driver.

Because the mapping happens at the Windows operating system level, any game that reads XInput can see the virtual pad. The game is not being tricked at the file level and InputMapper is not modifying the game itself. Windows genuinely has an Xbox 360 controller available, and your physical PlayStation pad is driving it. That single mechanism is what makes the same setup work across the Xbox app, standalone games, launchers, and emulators. If you are new to the tool, read how to use InputMapper first for the basic profile concepts, then come back here for the Game Pass order of operations.

What You Need Before You Start

You need a Windows PC, a DS4 or DS4 V2 controller with a USB cable or Bluetooth connection, and current downloads of ViGEmBus and InputMapper. Get both from the download page so you are using the known final builds rather than a random repack from elsewhere. Install ViGEmBus before InputMapper, and restart if Windows asks you to. A wired USB connection is the simplest way to do the first setup, because it removes Bluetooth pairing from the list of things that can go wrong while you are testing.

One honest limit before you begin: DualSense and Switch Pro controllers are not InputMapper inputs. If you are holding a DualSense instead of a DualShock 4, this guide does not apply to that pad — see our separate guide to DualSense on PC for the honest options for that controller.

Setup in the Right Order

The order matters. If you launch the Xbox app before the virtual controller exists, the game may never check for it again during that session. Follow these steps in sequence the first time, and afterwards it becomes a quick routine.

1. Install ViGEmBus 1.22.0 and restart your PC if prompted.
2. Install InputMapper and launch it. Connect your DS4 by USB or Bluetooth and confirm InputMapper lists the physical controller.
3. Create or select a profile with Xbox 360 controller output. This is the profile that tells InputMapper to present a virtual Xbox 360 pad to Windows.
4. Start the profile and leave InputMapper running. The virtual controller should now exist in Windows before any game starts.
5. Only now launch the Xbox app, choose your Game Pass game, and start it. The game should detect a controller at its menus.

Download InputMapper and ViGEmBus

One clean Xbox 360 output profile handles most Game Pass titles, since they all want an XInput pad. You can add per-game profiles later — see InputMapper profiles — but get the plain profile working first.

Verify the Virtual Controller in Windows

Before blaming a game, verify Windows itself can see the virtual pad. Press the Windows key, type Game Controllers, and open “Set up USB game controllers.” You should see an Xbox 360 controller listed once your InputMapper profile is running. Open its properties and press buttons and move the sticks on your DualShock 4 — the indicators in that panel should respond.

If the panel shows the virtual controller responding, InputMapper is doing its job and any remaining problem is inside the specific game or a double input issue described below. If the panel shows nothing, the profile is not running, ViGEmBus was not installed correctly, or the physical DS4 is not connected to InputMapper in the first place. Fix it at this level first; no in-game setting can find a controller Windows does not have.

Stop Double Input Before It Ruins a Session

A common side effect of any virtual controller setup is double input: the game receives your physical pad and the virtual pad at the same time, so menus jump two steps, characters act twice, or the camera spins. Not every Game Pass title reads the physical DS4, but the ones that check both DirectInput and XInput can show exactly this behaviour.

The fix is to hide the physical controller from games while leaving it available to InputMapper. HidHide v1.5.230 does this job. Our full walkthrough is in the HidHide guide, and the symptom-by-symptom diagnosis is in the InputMapper double input fix. Set this up once and test in the Game Controllers panel and in one game menu before you start a long session.

The Anti-Cheat Caveat You Should Not Ignore

Be straightforward about this: kernel-level anti-cheat systems in some competitive titles can object to virtual controllers. InputMapper creates a legitimate virtual device through ViGEmBus, but an anti-cheat system does not know your intent — it only sees a virtual input device and may block it, ignore it, or in stricter cases treat its use as a reason to restrict play. This varies by game and by anti-cheat vendor, and it can change with updates.

For single-player and co-operative Game Pass games this is rarely an issue. For ranked competitive games, check that title’s current rules and community guidance first, and never assume a virtual controller is guaranteed to be accepted. No honest guide can promise any mapper is 100% compatible with every title or safe from bans, and this guide does not promise that either.

A Note on EA Play Included with Game Pass

EA Play is included with PC Game Pass and Game Pass Ultimate, as EA’s own help confirms. The controller point is unchanged: those PC titles still expect XInput, so have the same InputMapper profile running before you launch them. Do not install a second mapper for EA titles — one mapper at a time avoids conflicts.

Games to Play With Your Pad

Once your controller is working, put it to use. These storefronts regularly bundle controller-friendly games that pair well with a working Game Pass library.

Browse Controller Games on Fanatical

Browse Controller Games on Humble

Affiliate link — see our Affiliate Disclosure.

Frequently Asked Questions

Why does my PS4 controller work in Windows but not in Game Pass games?

Xbox app and Microsoft Store games expect XInput controllers, while a DualShock 4 uses DirectInput on PC. InputMapper bridges that gap by mapping your DS4 to a virtual Xbox 360 controller through ViGEmBus, which those games can see.

Do I need to start InputMapper before opening the Xbox app?

Yes. Start ViGEmBus-supported InputMapper, run your Xbox 360 output profile so the virtual controller exists in Windows, and only then launch the Xbox app and your game. Games often check for controllers only at startup.

My menus are moving twice with every press. How do I fix that?

That is double input — the game is reading both your physical DS4 and the virtual Xbox 360 pad. Use HidHide v1.5.230 to hide the physical controller from games while InputMapper keeps using it, then retest in the game menu.

Is InputMapper guaranteed to work with competitive Game Pass games?

No. Kernel-level anti-cheat in some competitive titles can object to virtual controllers, and acceptance varies by game and can change with updates. Check the specific game’s rules first and do not rely on any promise of universal compatibility.

The General Method in One Sentence

InputMapper is DSDCS freeware, final build 1.7.7452.13622 from May 2020, and it maps supported controllers — the DS4 and DS4 V2, Xbox 360 and Xbox One pads, and generic DirectInput and XInput devices used as inputs — to a virtual Xbox 360 controller through ViGEmBus 1.22.0, the final archived version of that driver. Because the mapping happens at the Windows OS level, any game that reads XInput can see the virtual pad. The game does not need to know InputMapper exists. Windows has an Xbox 360 controller, you are holding it in everything but name, and the game behaves accordingly.

This is why the method generalises. Steam games, Epic and GOG titles, emulators, and a lone executable in a downloads folder all read controllers from the same Windows layer. Set the virtual controller up once and every category benefits — which is also why problems should be fixed at that layer first, before you go hunting through a specific game’s options menu. If you are starting from zero, pair this guide with how to use InputMapper for the first-run walkthrough.

Step One: One Global Profile for Most Games

Start with a single global profile: your DS4 mapped one-to-one to an Xbox 360 layout, with no creative remapping. Face button positions match their Xbox equivalents by location, triggers stay triggers, and sticks keep sensible deadzones. Install ViGEmBus and InputMapper from the download page, build that plain profile, and prove it in the Windows Game Controllers panel before you involve any game at all.

Download InputMapper

A clean global profile is your baseline and your diagnostic tool. If a new standalone game misbehaves, returning to the global profile tells you instantly whether the problem is the game or your customisations. Most standalone and indie games need nothing more than this baseline, because they were built and tested against a standard Xbox pad — which is precisely the device your global profile presents.

Step Two: Per-Game Profiles With Auto-Switching

Once the baseline works, per-game profiles handle the exceptions: a game with an unusual default layout, a title where you want the triggers swapped, or an older release that needs a couple of keyboard keys mapped onto spare buttons. InputMapper profiles can be tied to a game’s executable so the right profile loads automatically when that game starts, and the global profile returns when it closes.

Auto-switching is what makes a multi-profile setup pleasant rather than fiddly. Without it, you will eventually launch a game while the wrong profile is active and spend ten minutes blaming the game for your own setup. With it, your routine never changes: start InputMapper, start the game, play. The complete method for building and linking profiles is in InputMapper profiles — build per-game profiles sparingly, only where a game genuinely benefits, and leave everything else on the global profile.

Keep InputMapper Running Before the Game Starts

The single most common failure with standalone games is launch order. Many games scan for controllers once, at startup, and never look again. If InputMapper was not running — or its profile was not active — when the game started, the virtual controller simply was not there to be found, and reconnecting your pad mid-game changes nothing.

Make the order a habit: controller connected, InputMapper running with the correct profile active, virtual controller confirmed if you are troubleshooting, and only then the game. Leaving InputMapper running in the background while you play is expected; it is a small utility doing a live translation, and closing it mid-session removes the controller your game is actively using. If you previously tried to solve controller problems through Steam, also check that an old Steam Input configuration is not fighting your setup — the InputMapper and Steam Input conflict guide explains how to untangle that.

Exclusive Mode, HidHide, and Double Input

Standalone games show one recurring side effect: double input, where a single press acts twice because the game reads both your physical DS4 and the virtual Xbox 360 pad. Games that listen to both DirectInput and XInput are the usual suspects, and the symptom is obvious in menus long before it affects gameplay.

The remedy is to hide the physical controller from games while InputMapper keeps exclusive use of it. HidHide v1.5.230 performs that hiding, and InputMapper’s own exclusive-mode style options pursue the same goal from the other side. Work through the InputMapper double input fix step by step the first time it happens; afterwards, keeping HidHide configured once protects every standalone game you install later, not just the one that first showed the problem.

The Pre-Flight Checklist for Any Standalone Game

Use this checklist the first time you play any non-Steam game with a DS4. After a few repetitions it becomes automatic, and it turns “the controller does not work” into a two-minute diagnosis instead of a forum search.

• Controller connected by USB or Bluetooth and visible in InputMapper.
• InputMapper running, with the global profile — or the correct per-game profile — active.
• Virtual Xbox 360 controller present in the Windows Game Controllers panel and responding to test inputs.
• HidHide configured if this game, or games like it, have shown double input before.
• No second translator, such as Steam Input on a shortcut, remapping the same controller for this game.
• Game launched after all of the above, not before.
• In-game controller prompts checked once in the first menu, before starting a long session.

One caveat belongs on every checklist: kernel-level anti-cheat in some competitive titles can object to virtual controllers. Standalone competitive games are not exempt just because they skip Steam. Check a competitive game’s current rules before relying on a virtual pad there, and expect no mapper to be promised as universally accepted or safe from bans.

An honest boundary, too: DualSense and Switch Pro controllers are not InputMapper inputs, so this method does not extend to those pads. DualSense owners should follow the dedicated DualSense on PC routes instead of forcing a tool that never supported the controller. For alternatives if InputMapper ever stops suiting your library, our InputMapper alternatives page keeps the options current and honest.

More Standalone Games Worth Playing

Indie and DRM-free libraries are where standalone games shine, and a working pad makes the backlog far more approachable.

Browse Standalone Games on Humble

Affiliate link — see our Affiliate Disclosure.

Frequently Asked Questions

Does this method work for itch.io and DRM-free games?

Yes, as long as the game reads XInput. InputMapper maps your DS4 to a virtual Xbox 360 controller at the Windows level, so standalone, itch.io, and DRM-free games see that controller exactly as a Steam game would, with no launcher involved.

Should I use one global profile or a profile for every game?

Start with one clean global profile with a standard Xbox 360 layout — most games need nothing else. Add per-game profiles with auto-switching only for titles that genuinely benefit from remapping, so your setup stays simple and easy to troubleshoot.

Why does my controller only work if I start InputMapper first?

Many games scan for controllers once at startup and never check again. If the virtual controller did not exist when the game launched, the game cannot find it later, so always run InputMapper with your profile active before starting the game.

My button presses are registering twice. What causes that?

That is double input: the game is reading your physical DS4 and the virtual Xbox 360 pad together. Hide the physical controller from games with HidHide v1.5.230 while InputMapper uses it, and make sure no second translator is remapping the same pad.

Epic and GOG Ship No Mapper Layer of Their Own

The Epic Games Launcher and GOG Galaxy ship no built-in controller remapping layer comparable to Steam Input. They are storefronts and launchers: they download, update, and start your games, but they do not translate a DirectInput DualShock 4 into the XInput signal most Windows games expect. If a game on either store has no native DualShock support of its own, the launcher will not add it.

That is why an operating-system-level mapper is the standard workaround for these games. Instead of hoping each launcher or each individual game handles your controller, you fix the problem once in Windows itself. Every game started afterwards simply sees a controller it already understands. For a comparison of the two philosophies, see InputMapper vs Steam Input before you decide which route fits your library.

Route One: An InputMapper Profile That Applies Everywhere

InputMapper is DSDCS freeware, final build 1.7.7452.13622 from May 2020. It maps supported inputs — the DS4 and DS4 V2, Xbox 360 and Xbox One pads, and generic DirectInput and XInput devices — to a virtual Xbox 360 controller created through ViGEmBus 1.22.0, the final archived version of that driver. Because the mapping happens at the Windows OS level, any game that reads XInput can see the virtual pad, no matter which launcher started it or whether a launcher was involved at all.

The routine is simple and identical for Epic and GOG. Install ViGEmBus first, then InputMapper, both available from the download page. Connect your DS4, launch InputMapper, and run a profile with Xbox 360 controller output. Leave InputMapper running, then launch your game from Epic, from GOG Galaxy, or from a desktop shortcut. The game finds an Xbox 360 controller because, as far as Windows is concerned, one is connected. If you have never built a profile, how to use InputMapper walks through the basics step by step.

Download InputMapper

The strength of this route is its indifference to storefronts. A weekly free game on Epic, a classic in your GOG library, and a standalone installer on your desktop all get the same working controller without per-launcher settings, per-game shortcuts, or waiting for either store to add a feature it does not currently offer.

Route Two: Add the Game to Steam and Use Steam Input

The alternative is to add an Epic or GOG game to your Steam library as a non-Steam game shortcut, launch it through Steam, and let Steam Input handle the controller. Steam Input is a capable system, and if you already live inside Steam this can be convenient for an occasional title. For some players and some games, it works well enough that they never need anything else.

Be clear about its limits, though. Steam Input only manages games launched via Steam, plus added shortcuts, and it manages those shortcuts imperfectly. The shortcut has to point at the right executable, launcher updates can break paths, overlays can misbehave, and a game started directly from Epic or GOG — bypassing the Steam shortcut — gets no Steam Input help at all. You also end up maintaining two libraries and launching one store’s games through another store’s client, which many GOG users in particular are trying to avoid. It is a valid route, but it is a per-game workaround rather than a system-wide fix.

The GOG Angle: DRM-Free Installs Need No Launcher at All

GOG’s DRM-free model makes the InputMapper route especially clean. Many GOG games offer standalone offline installers, and the installed game can be run directly, without GOG Galaxy running at all. With InputMapper running first, that standalone game still sees the virtual Xbox 360 controller, because the controller exists in Windows, not inside any launcher.

This is the simplest possible arrangement: download the installer, install the game, start InputMapper with your Xbox 360 output profile, and double-click the game. No launcher in the middle, no shortcut chain to maintain, and no account client deciding how your input is handled. The same applies to DRM-free games you run from a backup folder — if the game reads XInput, the virtual pad is there for it. You can refine button layouts per game later using InputMapper profiles, including profiles that load automatically for specific executables.

Double Input and the One-Mapper Rule

Whichever route you choose, run only one input translator at a time for a given game. If Steam Input is remapping your DS4 for a shortcut while InputMapper is also presenting a virtual pad, a game can receive both signals and produce double input — doubled menu moves, doubled actions, and confusing prompts. Pick the route per game and stick to it.

With the InputMapper route, the other double input risk is a game that reads both your physical DS4 directly and the virtual controller. HidHide v1.5.230 exists for exactly this: it hides the physical pad from games while InputMapper keeps using it. Keep that tool in mind the first time a menu jumps two entries at once; it is a five-minute fix once you know what is happening, as explained in the non-Steam method guide at InputMapper for non-Steam games.

The Anti-Cheat Caveat for Epic and GOG Titles

Most Epic and GOG games are single-player experiences where a virtual controller raises no issues at all. Competitive multiplayer titles are the exception to keep in mind: kernel-level anti-cheat in some competitive titles can object to virtual controllers, regardless of which store sold you the game. The anti-cheat sees a virtual input device, not your good intentions.

Check the specific game’s current stance before using any mapper in ranked or tournament play, and do not trust any tool or guide that promises a virtual controller is universally accepted or safe from bans. For the large majority of story, strategy, and co-operative games on these stores, the OS-level approach is a normal, practical way to use the controller you already own.

Build Your Epic and GOG Library

A working controller makes backlogs more inviting, especially the classics and indie games both stores are known for.

Browse DRM-Free Games on GOG

Browse Game Bundles on Fanatical

Affiliate link — see our Affiliate Disclosure.

Frequently Asked Questions

Why does my DualShock 4 not work with Epic and GOG games?

The Epic Games Launcher and GOG Galaxy ship no built-in controller remapping layer comparable to Steam Input, and most Windows games expect XInput. InputMapper maps your DS4 to a virtual Xbox 360 controller at the Windows level, so those games can see it.

Can I just add an Epic or GOG game to Steam instead?

Yes, by adding it as a non-Steam game shortcut and launching it through Steam so Steam Input applies. The caveats are that Steam Input only manages games launched via Steam, shortcuts can break when launchers update, and the fix does not apply when you start the game directly.

Do GOG games need GOG Galaxy running for InputMapper to work?

No. GOG’s DRM-free standalone installs can run with no launcher at all. Start InputMapper with an Xbox 360 output profile first, then launch the installed game directly and it will see the virtual controller in Windows.

Should I use InputMapper and Steam Input at the same time?

No. Running two translators for the same game can cause double input and conflicts. Choose one route per game — InputMapper for a system-wide fix, or Steam Input for a specific Steam-launched shortcut — and disable the other for that title.

Why a Virtual XInput Pad Is the Simple Path

PCSX2 and RPCS3 are emulators that can bind XInput controllers. That single fact does most of the work in this guide. If Windows has an XInput controller available, each emulator can select it in its pad settings like any physical pad, and every button, stick, and trigger can be bound in the usual way.

InputMapper, the DSDCS freeware tool in its final build 1.7.7452.13622 from May 2020, maps supported physical controllers — the DS4 and DS4 V2, Xbox 360 and Xbox One pads, and generic DirectInput and XInput devices used as inputs — to a virtual Xbox 360 controller through ViGEmBus 1.22.0, the final archived release of that driver. Because the mapping happens at the Windows OS level, any program that reads XInput can see the virtual pad. The emulators are not being patched and no per-game hacks are involved; they are binding a controller Windows genuinely reports as connected.

There are other ways to make a DS4 talk to an emulator, including wrappers inside specific emulator configurations. The advantage of the InputMapper route is consistency: one profile, one virtual controller, and the same behaviour in PCSX2, RPCS3, and your regular PC games. If you already use InputMapper for PC titles, your emulator setup becomes a small extension of a system you already trust, as described in how to use InputMapper.

Set Up InputMapper Before the Emulators

Do the Windows-level setup first, before opening either emulator’s settings. Install ViGEmBus, then InputMapper, both from the download page. Connect your DS4 by USB or Bluetooth, launch InputMapper, and run a profile with Xbox 360 controller output. Then open the Windows Game Controllers panel — search for “Set up USB game controllers” — and confirm an Xbox 360 controller is listed and responds when you test its properties.

Download InputMapper and ViGEmBus

This order matters for the same reason it matters with PC games: programs usually enumerate controllers when they start or when you open their input settings. If the virtual pad appears after an emulator has already scanned for devices, you may need to reopen the pad settings or restart the emulator before it shows up. Starting InputMapper first, every time, removes that confusion entirely.

Selecting the Virtual Controller in PCSX2

In PCSX2, open the controller or pad settings, choose the input source or device list, and select the Xbox 360 controller entry rather than your physical DualShock listing. Then bind each emulated PlayStation 2 control by pressing the matching button or moving the matching stick on your DS4. Work through the face buttons, shoulders, triggers, sticks, D-pad, Start, and Select methodically, then test in the binding screen itself by pressing each control and watching the correct entry light up.

Save that configuration before launching a game. The most common PCSX2 mistake with any virtual pad is binding carefully and then closing the settings without applying them, so the next session starts from a blank or default layout. Once saved, your binding belongs to the virtual controller, which means it will still be correct next time as long as InputMapper is running before PCSX2 starts.

Selecting the Virtual Controller in RPCS3

RPCS3 follows the same pattern through its pads configuration. Open the Pads settings, pick a player slot, choose the XInput-style handler or device option your build presents, and select the Xbox 360 controller as the device for that slot. Bind the controls by pressing them on your DS4, confirm each input registers in the configuration window, and save the pad profile.

Assign the virtual controller to the player one slot for single-player use. If a second player joins, give them a separate physical controller bound directly, rather than trying to split one virtual device across two slots. Keeping one clear owner per slot avoids the mirrored-input problems that make co-operative sessions confusing to debug.

Use a Separate InputMapper Profile per Emulator

PCSX2 and RPCS3 do not need wildly different button maps — both emulate PlayStation pads, so your DS4 layout is already close to natural. What does differ is the fine detail: stick deadzones you prefer for PS2 games, a swapped confirm and cancel habit from a particular library, or trigger behaviour you only want in one emulator. InputMapper profiles let you keep those differences tidy instead of re-editing one global profile every time you switch emulators.

Create one profile for PCSX2 and one for RPCS3, both with Xbox 360 output, and adjust each to taste. The full method, including profiles that switch automatically when a specific program starts, is covered in InputMapper profiles. Start with identical copies of your known-good global profile and change only what an emulator actually needs — small, deliberate differences are far easier to troubleshoot than two profiles built from scratch.

Rumble and Touchpad: An Honest Accounting

Rumble deserves a straight answer. When an emulator sends rumble to an XInput device, that signal reaches the virtual controller, and InputMapper passes standard rumble through to the physical DS4 in normal use. In practice, rumble support also depends on the emulator and the game, so treat working rumble as the expected outcome for standard effects, not a guarantee for every title and every effect style ever shipped.

The touchpad is the honest limit. A virtual Xbox 360 controller has no touchpad, so touchpad-specific input does not carry over as touchpad input — there is simply no equivalent control on the device being emulated at the Windows level. In InputMapper profiles you can assign the touchpad click or areas to ordinary buttons, which covers games that only need an extra button press, but it does not recreate genuine touch gestures inside PCSX2 or RPCS3. Likewise, extras an Xbox 360 pad never had should not be expected to appear magically on the other side. What carries over cleanly is everything an Xbox 360 controller has: buttons, triggers, sticks, D-pad, and standard rumble.

A Note for Retro-Pad Fans and Double Input

Some players prefer a modern retro-style pad for PS2-era games rather than a DualShock 4. That is a perfectly good choice, and a pad that already presents itself as an XInput device can be bound in PCSX2 and RPCS3 directly, with no mapper required. InputMapper matters most when the controller in your hands is not the controller your software expects.

Finally, watch for double input in emulator menus: if presses register twice, the emulator may be seeing both your physical DS4 and the virtual pad. Select only the virtual controller as the bound device, and if a program still reads both, HidHide v1.5.230 can hide the physical pad from other software while InputMapper uses it, as explained in our double input fix and HidHide guide.

See the 8BitDo Ultimate Retro-Style Pad on Amazon

Affiliate link — see our Affiliate Disclosure.

Frequently Asked Questions

Why use InputMapper with PCSX2 and RPCS3 instead of binding my DS4 directly?

PCSX2 and RPCS3 can bind XInput controllers, and InputMapper presents your DS4 to Windows as a virtual Xbox 360 controller. Binding that one standard device gives you a consistent setup that also matches your regular PC games, instead of a separate workaround per emulator.

What should I select in each emulator’s pad settings?

Select the Xbox 360 controller — the virtual device InputMapper creates — in PCSX2’s controller settings and in the player slot of RPCS3’s Pads settings, then bind each control by pressing it on your DS4 and save the configuration.

Does rumble work through InputMapper in emulators?

Standard rumble sent to the XInput device passes through to the DS4 in normal use, though the result also depends on the emulator and the game. Treat standard effects as expected to work rather than guaranteed for every title.

Can I use the DualShock 4 touchpad in PCSX2 or RPCS3 this way?

Not as a touchpad, because a virtual Xbox 360 controller has no touchpad to carry that input. You can assign touchpad clicks to ordinary buttons in an InputMapper profile, but genuine touch gestures do not transfer to the emulators through a virtual XInput pad.

That raises an obvious question. Xbox controllers already speak XInput, and XInput is what most PC games expect — so why route one through InputMapper at all? For plain gaming in a modern title, you usually should not, and this page will say so plainly. But there are four real jobs InputMapper does for an Xbox pad that Windows alone does not: keyboard and mouse output, macros, per-game profiles, and testing. If any of those is your problem, the under-told Xbox side of InputMapper is exactly the tool you have been missing.

New to the software? Grab it from the download page and skim how to use InputMapper first — everything below assumes a working install with ViGEmBus in place.

How Xbox Pads Fit Into InputMapper

InputMapper separates the idea of an input from the idea of an output. Inputs are the physical devices you hold. Outputs are what the software presents to Windows and your games: a virtual Xbox 360 controller (via ViGEmBus), a virtual DS4 (via ViGEmBus), or keyboard and mouse emulation. The official list puts the Xbox 360 Controller and Xbox One Controller on the input side of that equation, and nothing stops an input from being re-expressed as a different output.

So an Xbox pad in InputMapper is not a hack or a side effect of generic device handling — though Generic XInput Devices are also on the official list, which covers many third-party pads in the same family. Your Xbox controller is a named, supported input, and once it appears in InputMapper you can build profiles for it just as you would for a DualShock 4, following the same workflow described in our InputMapper profiles guide.

Reason One: Keyboard and Mouse Output

The most useful reason to map an Xbox pad is to reach software that has no controller support at all. Point-and-click games, older titles, emulators with awkward input pages, media and productivity apps — plenty of PC software only listens to the keyboard and mouse. InputMapper can translate your pad into those signals: face buttons become keys, a stick can drive the mouse pointer, triggers can become clicks. Suddenly the Xbox controller on your desk is a couch-friendly remote for software that was never designed for one.

This works in the other direction for accessibility too. If a game’s native pad support exists but cannot be rebound, mapping the pad to the keys the game does accept can restore control over your own layout. It is not glamorous, but for the person who needs it, it is the difference between playing and not playing.

Reason Two: Macros and Reason Three: Per-Game Profiles

Windows treats your Xbox pad as a fixed device: a button is a button. InputMapper treats it as a starting point. A profile can move actions to where your thumbs prefer them, combine inputs, or bind a sequence to a single press through a macro — handy for repetitive menus, training-mode drills, or turning a multi-key command in a strategy game into one pad press.

Profiles make this sustainable. Instead of one global compromise, you keep a profile per game: one layout for the racing title, another for the keyboard-heavy simulator, another for desktop mouse control. InputMapper’s whole design — the same design DualShock owners use, compared in our InputMapper vs DS4Windows breakdown — is built around switching those mappings as the context changes. Xbox owners simply get to use that machinery too, and most never knew it was there for them.

Reason Four: Testing and the Virtual DS4 Output

Here is the trick developers, streamers, and curious players appreciate most: because InputMapper can output a virtual DS4 (via ViGEmBus), an Xbox pad can be presented to a game as a DualShock 4. Why would you? To test how a game behaves with PlayStation prompts without owning the hardware. To check whether a title’s DS4 support works before recommending it. To follow a guide written for PlayStation button labels while holding the pad you actually have.

The same flexibility helps when troubleshooting. If a game misbehaves with your physical pad, re-presenting it through a clean virtual device is a fast way to learn whether the fault lives in the game, the driver layer, or the hardware. And if the virtual device ever appears alongside the physical one and inputs double up, that is the classic problem covered by our double input fix — with HidHide v1.5.230 as the modern way to hide the physical pad, detailed in the HidHide guide.

The Honest Limits

Now the boundaries, because they matter. Mapping an Xbox pad through InputMapper does not add PlayStation features to it. There is no touchpad hiding in your Xbox controller waiting to be unlocked, and the virtual DS4 output cannot conjure hardware your pad does not have. What changes is the signal your PC sees, not the device in your hands.

Second, a native XInput game that already reads your Xbox controller perfectly gains nothing from the extra layer. Every translation step is a place where configuration can go wrong, and if your only goal is “press A, game receives A,” plug in and play. InputMapper earns its place when you need something Windows does not offer — a keyboard binding, a macro, a profile, a different virtual identity — not as a ritual to perform before every session.

Third, remember what InputMapper is: a finished tool whose final build, 1.7.7452.13622, dates to May 2020. It does its listed jobs well, but plan your setup around the official list rather than hoping for support that was never announced.

Pad Options if You Are Shopping

Any genuine Xbox 360 or Xbox One controller works as an official input. If you are buying a pad primarily for PC and like the Xbox layout, a wired third-party option such as a PowerA controller is a sensible desk pad — it lives in the same XInput world and pairs naturally with the profile workflows above.

See PowerA Controllers

Shop PowerA Controllers on Amazon

Affiliate link — see our Affiliate Disclosure.

Frequently Asked Questions

Is an Xbox controller really an official InputMapper input?

Yes. The Xbox 360 Controller and the Xbox One Controller both appear in InputMapper’s official input list, alongside the DualShock 4, DualShock 4 V2, and generic XInput devices.

Why map an Xbox pad if games already support it natively?

For keyboard and mouse output to software with no controller support, for macros, for per-game profiles with custom layouts, and for testing — including presenting the pad to a game as a virtual DS4 via ViGEmBus. For a native XInput game that already works, you do not need it.

Does InputMapper add PlayStation features to an Xbox controller?

No. It changes the signal your PC sees, including a virtual DS4 output, but it cannot add hardware features such as a touchpad to a controller that does not have them.

What should I do if inputs register twice?

That is the double input problem: the game sees both the physical pad and the virtual device. Hide the physical controller — HidHide v1.5.230 is the modern tool for this — and follow a dedicated double input fix.

The good news mirrors the DualSense story too: the Switch Pro Controller works very well on PC — through other doors. Steam Input supports it natively, DS4Windows also supports Switch Pro and Joy-Con, and a dedicated free tool called BetterJoy exists specifically for Switch controllers on PC. This page walks through all three routes, covers the Bluetooth pairing basics that trip people up the first time, and finishes with a PC-friendly alternative pad worth considering if you are buying fresh. For the InputMapper side of your setup, the software and general workflow live on our download page and in how to use InputMapper.

Why InputMapper Is the Wrong Tool for This Controller

It is worth being precise about what “not supported” means, because a Switch Pro Controller connected to Windows may still show up somewhere as a generic device, and generic DirectInput devices are on InputMapper’s list. That generic appearance is not Switch Pro support — it is an unrecognised pad falling into a catch-all bucket, with none of the controller’s specifics understood and no promise that the result will be complete or pleasant. Planning a setup around it is planning around an accident.

The fair comparison is with controllers InputMapper treats as first-class citizens. A DualShock 4 is named, revision by revision, as our V1 vs V2 guide shows. Even the DualShock 3’s indirect route is spelled out with its prerequisite, in the Magic-NS guide. The Switch Pro gets no such entry — and as with the DualSense, the respectful thing to do is say so and hand you the tools that actually list it. If your desk holds both a DualShock 4 and a Switch Pro, the practical pattern is simple: InputMapper for the DS4, and one of the routes below for the Nintendo pad.

Route One: Steam Input — the Built-In Answer

For most players, Steam Input is the whole solution. Steam has built-in support for the Switch Pro Controller, and the recipe is short. Connect the controller to your PC. In Steam’s controller settings, make sure Switch Pro controller support is enabled. Then add your game to Steam — games bought elsewhere can be added as non-Steam shortcuts — and launch it through Steam, so Steam’s translation layer sits between the controller and the game.

Once that layer is in place, the pad behaves like a first-class PC controller, with per-game layouts you can tweak or borrow from community configurations. The mental model to keep is that Steam is doing the job InputMapper does for a DualShock: receiving a controller the game might not understand, and presenting something it does. If your library already lives in Steam, you may not need anything else on this page. Our InputMapper vs DS4Windows comparison gives useful background on how these mapping layers differ in scope.

Route Two: DS4Windows and Route Three: BetterJoy

Despite its PlayStation-flavoured name, DS4Windows also supports Switch Pro and Joy-Con — support the Ryochan7 line added during its run, making the tool a broader controller hub than its name suggests. If you already run DS4Windows for a DualShock or DualSense, using it for your Switch Pro as well keeps your mapping life in one place, with the same profiles-and-output workflow across pads. (Note the version landscape: the Ryochan7 line ended at 3.3.3 in December 2023, and the current continuation is ds4windowsapp, at v3.5 as of February 2026; our DS4Windows install guide covers getting set up.)

The third route is the specialist: BetterJoy, a known free tool built specifically for Switch controllers on PC — Joy-Con and Switch Pro alike. Where the other routes are general platforms that include Switch support, BetterJoy’s entire reason to exist is Nintendo hardware, which makes it a natural pick if your setup is Switch-centric, if you want Joy-Con handled as a pair or individually, or if the general tools have not behaved with your particular configuration. There is no wrong choice among the three; there is only the one that fits how many platforms your desk already runs.

Whichever layer you choose, use exactly one per game. Two translators stacked together is how inputs double up — and if that happens, the remedy is in our double input fix, with HidHide as the modern hiding tool.

Bluetooth Pairing Basics for Switch Pro on Windows

The Pro Controller’s one quirk is that its sync control is small and easy to forget. The sync button sits on top of the controller, next to the USB-C port — a tiny round button. To pair: open Windows Bluetooth settings and choose to add a device, then press and hold the sync button until the player indicator lights on the bottom of the controller start running, signalling that the pad is discoverable. Select the controller in Windows’ device list and let pairing finish; the lights settle once the connection is made.

A wired connection over USB-C also works and is the fastest way to confirm the controller and your chosen tool see each other before you debug anything wireless. Two habits will save you grief afterward. First, remember that pressing the sync button is also how the controller starts looking for a new home — if you also use the pad with a Switch console, expect each device change to involve re-pairing on one side or the other. Second, if Windows shows the controller paired but your tool sees nothing, remove the pairing and repeat the process cleanly rather than stacking fixes; a fresh bond solves a surprising share of Switch Pro mysteries.

If You Are Buying a Pad for PC Anyway

The Switch Pro is a lovely controller, and the routes above make it a real PC pad. But if you are purchasing specifically for PC and do not already live in Nintendo’s ecosystem, a PC-first pad such as the 8BitDo Ultimate line is worth a look: designed to move between devices without console allegiances, and free of the pairing etiquette that comes with sharing a controller with a console.

Shop 8BitDo Ultimate Controllers

Affiliate link — see our Affiliate Disclosure.

Already own the Pro Controller? Then buy nothing. Pair it, pick Steam Input or one of the mapper routes, and play — just do not ask InputMapper to be the middleman it never claimed to be.

Frequently Asked Questions

Does InputMapper support the Switch Pro Controller?

No. The Switch Pro Controller is not in InputMapper’s official input list, which covers the DualShock 4 and V2, Xbox 360 and Xbox One controllers, the DualShock 3 and Move Navigation Controller via Magic-NS, and generic DirectInput and XInput devices. Do not expect InputMapper to handle it.

What is the easiest way to use a Switch Pro Controller on PC?

Steam Input. Enable Switch Pro support in Steam’s controller settings, add your game to Steam (non-Steam games can be added as shortcuts), and launch through Steam so its translation layer handles the controller.

What other tools work with Switch Pro and Joy-Con?

DS4Windows also supports Switch Pro and Joy-Con, and BetterJoy is a dedicated free tool built specifically for Switch controllers on PC, covering both Joy-Con and the Switch Pro Controller.

How do I pair a Switch Pro Controller with Windows over Bluetooth?

Open Windows Bluetooth settings and start adding a device, then press and hold the small sync button on top of the controller, next to the USB-C port, until the player lights start running. Select the controller in the list and let pairing complete.

That listing makes InputMapper a genuinely useful home for older and specialist hardware. A device Windows can see as a DirectInput controller can be brought into InputMapper, given a profile, and re-expressed as a virtual Xbox 360 controller (via ViGEmBus), a virtual DS4 (via ViGEmBus), or keyboard and mouse input. For games that only accept XInput — or only accept a keyboard — that translation is often the difference between a controller gathering dust and a controller back in service.

This page explains how InputMapper treats generic DirectInput devices, what profiles can and cannot do for them, the dead-zone basics every stick and wheel owner should understand, and the point at which a different, simpler tool is the better answer. If you need the software itself, it is on the download page, with the general workflow in how to use InputMapper.

What Counts as a Generic DirectInput Device?

Think in families rather than brand names. Arcade sticks and fight sticks are the classic case: many present themselves to Windows as a generic DirectInput device with a stick and a row of buttons, whatever artwork is on the panel. Older gamepads from the pre-XInput era are DirectInput by birth. Racing wheels and flight sticks have a long DirectInput heritage too, often with more axes than a standard pad offers. One-off and DIY controllers — a button box, a retro adapter, a converted cabinet control panel — usually arrive in Windows as generic devices as well.

The practical test is simple: if Windows’ own controller panel can see the device and its buttons and axes respond there, you have something InputMapper can generally work with as a generic input. If Windows cannot see it at all, fix that first — no mapping tool can profile hardware the operating system has not detected.

How InputMapper Profiles Treat Generic Devices

A profile is where a generic device becomes your device. Because generic hardware has no standard layout — one stick has eight buttons, another has twelve, a wheel adds pedals and a shifter — InputMapper cannot assume what anything does. You teach it: this button confirms, that axis steers, this switch fires a keyboard key. The result is saved as a profile, and profiles are per-device and per-game, exactly as described in our InputMapper profiles guide.

Two consequences follow. First, patience during setup is the price of flexibility: expect to spend a few minutes pressing each control and assigning it, rather than having a picture-perfect layout appear automatically. Second, the payoff is real customisation. A wheel’s paddle can become a keyboard shortcut. An arcade stick can output pure keyboard presses for a game that has no controller support whatsoever. A pad with an awkward button order can be normalised so it matches the layout every guide assumes.

Choose your output to match the target. Most modern games are happiest receiving the virtual Xbox 360 controller. Keyboard and mouse output is the universal fallback for software that ignores pads entirely. The virtual DS4 output exists too, but for generic hardware it is rarely the point — there is no DualShock hardware on your side of the cable to represent.

Dead-Zone Basics for Sticks, Wheels, and Older Pads

Generic and older hardware makes one setting impossible to ignore: the dead zone. A dead zone is the small region around a stick, wheel, or pedal’s resting position where input is treated as zero. It exists because real hardware is imperfect. A worn stick may not return to exactly centre; a wheel may report a whisper of movement while sitting still. Without a dead zone, menus scroll by themselves and cars drift gently into walls.

The balancing act is simple to state and easy to feel. Too little dead zone and you get drift and phantom input. Too much and the control feels dead and vague, because your first real movement is swallowed before the game sees anything. The right value is the smallest one that keeps the device quiet at rest — set it per device, in that device’s profile, and accept that your ten-year-old pad may honestly need more than your new stick does. Test at rest first, then in motion: sit in a menu and watch for wandering, then make small movements and confirm they register smoothly.

When XOutput Is the Simpler Tool

Honesty about scope matters here. If your entire goal is “this DirectInput device should look like an Xbox 360 controller so my game accepts it” — one device, one conversion, nothing else — then a dedicated converter may be all you need, and InputMapper’s profile system is more machinery than the job requires. That is precisely the comparison we lay out in InputMapper vs XOutput: XOutput’s whole purpose is that single DirectInput-to-XInput conversion, while InputMapper is a broader mapping platform with profiles, macros, keyboard output, and multiple virtual outputs.

Choose InputMapper when you want the broader platform: several games needing several layouts, keyboard bindings, a mix of generic and name-brand devices in one place, or a DualShock in the same setup as your stick. Choose the simpler tool when the job is a single conversion and you value the shortest path. Neither answer is a failure — matching tool weight to job weight is just good setup hygiene. Our broader InputMapper vs DS4Windows comparison can also help you place both tools in the current landscape.

A Modern Generic Pad, If You Are Starting Fresh

If your old pad finally gives up, or you want one controller that moves easily between devices, a modern multi-mode pad in the 8BitDo Ultimate style is the natural successor to the generic tradition: broadly compatible, unconcerned with console loyalties, and at home on a PC desk. It is a good example of where the generic category has ended up — the flexibility of a no-name device, with modern build quality.

Shop 8BitDo Ultimate Controllers

Affiliate link — see our Affiliate Disclosure.

And if a newly mapped device ever responds twice to one press, you are seeing the physical and virtual controllers side by side. Our double input fix explains the clean solution.

Frequently Asked Questions

Are generic DirectInput controllers officially supported by InputMapper?

Yes. Generic DirectInput Devices are a named entry in InputMapper’s official input list, along with Generic XInput Devices. If Windows can detect your device and its inputs, InputMapper can generally profile and map it.

What kinds of hardware does this cover?

Typical examples include arcade sticks, older pre-XInput gamepads, racing wheels, flight sticks, and DIY or no-name controllers that Windows sees as generic DirectInput devices.

What is a dead zone and why does my old pad need one?

A dead zone is the small area around a control’s resting position that is treated as zero. Worn sticks and wheels often report slight movement at rest, so a modest dead zone prevents drift — use the smallest value that keeps the device quiet.

When should I use XOutput instead of InputMapper?

When your only goal is converting one DirectInput device into an Xbox 360 controller for a game, XOutput’s single-purpose conversion is simpler. InputMapper is the better fit when you need profiles, macros, keyboard output, or several devices managed together.

So why does a comparison page exist at all? Because the two revisions look almost identical on a shelf, listings online rarely say which one you are buying, and owners reasonably want to know whether the V2 does anything the V1 cannot do inside InputMapper. The short answer is reassuring: in terms of mapping, profiles, and virtual output, there is no fundamental difference. The differences are hardware differences — how you identify the pad, how its light bar behaves, and how it can talk to your PC over USB. This page walks through all three, then gives honest buying advice for 2026.

If you have not installed the software yet, start with our download page and the walkthrough on how to use InputMapper, then come back here to confirm which revision is in your hands.

How to Identify Your Revision in Ten Seconds

The fastest reliable check is the model number printed on the label on the back of the controller. The original DualShock 4 is model CUH-ZCT1. The revised controller is model CUH-ZCT2, usually shortened to DS4 V2. If the label is worn or missing, use the visual check instead.

Look at the touchpad from the front. On the V2, a thin strip of the light bar is visible along the top edge of the touchpad, so you can see the controller’s colour glow from the player’s side of the pad. On the V1, the light bar faces entirely away from you, on the back of the controller, and nothing shows through the touchpad. That touchpad light strip is the single easiest way to tell the revisions apart in a photo — which matters when you are judging a second-hand listing from pictures alone.

Other clues exist but are weaker. Later shells and colourways tend to be V2 units simply because they were manufactured after the revision replaced the original on production lines, and the V2’s sticks and buttons have a slightly different finish. Do not rely on colour or feel. Model number first, touchpad strip second.

What Actually Differs Between V1 and V2

Beyond the light strip, the headline hardware change is communication. The V2 added a USB communication option in addition to Bluetooth. In plain terms, when a V2 is plugged in with a cable, the controller can send its input over that cable. A V1 plugged into a PC or console is, in the classic setup, charging over the cable while the actual input still travels over Bluetooth — which is why V1 owners sometimes unplug a “wired” controller and notice nothing change, or pair it and wonder why the cable made no difference to latency or dropouts.

For PC use this gives the V2 a practical edge. A true wired data connection is the simplest way to rule out wireless interference, pairing quirks, and battery anxiety during a long session. It also makes troubleshooting cleaner: if something misbehaves over a cable, you know the problem is in software or configuration, not in the radio link. With a V1, the honest advice is to treat Bluetooth as the connection and the cable as power.

Everything else you care about for gaming is effectively the same platform: the same button layout, the same touchpad, the same sticks and triggers, and the same role in your setup. Neither revision gives you extra mappable buttons over the other, and neither is locked out of any InputMapper feature.

Inside InputMapper: Nothing Fundamental Changes

InputMapper’s official input list names both revisions explicitly, and that listing is the important fact. Both are native inputs, not generic devices. Once connected, each revision can be mapped button-for-button, assigned to a profile, and sent to any of InputMapper’s outputs: a virtual Xbox 360 controller (via ViGEmBus), a virtual DS4 (via ViGEmBus), or keyboard and mouse emulation.

That means everything covered in our guide to InputMapper profiles — per-game mappings, macros, swapped sticks, keyboard bindings for games with no controller support at all — works the same way on a CUH-ZCT1 as on a CUH-ZCT2. A profile built for one revision does not need rebuilding for the other. If you also own a PlayStation pad from the previous generation, note the contrast: the DualShock 3 is only on the list via a dongle, as explained in our DualShock 3 and Magic-NS guide. The DS4 revisions need no such bridge.

If your PC ever shows two inputs for one controller — the game responding twice to a single press — that is a separate, well-known issue with a dedicated fix. See our double input fix and the modern hiding tool covered in the HidHide guide. It can happen with either revision and has nothing to do with which model you bought.

USB vs Bluetooth: Practical Notes

V2 over USB: plug in, let Windows settle, then open InputMapper and confirm the controller appears. This is the most deterministic route and the one we recommend while you are first setting up profiles. Once everything works wired, try Bluetooth and compare.

V2 over Bluetooth: pair it like any DS4, and it behaves like the V1 wirelessly — convenient for couch play, subject to the usual realities of shared radio space, distance, and battery level.

V1 in general: plan around Bluetooth as your input path. Keep the controller charged, keep the wireless path reasonably clear, and do not diagnose a Bluetooth symptom as a cable fault when the cable was only ever delivering power.

Whichever revision and connection you use, the setup basics in our guide to connecting a PS4 controller to PC apply unchanged.

Which Should You Buy in 2026?

If you find both revisions at a fair price and both are genuine, buy the V2. The USB communication option and the player-facing light strip are small quality-of-life wins, and a V2 will generally be the younger controller with less wear on its sticks and battery. The V1 remains a perfectly good InputMapper controller, though — if the V1 is the one in good condition from a seller you trust, there is no mapping feature you are giving up.

The bigger issue in 2026 is authenticity. Genuine DualShock 4 controllers are increasingly hard to find new, as the controller is long out of its production prime, and the market is full of lookalike pads that copy the shell while behaving like generic devices inside. A counterfeit may still work as a basic gamepad, but it is not the device on InputMapper’s official list, and its touchpad, sticks, and wireless behaviour may disappoint. Buy from reputable sellers, check the model number and touchpad strip against the listing photos, be suspicious of prices that look too good, and test the controller as soon as it arrives while a return is still possible.

Check DualShock 4 Availability

Affiliate link — see our Affiliate Disclosure.

Frequently Asked Questions

How can I tell a DualShock 4 V1 from a V2?

Check the model number on the back label: CUH-ZCT1 is the V1 and CUH-ZCT2 is the V2. You can also look at the touchpad — the V2 shows a strip of the light bar along the top edge of the touchpad, while the V1 does not.

Does InputMapper treat the DS4 V1 and V2 differently?

No, not in any fundamental way. Both the Sony DualShock 4 and the Sony DualShock 4 V2 are separate first-class entries in InputMapper’s official input list, and profiles, mapping, and virtual output work the same for both.

What is the main advantage of the V2 on PC?

The V2 added a USB communication option in addition to Bluetooth, so a plugged-in V2 can send input over the cable itself. That gives you a simple, stable wired connection for setup and troubleshooting.

Is a V1 still worth buying in 2026?

Yes, if it is genuine and in good condition — you lose no InputMapper features. The main caution applies to both revisions: genuine DualShock 4 controllers are increasingly hard to find new, so buy carefully and watch for counterfeits.

This page exists because that one line is easy to skim past, and readers have wasted evenings trying to pair a DualShock 3 directly and wondering what they did wrong. The answer is: nothing — the hardware step was missing. Below you will find what you need, how the dongle pairing concept works, what you can honestly expect once it is running, the same prerequisite that applies to the PlayStation Move Navigation Controller, and the basic troubleshooting order when things refuse to cooperate.

Already own the dongle? Then the rest of your setup follows the normal path: software from the download page, workflow from how to use InputMapper, and layouts from the profiles guide.

What You Need

The shopping list is short, and one item on it is non-negotiable.

Note what is not on the list: any claim that a plain Bluetooth adapter will do. Whatever a DualShock 3 can be persuaded to do with other software stacks is a different project. For InputMapper, the official, documented route is the Magic-NS — the same way the DualShock 4 needs no help at all, as our PS4 controller connection guide shows by contrast.

How It Works: The Dongle Is the Translator

It helps to picture the signal chain. Your DualShock 3 talks to the Magic-NS. The Magic-NS — a Mayflash wireless adapter that plugs into a USB port — translates the controller into a standard device your PC understands, presenting it through its XInput or DirectInput modes. InputMapper then sees that presented device as its input, and from that point everything is normal InputMapper: assign buttons, build a profile, and output to a virtual Xbox 360 controller (via ViGEmBus), a virtual DS4 (via ViGEmBus), or keyboard and mouse.

That middle step explains both why this works and where its limits come from. InputMapper is mapping what the dongle presents, not interrogating the DS3 directly. Whatever the dongle’s modes carry across — the standard buttons and sticks — is what you get to map.

Setup Steps

Step 1: Set the dongle’s mode. The Magic-NS has multiple operating modes, selected on the adapter itself, which change how it presents a connected controller to the PC. For use with InputMapper, choose one of its standard controller modes — XInput or DirectInput — so the DS3 arrives as a conventional gamepad. If the controller later behaves oddly or does not appear, the mode is the first suspect; the modes exist for different host devices, and the wrong one will not present the pad the way Windows and InputMapper expect.

Step 2: Pair the DualShock 3 to the dongle. The pairing concept is that the DS3 bonds to the adapter, not to Windows. Typically this involves connecting the controller to the adapter by cable for the initial handshake, then disconnecting and letting the wireless link take over, following the adapter’s own pairing instructions for a PS3 controller. Once paired, the dongle remembers the controller, and future sessions should reconnect through the adapter without repeating the ceremony.

Step 3: Confirm the chain in order. Verify each link before blaming the next one. Does the dongle respond and indicate a connected controller? Does Windows see a gamepad and respond to its buttons in the controller panel? Only then open InputMapper and confirm the device appears as an input. This order — dongle, Windows, InputMapper — will save you more time than any single tip on this page.

Step 4: Build your profile. Press every button and assign it deliberately; do not assume a default layout matches how the dongle presents the pad. Save the profile with a name you will recognise, and test it in a game menu before a session that matters.

What Works — and What Not to Expect

What works is the core of the controller: the standard buttons and the analog sticks, carried through the dongle’s XInput/DirectInput presentation and then mapped by InputMapper like any other input. For the large job of “use my old, familiar, well-made DS3 in PC games,” that is the whole requirement, and it is a satisfying piece of hardware recycling.

What we will not promise is the DualShock 3’s exotic hardware character — most famously its pressure-sensitive face buttons. Keep your expectations at the level of the dongle’s standard controller modes: buttons and sticks, presented conventionally. If a game or guide describes a feature that depended on the DS3 talking natively to a PlayStation 3, do not plan around it surviving two layers of translation. This honesty is deliberate. The DS3-through-Magic-NS route is good at what it is, and overselling it only produces disappointed setups.

The PlayStation Move Navigation Controller Note

The DualShock 3 is not the only device with this exact arrangement. InputMapper’s official list also includes the PlayStation Move Navigation Controller (via Magic-NS Dongle) — the same prerequisite, the same bridge. That one-handed navigation controller can be a surprisingly comfortable companion device for certain games and desktop control, but the rule is identical: no Magic-NS, no input. If you are buying the dongle for a DS3, you are also unlocking the listed route for the Navigation Controller.

Troubleshooting Basics

The DS3 does not appear in InputMapper. Walk the chain backwards: is the dongle in a standard XInput/DirectInput mode, does it show the controller as connected, and does Windows itself respond to the pad? InputMapper cannot list a device Windows has not received.

It worked yesterday and not today. Re-pair the controller to the dongle — wireless bonds get forgotten, especially if the DS3 has since been connected to a console. Also confirm the dongle’s mode has not been switched accidentally.

Inputs register twice. If the game sees both the presented device and InputMapper’s virtual output, that is the classic double input problem; see the double input fix and consider hiding the physical device with HidHide, covered in our HidHide guide.

Everything connects but the layout is wrong. Rebuild the profile rather than editing around it, pressing each control in turn. With a translation layer in the middle, assumed layouts are guesses.

Frequently Asked Questions

Can I use a DualShock 3 with InputMapper without a Magic-NS?

No. InputMapper’s official input list gives the entry as Sony DualShock 3 (via Magic-NS Dongle). The Mayflash Magic-NS adapter is a required prerequisite, not an optional extra — there is no native DS3 support.

What does the Magic-NS actually do in this setup?

It is the translator in the middle. The DualShock 3 pairs to the dongle, the dongle presents it to your PC through its XInput or DirectInput modes, and InputMapper maps that presented device like any other input.

Will the DS3’s pressure-sensitive buttons work?

Do not count on it. Expect the standard buttons and sticks as presented by the dongle’s conventional controller modes. Features that depended on the DS3 talking natively to a PlayStation 3 should not be assumed to survive the translation.

Does the PlayStation Move Navigation Controller need the dongle too?

Yes. It is listed in InputMapper’s official inputs as PlayStation Move Navigation Controller (via Magic-NS Dongle) — exactly the same prerequisite as the DualShock 3.

None of that means your DualSense is useless on PC. Quite the opposite: in 2026 it is one of the best-supported premium controllers on the platform — just not through InputMapper. This page explains the InputMapper situation precisely, then points you to the two routes that actually work, DS4Windows and Steam Input, with an honest account of what each gives you and the one cable-related caveat nobody should hide. If you came here ready to buy a DualSense for PC, you will find the buying section at the end — and the honesty above is exactly why you can trust it.

Can You Use a DualSense With InputMapper? No — and Here Is the Detail

Precision matters, so let us separate “listed support” from “something appears on screen.” Because Generic DirectInput Devices are an official InputMapper input category, a DualSense connected to Windows might show up as a generic DirectInput device. That is not DualSense support. It means a generic bucket caught an unrecognised pad: you would get, at best, a partial and unglamorous mapping experience with none of the controller’s identity or features understood — not the touchpad behaviour, not the gyro, and certainly not the haptics or adaptive triggers that are the entire reason the DualSense exists.

Compare that with how the official list treats hardware InputMapper genuinely supports: named entries, revision by revision, as with the two DualShock 4 models compared in our DS4 V1 vs V2 guide, or with an explicit prerequisite, as with the DualShock 3 via Magic-NS. The DualSense gets neither treatment, because the software was finished before Sony announced the controller’s details to the world. Anyone who tells you InputMapper “supports DualSense” is selling you the generic fallback as if it were the real thing. If PlayStation pads through InputMapper are your goal, the DualShock 4 is the controller this site is about — see connecting a PS4 controller to PC.

What Actually Works in 2026: DS4Windows

The first real route is DS4Windows, the community mapping tool for PlayStation controllers on PC. Be aware there are two chapters to its story. The well-known Ryochan7 line ended at version 3.3.3 in December 2023. Development continues today as the ds4windowsapp continuation, which reached v3.5 in February 2026 — that current continuation is the one to install, not an old download of the discontinued line.

With it, a DualSense becomes a fully mapped PC controller: buttons, sticks, touchpad, and gyro can all be put to work, with the per-game profiles and output control PC players expect from a mature mapper. Our step-by-step DS4Windows install guide walks through getting it running, and our InputMapper vs DS4Windows comparison explains how the two tools’ eras and device lists differ — the short version being that modern PlayStation hardware belongs with the actively developed tool. If you ever see double inputs after setting it up, the cause and cure are the same as ever: hide the physical pad, with HidHide v1.5.230 as the current tool, as covered in our HidHide guide and the double input fix.

What Actually Works in 2026: Steam Input

The second route needs no separate mapper at all. Steam Input — Steam’s built-in controller layer — supports the DualSense directly. Add your games to Steam (including non-Steam games added as shortcuts), enable PlayStation controller support in Steam’s controller settings, and Steam translates the DualSense for the game, with per-game layouts you can adjust or take from the community. For players whose library already lives in Steam, this is often the zero-install answer, and it keeps working game after game without a separate utility in the tray.

Choosing between them is a matter of shape, not quality. Steam Input is the convenient default inside Steam’s walls. DS4Windows is the system-wide tool that also covers games and launchers outside Steam, with deeper mapping control. Many DualSense owners end up with both, using Steam Input inside Steam and DS4Windows everywhere else — just take care not to run two translation layers into the same game at once.

The Wired Caveat: Adaptive Triggers and Haptics

Now the limitation to plan around. The DualSense’s signature features — its advanced haptics and adaptive triggers — are game-dependent on PC. Only titles that specifically implement them will use them; most games will treat the pad as an excellent conventional controller, which is no insult, but it is not the full PlayStation 5 experience either. And where those features are implemented, they generally require a wired USB connection. Bluetooth play is fine for standard input, but if you bought the controller for its triggers and haptics, expect to play the supporting games with a cable in. Treat any claim of full wireless feature support across PC gaming with suspicion — the honest summary is: wired, in the games that support it.

Buying a DualSense for PC

With expectations set correctly, the DualSense is a genuinely good PC purchase: a premium pad with a real touchpad and gyro, supported properly by both routes above, and at its best — triggers and haptics included — in wired play in supporting titles. Pair it with a charging dock and the desk setup stays tidy: drop the pad on the dock after a session instead of rotating cables, and keep the good cable free for wired feature play.

Shop the DualSense on Amazon

Shop Charging Docks

Affiliate link — see our Affiliate Disclosure.

Our final piece of buying advice doubles as usage advice: budget for a decent USB cable and use the DualSense wired whenever you are playing a title that implements its special features. That single habit is the difference between owning the controller’s headline features and merely owning the controller.

Frequently Asked Questions

Does InputMapper support the DualSense?

No. InputMapper’s final build 1.7.7452.13622 dates to May 2020, and the DualSense launched on November 12, 2020 — about half a year later. The DualSense is not in InputMapper’s official input list; at best it may appear as a generic DirectInput device, which is not real support.

What should I use for a DualSense on PC instead?

DS4Windows — the current ds4windowsapp continuation, at v3.5 as of February 2026 — for system-wide mapping, or Steam Input for games in your Steam library. Both give you proper mapping including the touchpad and gyro.

Do adaptive triggers and haptics work on PC?

Only in games that specifically implement them, and generally only over a wired USB connection. Most PC games will use the DualSense as a conventional controller, so plan to play wired for the fullest feature set.

Which DS4Windows version is current?

The Ryochan7 line ended at 3.3.3 in December 2023. The current continuation is ds4windowsapp, which reached v3.5 in February 2026 — install that one rather than an old build.