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.

What a Profile Actually Contains

• Output device: a virtual Xbox 360 controller, a virtual DS4, or keyboard and mouse output, all created through ViGEmBus.
• Button mapping: what each physical button sends to the output device.
• Stick and trigger behavior: including dead zones and sensitivity choices covered in our lightbar, rumble and dead zone settings guide.
• Touchpad behavior: for example using the pad as a mouse, as in DS4 touchpad as mouse.
• Macros: recorded combinations, covered in InputMapper macros.

Changing a profile never changes the controller itself. Unplug the DualShock 4 and use it on a console and it behaves completely normally, because every remapping lives in the profile on the PC.

Create Your First Profile

1. Connect a supported controller — a DualShock 4 or DS4 V2 is ideal — and confirm InputMapper lists it. If it does not appear, fix that first with the controller not detected guide.
2. Create a new profile from the profiles area of InputMapper.
3. Set the output to the virtual Xbox 360 controller. This is the safest default, because most PC games are built for XInput and will recognize it immediately.
4. Leave the default mapping in place, save the profile, and test it in the Windows game controller panel before changing anything.

Start boring on purpose. A working default profile is your known-good baseline: when an experimental profile misbehaves in a game, switching back to the baseline tells you instantly whether the problem is your custom mapping or something deeper in the setup, such as the driver chain described in how to use InputMapper.

Name Profiles So Future You Can Read Them

Profile names are free text, so develop a small naming habit early, before the list grows:

• Lead with the purpose or game: “Racing – Xbox Output”, “Desktop – Touchpad Mouse”, “Shooter – Low Dead Zone”.
• Include the output type when you mix outputs. Two profiles called “Default” and “Default 2” will confuse you within a week.
• Mark experiments clearly, for example with a trailing “– test”, and delete failed experiments instead of letting them pile up.
• Keep one untouched profile called something like “Baseline Xbox 360” that you never edit. Duplicate it when you want to experiment.

This sounds fussy until you have fifteen profiles and a game update breaks one mapping. Clear names turn a troubleshooting session into a quick comparison between a working profile and a broken one.

Bind a Device to a Profile

Creating a profile does not apply it. A profile takes effect when it is bound — assigned — to a connected device. With the controller connected, select the device in InputMapper and assign the profile you want it to use. Press a few buttons and confirm the output responds as expected before launching a game.

Binding matters most with more than one controller. InputMapper’s official input list includes the DualShock 4, DS4 V2, Xbox 360 and Xbox One controllers, the DualShock 3 only via a Mayflash Magic-NS dongle, PS Move Navigation via Magic-NS, and generic DirectInput and XInput devices. Each connected device can carry its own profile, so a DualShock 4 can run a touchpad profile while an Xbox controller runs a plain passthrough profile at the same time. If the wrong mapping appears in a game, check the binding first — the usual culprit is the right profile bound to the wrong device, or a leftover profile still assigned from a previous session.

Build Per-Game Profiles

Per-game profiles are where the system pays off. Different games want different things:

• A racing game may want a larger stick dead zone and gentle trigger behavior.
• A shooter may want a small dead zone and a macro or two on spare buttons.
• A strategy or desktop profile may want the touchpad as a mouse and keyboard shortcuts on the face buttons.
• An emulator profile may want a virtual DS4 output instead of Xbox 360 output, depending on the emulator — see InputMapper with emulators for examples.

Build each per-game profile by duplicating your baseline, renaming the copy for that game, and changing only what that game needs. Change one group of settings at a time and test in the game’s menus or a safe area, so you know which change helped and which one hurt.

Auto-Switching, In Concept

Players often ask for profiles that switch automatically when a game starts. Think of auto-switching as a convenience layer on top of binding: the right profile still has to exist, be named clearly, and be tested manually first. Set up and verify your per-game profiles by hand, keep names consistent, and treat any automatic switching as an optional extra rather than the foundation. A tidy, well-named library works perfectly well with a five-second manual switch before you play, and it never surprises you mid-session.

Where Profiles Are Stored

InputMapper keeps its data, including profiles, under the DSDCS folder in your roaming application data: %AppData%\DSDCS\InputMapper — in practice, the AppData\Roaming folder inside your Windows user profile. You do not need to open this folder for everyday use, but knowing it exists matters for two reasons. First, reinstalling Windows or moving to a new PC will leave your profiles behind unless you copy that folder. Second, if you ever troubleshoot with someone, this is the folder they will ask about.

Because everything you build lives there, back it up before a reinstall, a major cleanup, or a PC move. Our companion guide, back up InputMapper profiles, shows how to copy the folder, restore it on a new machine, and keep a sensible backup habit. Do that once and a rebuilt PC becomes a ten-minute restore instead of an evening of recreating every mapping from memory.

Frequently Asked Questions

Where does InputMapper store its profiles?

InputMapper stores profiles under %AppData%\DSDCS\InputMapper, inside the AppData\Roaming folder of your Windows user profile. Copy that folder to preserve your profiles before reinstalling Windows or moving to a new PC.

Can each controller use a different profile?

Yes. A profile takes effect when it is bound to a connected device, and each device can carry its own profile. A DualShock 4 can run a touchpad profile while an Xbox controller runs a plain profile at the same time.

Should I edit my only working profile?

No. Keep one untouched baseline profile with the default mapping and Xbox 360 output. Duplicate it for experiments and per-game setups, so you always have a known-good profile to switch back to when testing.

Do profiles change anything on the controller itself?

No. All mapping lives in the profile on your PC. The controller hardware is unchanged, so the same DualShock 4 behaves completely normally when you plug it into a console.

How Macros Fit Into a Profile

InputMapper outputs a virtual Xbox 360 controller, a virtual DS4, or keyboard and mouse input through ViGEmBus. A macro is an extension of that mapping: instead of a button simply sending one output, it sends a small script of outputs. Because macros are saved in the profile, they travel with it — back up the profile folder under %AppData%\DSDCS\InputMapper and your macros are backed up too, as explained in back up InputMapper profiles.

Before building macros, make sure the underlying profile works without them. Follow InputMapper profiles to create a baseline, bind it to your DualShock 4, and test the plain mapping in a game. A macro built on a broken baseline is just a faster way to send the wrong input.

The Macro Editor, In Concepts

Exact clicks vary in feel, but every macro you build follows the same four ideas:

• Trigger: the physical button (or combination) that starts the macro. Pick a button you will not hit by accident mid-game — a spare or less-used input is ideal.
• Steps: the sequence itself. Steps can be controller outputs, keyboard keys, or mouse actions, pressed and released in order.
• Timing: the gap between steps. Games need time to register each input, so a sequence replayed instantly may drop steps. Small pauses between steps make macros far more reliable.
• Press pattern: whether the macro fires once per press, holds while you hold the trigger, or repeats. One-shot is right for shortcuts; repeating patterns are where you should stop and think about fairness, as discussed below.

Recording a Button Combination

The simplest macro records a combination you would otherwise chord with two hands or awkward fingers. Open the macro editor from your profile, choose the trigger button, record the combination by pressing the sequence you want — for example two face buttons and a shoulder button in a specific order — then stop recording and save. Test the macro somewhere harmless, such as a game’s menu or a text document if the output includes keyboard keys, and adjust the timing if steps are missed. Short combinations record most reliably; long fighting-game style strings are sensitive to timing and to the game’s own input window, so build them up a few steps at a time.

Practical Example 1: A Screenshot Combo

Couch players lose screenshots because the keyboard shortcut is across the room. A macro fixes that:

1. Create or duplicate a profile for general gaming.
2. Pick a trigger you rarely use in that game.
3. Record a keyboard output sequence matching your screenshot tool’s shortcut — a modifier key plus a function or letter key, pressed together and released.
4. Add a small pause between press and release so the shortcut registers cleanly.
5. Save, bind the profile, and test it in a game where screenshots are safe to take.

The same pattern works for recording clips, toggling an overlay, or muting a microphone app — any single keyboard shortcut can ride on a controller button. Our touchpad as mouse guide pairs well with this, since touchpad clicks plus one shortcut macro cover most desktop chores from the sofa.

Practical Example 2: Push-to-Talk Style Keys

Voice chat apps usually expect a keyboard key held down to talk. A controller version works like this: assign a macro, or a direct keyboard mapping, so that holding a chosen controller button holds the voice app’s talk key, and releasing the button releases it. Set the voice app to the same key, then test in the app’s own input indicator before joining a channel. Keep the trigger away from buttons you mash in combat, or your team will hear your most excited moments in full. This is a mapping convenience, not a special voice feature — InputMapper is sending keyboard input, and the voice app cannot tell the difference.

Keyboard and Mouse Outputs: Ground Rules

• Test keyboard macros in a harmless window first. A macro that types into a game is delightful; the same macro typing into a chat box or a password field is not.
• Keep sequences short. The longer the chain, the more places timing can break, especially if the game stutters or a menu opens mid-sequence.
• Name macros inside the profile where the editor allows notes or clear profile names, so future you remembers why a button types three keys. Per-game profiles, as covered in the profiles guide, keep game-specific macros from leaking into other games.
• Remember that some games capture the keyboard differently when menus are open. Test your macro in real gameplay, not only on the title screen.

Caution: Online Games and Anti-Cheat

This is the part to read twice. Macros that automate gameplay — repeating attacks, one-button combos that replace skill, or rapid repeated inputs — can violate a game’s terms of service and can trigger anti-cheat attention, even though InputMapper itself is just a mapping tool. Rules differ by game and change over time, and a macro that is tolerated in a single-player title may be a bannable automation in a competitive one. The safe line is simple: use macros for shortcuts and accessibility — screenshots, push-to-talk, overlay toggles, single quality-of-life combinations in offline games — and do not use them to automate play against other people. If a game’s rules are unclear, do not test the boundary with an account you care about. When in doubt, play that title with a plain profile such as the baseline from how to use InputMapper, and keep macros for offline use.

When You Need More Than InputMapper Macros

InputMapper’s final build is from May 2020 and is no longer developed, so its macro editor is a capable but frozen toolset. If you need elaborate conditional logic, layered macros, or actively supported automation features, that is the territory of a paid commercial mapper. Our honest comparison, InputMapper vs reWASD, lays out what reWASD adds — and notes plainly that reWASD is a paid commercial product and we have no affiliate relationship with it. For most players, InputMapper’s macros plus per-game profiles are enough; power users should read the comparison and decide with their eyes open. The wider alternatives page covers the other current options, including the free Steam Input inside the Steam client.

Frequently Asked Questions

Where are InputMapper macros saved?

Macros are saved as part of the profile you build them in, and profiles live under %AppData%\DSDCS\InputMapper. Back up that folder and your macros are backed up with the rest of the profile.

Can macros get me banned in online games?

They can if they automate gameplay against other players. Rules vary by game and anti-cheat systems may flag automation. Use macros for shortcuts like screenshots and push-to-talk, and use a plain profile in competitive online games.

Why does my recorded macro drop some steps?

Usually timing. If steps replay with no gap, the game may not register each input. Add small pauses between steps, shorten the sequence, and test again in the actual game rather than only in menus.

Is there a better tool if I need advanced macros?

For elaborate conditional macros you would need a paid commercial mapper such as reWASD, which we compare honestly in our InputMapper vs reWASD guide. We have no affiliate relationship with reWASD. InputMapper macros still cover everyday shortcuts well.

Pairing Mode, Done Exactly

1. Charge the controller first. A nearly flat battery can enter pairing mode and then die mid-handshake, leaving a half-registered device behind.
2. Make sure the controller is fully off. If it is awake and connected to anything — a console, another PC, a phone — turn that device’s Bluetooth off or unplug the controller’s cable so it lets go.
3. Hold Share and PS together and keep holding. The lightbar must reach a rapid double-blink pattern. That double-blink is pairing mode. A single slow pulse means the controller is merely trying to reconnect to its last device — release, wait for it to go dark, and hold the buttons again.
4. On the PC, open Settings, Bluetooth & devices, Add device, Bluetooth, and select “Wireless Controller”.
5. Wait for the “ready” confirmation, then open InputMapper and confirm the controller is listed.

If Windows asks for a PIN, something has gone off-script — a DualShock 4 pairs without one, and a PIN prompt usually means you selected the wrong device from the list. Cancel and pair again, checking the device name carefully. Our quick version of this flow lives in connecting a PS4 controller to PC; this guide continues where that one stops.

Removing Stale Pairings

Bluetooth remembers. Every previous pairing leaves an entry in Windows, and the controller remembers its last host too. When those memories disagree — after a Windows reinstall, a new adapter, or months of use elsewhere — you get the classic symptoms: the controller appears but will not connect, connects and drops within a minute, or pairs happily to everything except your PC.

1. In Windows Bluetooth settings, find every “Wireless Controller” entry and choose Remove device. Duplicates are common and all of them should go.
2. Restart Bluetooth or the PC, so the radio starts from a clean list.
3. Put the controller into pairing mode again with the Share + PS hold, and pair fresh as above.
4. Test in InputMapper for a full minute of button presses before launching a game.

Ninety percent of “Bluetooth is broken” cases end at this step. Do it before you change drivers, buy hardware, or blame InputMapper. Persistent drops after a clean re-pair are a different problem, covered in Bluetooth lag and disconnects.

Re-Pairing After Switching Devices

A DualShock 4 happily pairs with a PlayStation, a phone, or a second PC — but it reconnects automatically to only one remembered host at a time, and switching back is not automatic. Expect this routine whenever the controller has been elsewhere:

• Returning to the PC after console use: the controller will try to wake the console. Pair it to the PC again from scratch — remove the Windows entry if the quick reconnect fails, then Share + PS pairing mode and Add device.
• Keep a micro-USB cable in the loop. Plugging in gives you instant wired play while you sort pairing out, and wired is also how you prove the controller itself is healthy.
• If two PCs are in the same room, turn Bluetooth off on the one you are not using. A discoverable controller in pairing mode will attach to whichever host grabs it first.

Players who switch constantly often dedicate one controller to the PC and leave its pairing untouched. It feels extravagant until the third evening spent re-pairing instead of playing.

USB 3.0 and 2.4 GHz Interference

Bluetooth lives in the 2.4 GHz band, and USB 3.0 ports and cables are a known source of noise in exactly that band. A Bluetooth dongle plugged directly into a USB 3.0 port, surrounded by external drives and their cables, can have a fraction of its expected range — fine on the desk, hopeless from the couch. Fixes, in order of effort:

• Move the dongle away from USB 3.0 hard drives and hubs. Even a short distance helps.
• Use a short USB extension cable to raise the dongle into clear air, away from the PC case and its tangle of cables. This is the single most effective cheap fix.
• Keep line of sight in mind. A dongle behind a metal case under a desk asks the signal to pass through both.
• Reduce crowding: other 2.4 GHz transmitters — wireless mice dongles, older Wi-Fi — all share the band. You cannot empty the band, but spacing transmitters apart reduces collisions.

Adapter quality matters too, and it is why we list two options below rather than one: a general Bluetooth dongle, and a UGREEN adapter as an alternative if your current radio is the weak link. Test interference fixes before replacing hardware, though — an extension cable has rescued more “bad” adapters than any purchase.

Bluetooth Power Management: Stop Windows Putting the Radio to Sleep

Windows can turn off Bluetooth hardware to save power, and on some systems it does so aggressively enough to drop a controller mid-session or after every sleep. To check:

1. Open Device Manager and find your Bluetooth adapter under the Bluetooth section.
2. Open its properties and look for a Power Management tab.
3. If “Allow the computer to turn off this device to save power” is checked, uncheck it and apply.
4. Also check any generic Bluetooth radio or USB root hub entries the adapter hangs off, if your disconnects happen right after the PC wakes.

Not every adapter exposes the tab. If yours does not, the equivalent behavior is sometimes controlled by the PC’s power plan — using a high-performance plan while gaming achieves the same end. If drops continue with power management off and pairings clean, work through Bluetooth lag and disconnects and the wider troubleshooting hub.

Wired Is the Fallback Test — Always

Every Bluetooth diagnosis should include one wired session. Connect the controller with a micro-USB data cable — not a charge-only cable, as warned in the connection guide — and play normally for ten minutes. If wired is flawless, the controller, InputMapper, your profile, and ViGEmBus are all proven good, and the problem is confined to the radio path: pairing, interference, adapter, or power management. If wired shows the same fault, stop debugging Bluetooth entirely and look at the software chain instead. This one test, done early, is what separates a ten-minute fix from an evening of guessing.

Better Bluetooth Hardware

If testing shows your adapter is genuinely the weak link, these are the two options we link for this site.

Bluetooth Dongle on Amazon UGREEN Bluetooth Options

Affiliate link — see our Affiliate Disclosure.

Frequently Asked Questions

Why does my controller show a slow pulse instead of double-blinking?

A slow pulse means the controller is trying to reconnect to its last paired device, not offering itself for a new pairing. Let it go dark, then hold Share and PS again until the lightbar double-blinks rapidly, which is true pairing mode.

Why does my DualShock 4 connect and then drop after a minute?

The most common causes are a stale pairing, Bluetooth power management turning the adapter off, or USB 3.0 interference weakening the signal. Remove the pairing and re-pair cleanly first, then check power management and dongle placement.

Do I have to re-pair after using the controller on my console?

Usually yes. The controller reconnects automatically to one remembered host, and after console use that host is the console. Remove any failed Windows entry if needed, then pair again using Share and PS pairing mode.

How do I prove the problem is Bluetooth and not InputMapper?

Play wired with a micro-USB data cable for ten minutes. If wired play is flawless, the controller, InputMapper, and your profile are proven good, and the fault is in the pairing, interference, adapter, or power management.

What InputMapper Can and Cannot Do

According to the official input list, InputMapper accepts the DualShock 4, the DS4 V2, the Xbox 360 controller, the Xbox One controller, the DualShock 3 only via a Mayflash Magic-NS dongle, the PS Move Navigation controller via Magic-NS, and generic DirectInput and generic XInput devices. On the output side it can create a virtual Xbox 360 controller, a virtual DS4, or keyboard and mouse output — all through the ViGEmBus driver.

Two popular controllers are not on that list: the DualSense and the Nintendo Switch Pro Controller. The final build predates the DualSense launch in November 2020, so InputMapper never added support for it. If you own one of those controllers, read our guides to DualSense on PC and the Switch Pro Controller on PC instead of forcing them through InputMapper.

Requirements Before You Start

• A PC running Windows — InputMapper runs on Windows 10 and 11 in practice. Note that Windows 11 was never officially supported, because the final build predates it.
• .NET Framework 4.x installed. Windows normally includes a 4.x version, so do not hunt for a specific minor version.
• A supported controller, ideally a DualShock 4 or DS4 V2 for this guide.
• A micro-USB data cable for a wired first connection, or a Bluetooth adapter for wireless play.
• Administrator access, because driver installation requires it.

Download the installer only from a page you trust. Our download page links to the archived installer and to a clearly labeled mirror. Check the file size and hash above before you run anything, and never treat any mapper as automatically trustworthy — version 1.6.10 of InputMapper even has a recorded buffer-overflow vulnerability, CVE-2019-25464, which is one more reason to use the final build rather than an old copy found on a random forum.

Step 1: Install ViGEmBus First

InputMapper 1.7 does not create its virtual controllers by itself. It outputs through ViGEmBus, an independent open-source project by nefarius under the BSD-3 license. Installing ViGEmBus first avoids the most common first-run error, where InputMapper opens but cannot create a virtual device.

The final ViGEmBus release is 1.22.0, released on November 2, 2023, after which the repository was archived. Download it from its GitHub releases page, run the installer, accept the driver prompt, and restart the PC if Windows asks you to. Do not download ViGEmBus from vigem.org — that domain has changed hands and must not be used. Our ViGEmBus install guide covers each prompt in detail, and the virtual bus not found fix helps if you skipped this step.

Get ViGEmBus from GitHub

Step 2: Install InputMapper

1. Run the InputMapper installer for build 1.7.7452.13622.
2. Accept the license terms and keep the default install location unless you have a reason to change it.
3. Let the installer finish, then launch InputMapper from the Start menu.
4. If Windows shows a SmartScreen prompt for an unrecognized app, verify the file name, size, and hash first. Only continue if they match what you expected to download.

On first launch, InputMapper looks plain: a device area at the top, a profiles area, and settings. Do not change advanced options yet. The goal of a first setup is a single working virtual Xbox 360 controller that a game can see. Extras such as macros and touchpad mapping come later, once the basic chain is proven.

Download InputMapper

Step 3: Connect Your DualShock 4

For a first connection, use a wire. Plug a micro-USB data cable into the DualShock 4 and into a USB port on the PC. Windows should detect the controller, and InputMapper should list it as a connected device shortly afterwards. A wired first test removes Bluetooth pairing, battery level, and wireless interference from the equation, so if something fails you know the problem is in the software chain, not the radio link.

Once wired mode works, you can pair over Bluetooth by holding Share and PS on the controller until the lightbar double-blinks, then adding “Wireless Controller” in Windows Bluetooth settings. Our dedicated guides to connecting a PS4 controller to PC and InputMapper Bluetooth pairing walk through both methods step by step.

Step 4: Create a Profile With Xbox 360 Output

1. In InputMapper, create a new profile and give it a clear name, such as “Xbox 360 Default”.
2. Set the output device to the virtual Xbox 360 controller. This is the output most PC games understand natively, because most were built around XInput.
3. Leave the standard button mapping in place for now. Face buttons, triggers, sticks, and the D-pad should mirror the layout printed on an Xbox controller.
4. Save the profile, then bind it to your connected DualShock 4 so the controller actually uses it.

Profiles are where InputMapper becomes useful beyond a simple adapter: each profile can hold different mappings, stick settings, and macros, and you can keep one profile per game. Our InputMapper profiles guide explains naming, binding, and per-game setups in depth, and it is worth reading before you build a large library.

Step 5: Test the Virtual Controller

With the profile active, open the Windows game controller panel by searching for “Set up USB game controllers” in the Start menu. You should see the virtual Xbox 360 controller listed. Open its properties and press buttons on the DualShock 4: the on-screen indicators should respond. If the real controller and the virtual controller both appear, that is expected — the real one is the input, the virtual one is what games should use.

Then launch a game with native Xbox controller support and test movement, camera, and menus. If inputs double up or the game sees two controllers at once, you are running into the classic double-input problem, which is about hiding the real controller, not about your mapping. Start with the double input fix rather than remapping buttons at random.

A Note on Exclusive Mode and Hiding the Real Controller

Older versions of InputMapper relied on exclusive mode and on HidGuardian plus HidCerberus to hide the physical DualShock 4 from games. That stack is legacy software from 2016 to 2018. The modern successor for hiding a controller is HidHide, currently at version 1.5.230 from May 11, 2024, for Windows 10 and 11 x64, available from GitHub releases. You do not need it for a first test — only add a hiding tool if a specific game actually shows double input. If InputMapper reports that it cannot take exclusive access, see exclusive mode failed for the order in which to close competing apps and services.

If you run into other problems, the troubleshooting hub and the Windows 11 notes collect the fixes that apply to this final, unmaintained build.

Connection Kit

A reliable wired cable and a decent Bluetooth adapter remove most first-setup headaches. A charge-only cable will never carry data, and a weak adapter drops connections mid-game, so these two small items are worth getting right.

Bluetooth Dongle on Amazon Micro-USB Data Cable on Amazon

Affiliate link — see our Affiliate Disclosure.

Frequently Asked Questions

Do I need to install ViGEmBus before InputMapper?

Yes, install ViGEmBus first. InputMapper 1.7 creates its virtual Xbox 360 and virtual DS4 outputs through ViGEmBus, so without that driver installed first, InputMapper can open but cannot create a working virtual controller.

Does InputMapper work with the DualSense controller?

No. The DualSense is not in InputMapper’s official input list, and the final build from May 2020 predates the DualSense launch in November 2020. Use a current tool for DualSense instead.

Why does my game see two controllers at once?

The game is seeing both your real DualShock 4 and the virtual Xbox 360 controller that InputMapper creates. That is the double-input problem, and it is fixed by hiding the real controller, for example with HidHide, not by changing your button mapping.

Is InputMapper officially supported on Windows 11?

No. InputMapper runs on Windows 10 and 11 in practice, but Windows 11 was never officially supported because the final build predates Windows 11. Expect occasional quirks and use the troubleshooting guides when they appear.

Before You Tune: Work on a Copy

All three setting groups live inside a profile. Duplicate your known-good baseline profile, name the copy for its purpose — “Evening – Dim Lightbar” or “Shooter – Small Dead Zone” — and tune the copy. If an experiment feels wrong, your baseline is untouched and you can switch back instantly. Test each change in the same place: a quiet area of a familiar game, with the camera free, so differences come from the setting and not from the game throwing explosions at you. Change one group at a time. Players who change lightbar, rumble, and dead zones together and then feel “something is off” have no way to know which change caused it.

Lightbar Settings: Color and Brightness

The lightbar on the back of the DualShock 4 and DS4 V2 faces away from you in play, but its glow still matters: it reflects off screens and walls in a dark room, it is what other people in the room see, and on the DS4 V2 a thin strip is also visible on the touchpad from above. Through a profile you can treat the lightbar as a simple indicator rather than a lamp:

• Pick a color per profile. A different lightbar color per profile is a genuinely useful signal: glance down and you know whether the desktop profile, the racing profile, or the shooter profile is active before you press anything.
• Lower the brightness for evening play. A dimmer bar is easier on the eyes in a dark room and kinder to the battery, as explained below.
• Use color as a player marker. With two controllers in local multiplayer, distinct colors make it obvious whose controller is whose — and each device can carry its own profile, as the profiles guide explains.

Keep expectations grounded: the lightbar is a small set of LEDs with simple controls, not a display. Color and brightness choices are cosmetic and practical, and no setting here affects how games read your input.

Rumble Settings: Intensity With Restraint

Rumble sells impact — collisions, explosions, rough ground — but at full strength for a whole session it numbs your hands and drains the battery faster. The setting to look for in a profile is rumble intensity: a scaling of how strongly the motors respond to what the game asks for.

• Start in the middle. Play a familiar sequence, then nudge intensity up or down in small steps. The right level is where you feel events clearly without the controller buzzing in your grip between them.
• Turn rumble down, or off, for menu-heavy, strategy, and desktop-style sessions. There is little information in it there, and the battery saving is real.
• Keep one stronger-rumble profile for games where rumble carries gameplay information, such as off-road racing or horror titles, instead of forcing one compromise on everything.

If rumble feels inconsistent — strong in one game, absent in another — that is usually the game, not your setting. Games send rumble requests to the virtual Xbox 360 controller that InputMapper creates through ViGEmBus, and titles vary widely in how much they send. Test rumble judgments in the same game before changing the profile, just as with the basic setup checks in how to use InputMapper.

Dead Zones: The Setting That Fixes Drift

A dead zone is the small area around a stick’s resting position that the software ignores. It exists because analog sticks rarely report a perfect center, especially as they age: without a dead zone, a resting stick can send a faint constant tilt, and the camera creeps or a character walks slowly on its own.

Finding Your Dead Zone

1. In a game, load a quiet scene and take your thumbs completely off the sticks. Watch for camera movement or a drifting cursor for ten seconds.
2. If anything moves, raise the dead zone a small step in your profile and test again.
3. Stop as soon as the drift disappears. Then wiggle the stick gently and confirm small movements still register smoothly.

The goal is the smallest dead zone that hides your stick’s resting error. Too large a dead zone eats the beginning of every movement: aiming feels vague, gentle steering disappears, and players often describe the controller as “heavy” or “laggy” when the real problem is an oversized dead zone. Racers usually tolerate — and benefit from — a slightly larger zone than shooters, which is exactly why dead zones belong in per-game profiles rather than one global choice. If drift appears in only one direction or grows worse week by week, the stick itself may be wearing; no setting fully repairs failing hardware, and our troubleshooting hub helps separate a settings problem from a hardware one. The touchpad equivalent of this tuning — accidental input and drift — is discussed in DS4 touchpad as mouse.

The Battery Note Everyone Learns the Hard Way

Lightbar brightness and rumble are the two biggest discretionary drains on a DualShock 4 battery over Bluetooth. A bright lightbar plus strong, constant rumble shortens a wireless session noticeably compared with a dim bar and moderate rumble. Practical habits:

• Run an “evening” profile with a dimmer lightbar and moderate rumble as your wireless default.
• When the battery warning arrives mid-game, plug in the micro-USB cable and keep playing wired, as in connecting a PS4 controller to PC — wired play removes the battery from the equation entirely.
• Charge between sessions instead of deep-cycling the battery every night.

A simple drop-in charging dock makes that last habit automatic, since the controller lives on the dock instead of in a drawer with a dead battery.

DualShock 4 Charging Dock on Amazon

Affiliate link — see our Affiliate Disclosure.

Frequently Asked Questions

Can I set a different lightbar color for each profile?

Yes, lightbar choices live in the profile, so each profile can use its own color and brightness. Many players use this as a quick visual check for which profile is active before starting a game.

Why does my camera move when I am not touching the sticks?

Your stick is reporting a small input at rest and the dead zone is too small to ignore it. Raise the dead zone in small steps until the drift stops, but no further, or aiming and gentle steering will start to feel vague.

Does turning down the lightbar and rumble save battery?

Yes. Lightbar brightness and rumble are two of the biggest discretionary drains on a DualShock 4 over Bluetooth. A dimmer lightbar and moderate rumble noticeably extend a wireless session, and wired play removes the battery concern entirely.

Why is rumble strong in one game and weak in another?

Games send different amounts of rumble to the controller, and your profile only scales what the game requests. Judge and adjust rumble intensity within the same game before changing profiles.

Why the Touchpad Works as a Mouse

InputMapper’s outputs are not limited to controllers. Alongside a virtual Xbox 360 controller and a virtual DS4 — both created through ViGEmBus — it can output keyboard and mouse input. The touchpad is a natural fit for that output: it is a small trackpad sitting in the middle of the controller, reporting finger position and taps. InputMapper translates that finger movement into cursor movement, which Windows treats like any other mouse. Nothing about this requires the game itself to support touchpads; the cursor control happens at the Windows level, before the game is even involved.

That distinction explains the two places touchpad mouse control shines. On the Windows desktop and in launchers, it is a genuine mouse replacement. Inside a game, it depends on the game: a strategy title with a real cursor loves it, while a shooter that locks the pointer for camera control will not use a mouse cursor at all — there, the right stick should stay in charge.

Set Up a Touchpad Mouse Profile

1. Start from a working baseline profile. If you have not built one yet, follow how to use InputMapper first, then InputMapper profiles for how profiles and binding work.
2. Duplicate the baseline and name the copy clearly, for example “Desktop – Touchpad Mouse”. Never experiment on your only working profile.
3. In the copied profile, set the touchpad to mouse-style output, so finger movement drives the cursor.
4. Bind the profile to your DualShock 4 and return to the Windows desktop.
5. Move one finger slowly across the pad. The cursor should follow. Tap the pad and confirm a click registers where the cursor sits.

Keep this as a dedicated desktop profile rather than your all-purpose game profile. Switching to “Desktop” to browse and launch, then switching to a game profile with the touchpad left alone, avoids almost every annoyance described later in this guide.

Tune Movement, Tap, and Swipe Settings

Cursor Speed and Feel

The pad is small, so cursor travel is a compromise. Too slow and you swipe repeatedly to cross the screen; too fast and you overshoot every button. Set speed so one comfortable swipe crosses most of the screen, then fine-tune after a day of real use rather than chasing perfection in the settings window. If your Windows mouse settings are already tuned for a fast desktop mouse, expect the touchpad to feel different — judge it on its own, with the controller in your hands at couch distance.

Taps and Clicks

Decide how you want to click, and be consistent:

• Tap to click: a light tap on the pad clicks. Fast, but easy to trigger accidentally while moving the cursor.
• Pad press: the touchpad is also a physical button you can press down. Slower, but deliberate — many couch users prefer this for important clicks.
• Mapped buttons: in a desktop profile you can also put mouse buttons on controller buttons you trust more, keeping the pad purely for movement.

Whichever you choose, test it on the desktop first: open a folder, right-click an empty area if you have a right-click method mapped, and close the window again. If you can do that calmly three times in a row, the setup is usable.

Swipes and Scrolling

Swipe behavior is what makes long pages, store listings, and settings screens bearable from the couch. Set scrolling so a deliberate swipe moves a readable amount — a small scroll per swipe forces constant swiping, while a huge scroll makes precise reading impossible. Test in a browser window or a long settings page, and adjust until one swipe feels like turning a page rather than throwing it. Diagonal drift is normal on a small pad; aim for the center of the pad and swipe straight, and the cursor and scroll will behave.

Using the Touchpad in Games

Split your expectations by game type:

• Cursor-driven games — strategy, management, point-and-click, and many emulator front ends — can genuinely be played with the touchpad, especially with a per-game profile that slows the cursor a little for precision.
• Camera-driven games — shooters and third-person action — capture the mouse for looking around, so touchpad mouse output has nowhere useful to go. Use a normal game profile there and leave the touchpad for its in-game button role, if the game uses one.
• Menus and launchers around any game still benefit, which is why the desktop profile earns its place even for action-game players.

If a game shows both controller prompts and a wandering cursor, it may be seeing the real controller and the virtual output together. That is the double-input problem, not a touchpad fault — see the double input fix. And if Steam games behave differently from other games, check for a conflict with Steam Input in InputMapper and Steam Input conflicts, since Steam can apply its own touchpad behavior on top.

Related Settings Worth Tuning Together

Touchpad feel does not live alone. While you are in profile settings, the lightbar, rumble, and dead zone options shape how the same controller feels in the hand. A dimmer lightbar makes evening desktop sessions easier on the eyes, and a sensible dead zone stops camera drift that players often blame on the touchpad. Our companion guide, DualShock 4 lightbar and rumble settings, walks through those options together, and it is the natural next step after this one. Similarly, a couple of macros — a screenshot shortcut, an Alt-Tab style launcher shortcut — turn the desktop profile into a complete couch control setup.

Finally, save and back up the profile once it feels right. Touchpad tuning is fiddly, personal work; losing it in a reinstall is disproportionately annoying. The backup routine in back up InputMapper profiles protects the profile folder under %AppData%\DSDCS\InputMapper in a few minutes.

Frequently Asked Questions

Can I use the DS4 touchpad as a mouse on the Windows desktop?

Yes. In an InputMapper profile, the DualShock 4 touchpad can output mouse movement, taps, and swipes, so you can move the Windows cursor, click, and scroll from the controller without a separate mouse.

Why does the touchpad not move the camera in my shooter?

Shooters capture the mouse for camera control, so there is no free cursor for touchpad mouse output to move. Use a normal game profile with the right stick for the camera, and keep the touchpad profile for the desktop and cursor-driven games.

Should the touchpad mouse be in my main game profile?

Usually not. Keep a dedicated desktop profile for touchpad mouse control and separate game profiles for play. Switching profiles avoids accidental clicks during games and lets you tune cursor speed without affecting gameplay.

Why does my cursor drift or click by itself?

Accidental palm or thumb contact with the pad is the usual cause, followed by tap-to-click being too easy to trigger. Rest your thumbs off the pad, consider using the physical pad press for clicks, and check stick dead zones if the drift is actually from an analog stick.