Thanks for the feedback, I’ll pay special attention to this issue this week. I’ll let you know when I have any updates.
1 Like
I believe I’ve resolved the issue, and the v1.2.16 update will be available soon.
I recommend using this approach to correctly capture touchpad data.
IMC
Note: the controller automatically generates IDs when touch down is true. Therefore, it is necessary to add all available Touch IDs in Unreal to the IMC
1 Like
Does this plugin have compatability with CommonUI/CommonInput? Trying to use it in UI / Menus and having a difficult time. Do you have any suggestions? Im all out of ideas.
Absolutely. If you’re having trouble with input mapping for UI navigation, the solution is quite simple. The plugin uses standard input key names for the left analog stick.
You just need to create Input Actions for UI navigation (e.g., UINavigateUp, UINavigateDown) and then map these specific keys to them in your project’s input settings or your CommonUI data table:
Gamepad_LeftStick_Up
Gamepad_LeftStick_Down
Gamepad_LeftStick_Left
Gamepad_LeftStick_Right
Once you map those keys to your actions, CommonUI will handle the widget navigation correctly.
just like in the tutorial’s example project. You can see the tutorial here for reference: https://github.com/rafaelvaloto/WindowsDualsenseUnreal/wiki/Example-Project:-Gyroscope-Aiming
Could you please give me an example of how this can be used? Seeing the difference between it was triggered by Pressed, Released, or Pulse to calculate what direction you swipe is eluding me! 
Sorry, I think I made a mistake there in the previous action image, it will actually depend on what you need… but you can leave the action without any value and just map it to the 2d axis like in this image.
So we still have a bug:
With the setup you provide, you’ll have repeated trigger which is fine, but if you’re trying to track the moment to touch and the moment to release, that is bad. So I put a print string to print the Action Values on “Started” and “Completed”, which works perfect but there is one bug. If you touch the touchpad from the VERY top (like on the top corner) and swipe down, sometimes the “Started” and “Complete” will bug out and repeat over and over when you’re still holding the touch.
I don’t know if that explains it well but TLDR:
Swiping down from the very top can glitch and infinitely repeat “Started” and “Completed”.
1 Like
Hi, sorry for the late reply. Did you use the configuration this way? I couldn’t reproduce this issue with the tests.
Yeah, same setup as that. And when I say “very top” I mean around the curve of the touchpad.
1 Like
Example Project: Audio-Based Vibration
This project demonstrates the Advanced Audio Vibration, a native feature of the DualSense controller. It serves as a simple playlist to showcase how music, footsteps, and other sound effects can be translated directly into high-fidelity haptics when the controller is connected via USB.
WindowsDualsenseUnreal/README.md at master · rafaelvaloto/WindowsDualsenseUnreal
Any plans for a video? I’m very noob and just don’t understand.
Hello, yes I intend to make updated videos as soon as I have some free time.
Other “bug”, if you use the touch screen while in a window mode, the touch screen can interact with stuff outside the application.
1 Like
Hi, yes I noticed that too, I’m thinking about how to work around it. I’ll implement a Swipe feature suggested by a plugin user and try to solve these problems at the same time.
1 Like
[RELEASE] DualSense Unreal Plugin: Stable Audio Haptics on Both Bluetooth & USB! (+ Sample Project)
Hey everyone!
I’m beyond excited to announce a massive new update for the DualSense Unreal Plugin. After a ton of development, and testing, we have finally cracked the code:
True, stable, high-performance Audio Haptics now work seamlessly over BOTH Bluetooth and USB connections.
This has been the most requested feature and the biggest technical hurdle, and it’s finally ready for your projects.
Key Features
-
Full Audio Haptics Support: Convert any in-game sound into immersive haptic feedback.
-
Dual Connection, Single Solution: Connect via USB or Bluetooth. The plugin automatically detects the connection type and uses the correct, native protocol.
Submix-Based Architecture: We leverage Unreal’s native audio engine. You don’t need to do any encoding. Just send your haptics audio track to a designated
Sound Submixusing aSubmix Send, and the plugin does the rest. -
Lightweight & Performant: Designed to be as efficient as possible