PS(R) Ga`epad working via BT?

First: yes, I'm aware the project is specifically not geared towards fake copies but since this one worked on SCPToolkit and seems very popular I'm wondering if anyone has this controller and can make it work via BT?

The issue I get is that it seems it doesn't connect, I click the 'ps3' button and it just flashes but never seems to 'connect' via BT.

On DsHidMini Host address is 00:00:00:00:00:00 but it says pairing was OK. My bluetooth pen seems to be, it's an "Hama Nano Bluetooth USB Adapter".

Anyone with this controller is able to make it work via BT? anything else I can provide to add support for it?

See here and here and here and here and here.

TL;DR: it's impossible to to address your issue with the little information you provided, please check the links.

I repeat myself: If it works, great. If it doesn't, leave a one star review wherever you got the controller from and nag the manufacturer, thanks 😇

Cheers

@nefarius Thanks, as I said, I'm fully aware this is not your goal and thank you very much for your time.

What I want is to provide as much information as possible. Is there a guide to provide any kind of debbuging log to you?

I have read through all of that and my controller doesn't seem to have the bluetooth encryption problem. I'm only insisting because with old SCPToolkit my controller BT actually works. Isn't that a sign that it probably can also work with bthPS3?

It's even in the regedit "SIXAXISSupportedNames" so that's why I'm insisting, because it seems that it's a popular fake controller that is supposed to work. Is there any BT tool I can start to see why it isn't pairing?

thanks again.

Trace file: https://easyupload.io/7851kx

e25758f1-9e9c-4890-8764-e84fe984b87a-image.png

e98f2f26-00a6-4ccf-8a05-10a18c502d5a-image.png

Isn't it a bit weird that in DsHidMini the host address is all 0's ?

Actually my memory was wrong, I could only make this controller work in SCPToolkit with a modified .dll. It is documented over here: https://github.com/nefarius/ScpToolkit/issues/241

Namely it seems this is the issue and the fix: https://forums.pcsx2.net/Thread-ScpToolkit-XInput-Wrapper-aka-ScpServer-Reloaded?pid=516138#pid516138

Is there any hope for that fix to come to bthPS3?

@cifroes said in PS(R) Ga`epad working via BT?:

I have read through all of that and my controller doesn't seem to have the bluetooth encryption problem. I'm only insisting because with old SCPToolkit my controller BT actually works. Isn't that a sign that it probably can also work with bthPS3?

You can not compare SCP to BthPS3, they work fundamentally different and due to the design and architecture of the Microsoft Bluetooth stack and its limitations it is not possible to make a 1:1 clone of SCP since we would then be back at square one: writing a completely custom Bluetooth stack which defeats the whole purpose of BthPS3 and I will never, ever consider engaging in this massive waste of time ever again just because some lazy cheap manufacturers can't stick to age old well-established standards.

I know it's frustrating but it is not my job and not within my reach to fix other people's crappy hardware in software 🙂

@cifroes said in PS(R) Ga`epad working via BT?:

Isn't it a bit weird that in DsHidMini the host address is all 0's ?

That's not weird, that is a massive problem, it means that for whatever reason the request to fetch the address either failed or that the pairing initially wasn't successful at all. Both are cases I have no control over whatsoever, it either works or it doesn't. That is the end of the road, the driver can't do more than the logic that already works flawlessly on thousands of controllers.

@cifroes said in PS(R) Ga`epad working via BT?:

Actually my memory was wrong, I could only make this controller work in SCPToolkit with a modified .dll. It is documented over here: https://github.com/nefarius/ScpToolkit/issues/241

Namely it seems this is the issue and the fix: https://forums.pcsx2.net/Thread-ScpToolkit-XInput-Wrapper-aka-ScpServer-Reloaded?pid=516138#pid516138

Is there any hope for that fix to come to bthPS3?

I have experimented with different MTU values in BthPS3 and so far none of them made any difference, plus since I do not own the affected hardware in question and can not reproduce it it is impossible for me to even try if that would make any difference.

I can try making the MTU configurable as registry values for adventurous users but that is about it, I do not have the time and resources anymore to dump hours upon hours upon days in this very inefficient method of trial-and-error and as long as nobody else steps up and helps and contributes who owns the hardware and can experiment with driver modifications this is another dead end.

I can and will not pursue this matter any further as long as I'm on my own, both for personal interest and in the interest of my health and sanity.

@cifroes said in PS(R) Ga`epad working via BT?:

Trace file: https://easyupload.io/7851kx

e25758f1-9e9c-4890-8764-e84fe984b87a-image.png

Thanks for the Trace. I have no idea what this error means or why it occurs, we're not even close to the stages that are required to establish channel connection so whatever happens here fails at a stage I have no control over anyway.

These are the source code sections that should correspond with the modifications expressed here.

Feel free to build and test for your own, I can only repeat myself, I never had success with that and as of now have no way to test or verify myself. All I can provide is guidance.