BthPS3 Code 31 about bthps3

[nefarius]

it boils down to broken or weird Windows installations

Maybe cuz of the Lite OS?

IDK what that is supposed to be, Windows 11 is a shameless Beta product anyway. If you further manipulate it I doubt things get any better.

[nefarius]

Give me a couple of days and I can make a release with more logging added to the filter driver, maybe then we get closer to the culprit.

[nefarius]

Had no time yet unfortunately 😕

[nefarius]

This error means the filter driver BthPS3PSM wasn't loaded, which is mandatory for BthPS3 to work.

I can't tell you why, it boils down to broken or weird Windows installations, I can't reproduce it, and I can't offer a fix besides what's already documented.

[nefarius]

Potentially related to #64

[ShadowElixir]

it boils down to broken or weird Windows installations

Maybe cuz of the Lite OS?

[ShadowElixir]

Give me a couple of days and I can make a release with more logging added to the filter driver, maybe then we get closer to the culprit.

Any updates?

[ShadowElixir]

This is also happening on debloated Windows 10

[yanuarmdhn]

#25 (reply in thread)

I updated VigemBus and BthPS3 to the latest version, my 4.0 dongle kept working normally and my 5.1 dongle now gives me code 10. When I remove the filter, I can at least use the 5.1 dongle with other things, but the "Nefarius Bluetooth PS Enumerator" shows the code 31 =/.

Dongle 5.1

Apparently the only solution is to use another dongle. So, I don't recommend you to buy the Baseus Bluetooth Dongle ba04 5.1 if you want to use BthPS3. (Although I vaguely remember seeing in some video someone using version 5.0 of this dongle working normally.)

Anyway, thanks for the help!

Dongle 4.0

I think this is the problem. Driver BthPS3 Bluetooth Drivers v2.6.174 doesn't support Bluetooth dongle 5.0. I tried to install Bluetooth dongle 5.0, My OS Windows 10 Latest Update, Dshidmini latest. i already follow all installation and troubleshooting instructions, the results always failed. Maybe the devs will fixed on the next update.

[tiag0d]

#25 (reply in thread)

I updated VigemBus and BthPS3 to the latest version, my 4.0 dongle kept working normally and my 5.1 dongle now gives me code 10. When I remove the filter, I can at least use the 5.1 dongle with other things, but the "Nefarius Bluetooth PS Enumerator" shows the code 31 =/.
Dongle 5.1
Apparently the only solution is to use another dongle. So, I don't recommend you to buy the Baseus Bluetooth Dongle ba04 5.1 if you want to use BthPS3. (Although I vaguely remember seeing in some video someone using version 5.0 of this dongle working normally.)
Anyway, thanks for the help!
Dongle 4.0

I think this is the problem. Driver BthPS3 Bluetooth Drivers v2.6.174 doesn't support Bluetooth dongle 5.0. I tried to install Bluetooth dongle 5.0, My OS Windows 10 Latest Update, Dshidmini latest. i already follow all installation and troubleshooting instructions, the results always failed. Maybe the devs will fixed on the next update.

I'm having the exact same issue with a bluetooth 5.0 dongle. If this is an issue with the program I hope to see it fixed when possible.

[Wiiplay123]

This happened to me with all of my USB bluetooth devices including my HTC Vive bluetooth after installing BthPS3, I uninstalled and it kept happening. I reinstalled and it continued happening, but the HTC Vive bluetooth started working again after reinstalling its drivers.
I found out that BthPS3 was actually working with my motherboard's integrated bluetooth so I didn't need that extra USB bluetooth dongle anyway. I have a .etl file if you need it.

I'm on Windows 10 Home Version 21H2, upgraded from Windows 7.

I originally had the extra USB bluetooth dongle for SCPToolkit.

[nefarius]

#82 might be related.

[nefarius]

New pre-release is out, please test!

[nefarius]

Tested with a wide range of Windows 10 and 11 versions, I consider this fixed.

[DeadKiller25]

Still getting Code 10 on BthPS3 install (both recent versions), and Code 31 on the Nefarius Bluetooth PS Enumerator after running the PowerShell command. I'm running Windows 10 Home - 22H2.

My dongle is a Generic Bluetooth Adapter, it has a v5.0 printed on it, and the HCI and LMP are v10.137. I've tried both SCPToolkit and DshidMini/BthPS3 and never got it to work wirelessly, I think this adapter's simply not gonna do the job :/

Edit: Alright. It's been a while and if I didn't live in such a remote area I would have already bought another dongle. I can only buy from online stores and receive through shipping and obviosly shipping alone is more expensive than dongles themself, and even so there's only generic dongles on sale, save for one TPLink adapter kinda overpriced. So, randomly one day in september my generic dongle received a driver update (?) and now it doesn't get recognized as generic, but a BARROT Bluetooth Adapter. However, nothing changed, still the same thing happens, should I just give up?

[nefarius]

Welp.

[celsosa]

I have same problem. I'm using Baseus bluetooth adapter 5.1

[DeadKiller25]

I have same problem. I'm using Baseus bluetooth adapter 5.1

You know... I had a old netbook gathering dust and I remembered it had a good bluetooth adapter. Well, I ended up using it's adapter over LAN using this software. It allows to share over network any USB device, and from my tests, WiFi offers a somewhat crappy experience, though LAN seems just fine :)