v2.1

Troubleshooting

Fixes for the most common problems with the DualSense plugin.

The controller is not detected

  • Look in the Output Log for LogDualSense: DualSense #0 connected. If it is not there, the plugin did not find the controller.
  • Check that the plugin is enabled in Edit → Plugins and that you are on Windows.
  • Over Bluetooth, pair the controller in the Windows settings first. If it is paired but not seen, unpair it and pair it again, or try a USB cable.
  • Close tools that take exclusive control of the controller (see below), then reconnect it: the plugin looks for new controllers every 2 seconds.

Every button fires twice

The RawInput plugin is still reading the controller. Remove the DualSense DeviceConfigurations from [/Script/RawInput.RawInputSettings] in Config/DefaultInput.ini and disable the Raw Input plugin. See Installation.

The same happens with Steam Input: when Steam runs your game with Steam Input enabled for PlayStation controllers, it adds a virtual Xbox pad. Disable Steam Input for the game, or ignore the XInput device.

Nothing happens on the controller

  • Did you call DS Update Output? The DS Set ... nodes alone only change the stored state.
  • Is the Controller Id right? The first controller is 0.
  • DS Is Controller Connected returns false? See the first section.
  • A Force Feedback Effect with Device Properties is active? It wins over the DS nodes until it ends. See Force Feedback Effects.

A trigger effect feels wrong or too weak

  • Check the ranges: Weapon needs Start 2–7 and End after Start; strengths are 1–8. Values out of range are clamped, which can change the feel.
  • A Strength or Amplitude of 0 turns the effect off.
  • Some effects only work in part of the travel: a Feedback at Position 8 starts almost at the end.
  • Try the same effect in the demo to tell your settings apart from the hardware.

DS4Windows, DSX and similar tools

These tools can hide the DualSense behind a virtual Xbox controller, or keep sending their own trigger effects. Close them (or exclude your game) while you test. The plugin itself doesn't need any of them, and neither do your players.

Packaging fails or the game does not find the plugin

  • The plugin only builds for Win64. Packaging for another platform with the plugin enabled will skip it.
  • Check that you installed the package that matches your engine version (UE57 or UE58).

Still stuck?

Ask on Discord with the plugin version, engine version, connection type and the LogDualSense lines from the Output Log.

© 2026 Developed by Altercode. Blueprint graphs rendered with ueblueprint (MIT).

Unofficial plugin, not affiliated with, endorsed by or sponsored by Sony Interactive Entertainment Inc. "DualSense", "DualSense Edge" and "PlayStation" are registered trademarks or trademarks of Sony Interactive Entertainment Inc. "Unreal" and "Unreal Engine" are trademarks or registered trademarks of Epic Games, Inc.