How to Map PS5 Controller for Apex Legends via DS5Windows

In Apex Legends, every movement counts, rapid armor swaps, tap-strafing, tracking targets at high FOV. The DualSense controller has excellent build quality and comfortable thumbsticks, but running it natively on PC can introduce subtle input lag, limited deadzone customization, or triggers that feel less responsive than you’d like.

Configuring your DualSense through DS5Windows (DSX) gives you custom response curves, hair-trigger sensitivity, dedicated button macros, and gyro-assisted aim adjustment, more control than Apex’s built-in controller settings offer on their own.

Why Use DSX Instead of Steam Input

Steam Input natively supports PlayStation controllers, so it’s a reasonable starting point, but competitive players often prefer DSX for a few specific reasons:

  • Custom stick response curves: fine-tune curves directly rather than relying only on Apex’s Advanced Look Controls
  • Hair triggers: lower trigger activation thresholds so aim-down-sights and firing respond closer to the start of the pull
  • Macro mapping: bind touchpad presses or other buttons to keyboard shortcuts, inventory or map toggles, quick pings, without taking your thumb off the stick

Setting Up Your Profile

  1. Open DSX, go to the Profiles tab, and create a new profile named something like “Apex Legends.”
  2. Set the emulated controller based on how you’re playing:
    • Xbox 360 tends to be the safer, more plug-and-play option, especially for EA App users or anyone prioritizing wireless stability.
    • DualShock 4 is worth trying if you’re on Steam and want native PlayStation button icons on screen, along with touchpad gesture support.

Calibrating Stick Response

Apex asks a lot from your sticks, close-range tracking and fast slide-jumping both need quick, predictable response without feeling twitchy.

Left Stick (Movement)

Keep the deadzone small enough that movement feels immediate, but not so small that you get drift from an idle stick. A linear output curve tends to preserve consistent muscle memory better than a curved response, since what you input is closer to what you get.

Right Stick (Aiming)

A slightly larger deadzone than your left stick helps prevent unwanted camera drift while tracking targets, but push it too far and small recoil-control adjustments start feeling jumpy instead of smooth. If your controller has any stick drift, raising this deadzone a bit is usually a better fix than trying to compensate in Apex’s own settings, since DSX applies deadzone filtering before the game ever sees the input.

There’s no single correct number for either stick, controller condition and personal feel both matter here, so it’s worth spending a few minutes adjusting and testing in the firing range rather than copying exact values from a guide.

Setting Up Hair Triggers

In a fast gunfight, the time it takes to physically pull a trigger down can matter. Lowering the trigger’s activation threshold, so it registers a full press well before you’ve pulled it all the way, effectively turns your analog trigger into something closer to a fast digital click.

Steps

  1. Open the L2 and R2 tabs in your profile.
  2. Lower the deadzone toward zero.
  3. Lower the max threshold so a partial pull, roughly the first 5 to 10 percent of the trigger’s travel, registers as a full press.

Start conservative and tighten it further if it still feels slow, going too aggressive too fast can make triggers feel overly sensitive and cause accidental fires.

Mapping the Touchpad

The DualSense’s touchpad gives you extra input real estate that’s easy to underuse.

  1. In the Touchpad tab, set the output mode to act as button input rather than a mouse surface.
  2. Map the left side of the touchpad to something like your map or inventory key.
  3. Map the right side to something like weapon inspect or your ultimate ability key.

This lets you check your map or inventory without lifting your thumb off the movement stick, small, but it adds up over a match.

Preventing Double Input Issues

To avoid menu stutter or dropped inputs when Apex launches, hide your physical controller with HidHide so the game only reads DSX’s virtual one.

  1. Open the HidHide Configuration Client, available from its official GitHub release page if you haven’t installed it yet.
  2. Under Devices, find your DualSense and check the box to hide it.
  3. Under Applications, add DSX to the whitelist.
  4. Enable hiding and confirm the lock icon appears.

You’ll also need ViGEmBus installed for DSX’s emulation to work at all, our Drivers page covers setup for both if you’re doing this for the first time.

Recommended In-Game Settings

To avoid Apex’s own controller processing fighting with DSX, a few settings inside Apex are worth adjusting:

  • Set your interact/reload behavior to whatever feels most natural, tap to use, hold to reload is a common choice
  • Set look and movement deadzones to their smallest in-game values, since DSX is already handling deadzone filtering for you
  • Use a linear response curve in Apex’s settings to match a linear curve in DSX, this keeps aim translation direct rather than doubling up on curve smoothing from two different places

Troubleshooting Common Issues

In-game button prompts keep switching: This usually means Steam Input is running alongside DSX. Go to that game’s Properties in Steam, open the Controller tab, and set the override to Disable Steam Input.

Camera spins on its own: Often a sign your right stick deadzone is set too low for a controller with some wear. Raise it gradually in DSX until the drift stops.

Inputs feel delayed over Bluetooth: This is more often signal interference or distance than anything DSX can fix with a setting, a wired USB connection is the more reliable option if latency really matters for your setup. Note that DSX doesn’t include a manual polling rate override, despite what some older guides claim, it reads input as fast as your connection allows.

If none of this resolves things, check our Troubleshooting guide and FAQ page for broader DSX issues that might be the actual cause.

Leave a Comment