DualSense (Edge) target does not work in hidraw in Proton

[xzn]

Maybe I'm missing something obvious here:

Emulated virtual DualSense (Edge) shows up in KDE game controller system settings as a bluetooth device (with the hidraw path) and gets input preview correctly. Input preview also shows correctly in Steam (in controller settings). The emulated DS5 shows up correctly in Wine's control panel game controller setting page as well.

However if I try to run a game that has native DualSense support in proton, the controller does not function at all.

Case Final Fantasy VII Remake/Rebirth, there's also a weird couple-of-seconds pause whenever I click the mouse inside game window while the DualSense target is active.

For Stellar Blade, I get something like

[2025-11-26T08:20:30Z WARN  inputplumber::input::manager] Unable to create initialized UdevDevice for /dev/input/event27 after 80 attempts.
[2025-11-26T08:20:34Z WARN  inputplumber::input::manager] Unable to create initialized UdevDevice for /dev/input/js4 after 80 attempts.
[2025-11-26T08:20:39Z WARN  inputplumber::input::manager] Unable to create initialized UdevDevice for /dev/input/event27 after 80 attempts.
[2025-11-26T08:20:43Z WARN  inputplumber::input::manager] Unable to create initialized UdevDevice for /dev/input/js4 after 80 attempts.

when launching the game.

Tried multiple PCs with different input mapped to ds5, HHD works fine for the most part in comparison, don't know what the problem is.

---

Edit:

Ok HHD emulates a bluetooth ds5 by default. InputPlumber emulates a USB one and I guess the emulation isn't quite complete..

[ShadowApex]

Emulation of the USB version of the DS5 should be complete, but yes we currently do not yet support emulating the bluetooth version of the DS5 controller. Games may only support one version of the controller.

Once the following changes are merged, you should be able to emulate a DS5 bluetooth controller with InputPlumber:
#381

[xzn]

Just to clarify, for both HHD and InputPlumber, if the DS5 is emulated in USB mode, games running under Proton won't work. What I meant by "incomplete" is that (just a guess from my part) the emulated USB DS5 doesn't actually have a USB device/hub whatever associated. I could be 100% wrong about what's actually causing the issue.

Thanks for the great work so far!

Edit:

Maybe it's a bug in wine? Lots of lines that look like this:

00b4:err:sync:RtlpWaitForCriticalSection section 0000000000C48138 "../src-wine/dlls/winebus.sys/main.c: cs" wait timed out in thread 00b4, blocked by 00a0, retrying (60 sec)
00a0:err:hid:hidraw_device_set_feature_report id 8 write failed, error: 5 Input/output error

[xzn]

Found this page (not sure where they got their info from but the page is CC-BY-SA) https://controllers.fandom.com/wiki/Sony_DualSense#Bluetooth_Control

Anyhow implementing that would fix FFVII Rebirth when inputplumber is active with ds5 usb mode emulation. (Tested by masking out certain code path in wine.)

I can look into inputplumber's code base later.

Happy new year!

Edit:

To be precise, when encountering unhandled/unimplemented report, instead of failing, return success anyway and maybe print a warning to log. That would fix this issue.

Edit 2:

DualSenseDevice isn't calling write_set_report_reply which leads to kernel time out on the request. Since we don't care what report we receive on the emulated device (mostly anyway), we can always call write_set_report_reply to avoid time out.

[github-actions]

🎉 This issue has been resolved in version 0.70.2 🎉

The release is available on:

• v0.70.2
• GitHub release

Your semantic-release bot 📦🚀