I just realized that it doesn’t happen if I also have an Xbox controller connected (or any other controller). Still something that could benefit from a fix, if possible!
Hi, thanks for getting back to me and helping to work on this. I’m using the version currently available from FAB. UE tells me it’s version 5.6.0. The input class name is listed as FWinDualShock, which may be because I am also running the Windows DualShock plugin from Epic. I never disabled it, should I do so? I suppose it’s possible they’re fighting with each other, however, the DualSense controller is working just fine except for CommonUI functionality.
EDIT: I just checked inside the editor and it lists the plugin as 1.2.19. Sorry about that, didn’t think to check the plugin listing inside the editor.
EDIT 2: I have created a controller data blueprint and entered the input settings there. I have attempted to modify the Gamepad Hardware Id Mapping with the info you provided, but that didn’t help at all. Are you suggesting that I add the data you provided directly to DefaultGame.ini?
EDIT 3: After doing some reading I disabled the Epic plugin, and added your suggested lines to the DefaultInput.ini. I then started the game back up and edited my PS5 controller data to match the new controller info, but it still displays the Xbox icons when I use the DualSense controller.
I added this code to DefaultInput.ini and it fixed my problem, yeah!
Thanks for the report. Actually, your problem can be easily solved if you apply the delegate, and in the input settings, you need to configure the following.
However, we still have an issue that was reported in this GitHub issue. For this to work correctly, we will need to make some changes to the method that reads the input from the controls in the plugin.
Yes, this problem does exist over USB, I will investigate the reason so that the correction can be made. Thank you.
I’ve updated to the new version where I log the input modification event in this delegate. You can test it as soon as the FAB releases the update. v1.2.20. I believe that should solve the problem.
Thanks for the info. I’ll keep an eye out for the update and then give it another test and report back.
**If you can comment on the open issue, I’d appreciate it. More developers are contributing, and that helps them understand the problem.
**
DualSense establishes itself as the current input device constantly (OnInputHardwareDeviceChanged) · Issue #87 · rafaelvaloto/WindowsDualsenseUnreal
I have tested and am at this point at a complete loss. The Input Device Subsystem is returning the correct information for the DualSense controller, the controller works perfectly fine, and I have my PlayStation 5 controller data set up with the mapping that is being returned from the Input Subsystem and still it is using the Xbox images not the PlayStation images I have set up in the Data set.
Any further help would be appreciated.
Thanks.
Hi, if it’s convenient for you, clone the repository from the master branch. It seems the problem has been fixed. The version currently in the FAB is outdated. Unless you want to wait for a new, updated version to be released.
I may give that a try. I also intend to check into our implementation to see if we missed anything. Just an FYI in case it makes a difference, the version in the project from FAB is 1.2.20 which is also the latest version on GitHUB. It just updated a couple of days ago and I am still experiencing the Xbox icon issue.
After I do a little checking I’ll pull the zip package from GitHUB and load it over the FAB version and let you know if that changes anything. I’ll also post back here with any fixes we find in our configuration so that others can find the info in case they need it. I’ll let you know what I find out either way.
Thanks again. I’ll post back soon.
You plug it in and it just works: Thank you!
Hi, one important detail: the version in the .zip file on GitHub is the same as the one on the FAB Marketplace. To make it work, you must clone the repository from the master branch; this branch contains the fix you probably need.

