You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't a feature request or a discussion topic
Bug description
I was connected via Bluetooth but the battery was getting low, so I plugged it in. After doing so, it was not seen/recognized by Epic Games/Fortnite, but Steam still saw it, so I knew it was connected and "working." After some troubleshooting, I realized it was showing twice, once under wireless/BT and once wired, both with the same ID. I'm guessing Steam is somehow able to deal with the fact it was basically two devices simultaneously while Epic wasn't. DsHidMini (or maybe it's an issue with BthPS3) should remove it as a wired/wireless device when it connects as the other.
Steps to reproduce
Connect a DS3 controller wirelessly
Plug it in to connect it wired
See that it's showing twice, one wireless and one wired
Actual result: See above Expected result: See above
Screenshots
Machine info
CPU-Architecture: x64 Windows version: Windows 10 22H2 Software/driver version(s): 2.2.282
Any other helpful information
The text was updated successfully, but these errors were encountered:
Bug description
I was connected via Bluetooth but the battery was getting low, so I plugged it in. After doing so, it was not seen/recognized by Epic Games/Fortnite, but Steam still saw it, so I knew it was connected and "working." After some troubleshooting, I realized it was showing twice, once under wireless/BT and once wired, both with the same ID. I'm guessing Steam is somehow able to deal with the fact it was basically two devices simultaneously while Epic wasn't. DsHidMini (or maybe it's an issue with BthPS3) should remove it as a wired/wireless device when it connects as the other.
Steps to reproduce
Actual result: See above
Expected result: See above
Screenshots
Machine info
CPU-Architecture: x64
Windows version: Windows 10 22H2
Software/driver version(s): 2.2.282
Any other helpful information
The text was updated successfully, but these errors were encountered: