Thank you both! 🙂
The solution with DS4Windows is interesting, I'll try it.
Regarding HidHide, I can't understand why the program can't see my connected controllers (I tried the two most recent versions)!
I highly recommend not fooling with these folders, you can do more damage than harm. If Driver Store Explorer doesn't list it, the damage is already done.
Why do you care so much anyway? A driver file that has no service loaded simply just sits there as any other file, it does nothing but occupy a few kilobytes of disk space so I don't understand what we're discussing here...
Heck, every Nvidia GPU driver update leaves countless outdated files on the system, who cares 😁
@mlengka93 this is tricky; the product name embedded in the USB descriptor differs from the one in the Wireless part of the chip/firmware, probably necessary to fool the PS3 into accepting an USB connection.
Basically rumble (and Lightbar changes?) through a virtual DS4 is currently completely disabled as time of writing because of major compatibility issues with games and the ViGEm Bus driver. Until that is fixed properly it will stay disabled because a horde of ignorant pricks floods their issue tracker and wastes everyone's time instead of reading the release notes.
So I'm positiv you experience this case. Since you didn't provide any links or version numbers this is my best guess.
@if555666 use the reset pin on the back of the controller, clears internal memory, is basically a factory reset. Afterwards plug into PS3 via USB again and you're good to go. If not, you're facing some obscure hardware issue we can't help you with I'm afraid.
ScpToolKit presented your DS3 as if it were a Xbox 360 controller to Windows by default. This is NOT the case with DsHidMini. Because most games expect a Xbox 360 controller to work properly, using your controller in most Hid Devices Modes will get you a broken layout.
To have the same functionality (Xbox 360 emulation), DsHidMini requires a few extra steps.
I can only repeat myself: Microsoft has deemed Windows 7 dead and they even go as far as to severely put obstacles in the way of any independent driver developer (me). It is in no way feasible for me as a single individual and business owner to further invest in a dead platform where the manufacturer actively wants to see driver support die for a community/hobby project that I don't intend to monetize and declare feature-complete.
Sorry pal, it ain't going to happen. Not from me. I need to go with the future and that is Windows 10 for kernel drivers only.
As of time of writing you can not have multiple Bluetooth host radios active at the same time, that is a limitation of Windows so this applies to BthPS3 as well, you can only use one host radio. You can have multiple controller on that ofc.
@nefarius OK it looks like there are still problems with my bluetooth, because both my headset and controllers are stuttering after connecting. I had previously only tested that they connected and worked, and hadn't used them since then. The headset has been tested on my phone and laptop and works without stutter there, and the controller seems to not stutter on my laptop as well. The headset is new but the controllers are old and did not stutter prior to this whole uninstallation process. The only drivers changed since last week I believe are an updated graphics card driver and those pairing with the headset. Any ideas on how to proceed would be appreciated.
XOutput emulates a Xbox controller by using ViGEm, meaning that ViGEm is not at fault here, in fact, everything is working exactly as it should.
If there are buttons assigned the wrong way, that can only means that:
You've set Xoutput incorrectly or
You are confusing XInput's with Nintendo's button scheme. In the Nintendo controller, A/B and X/Y have their position switched when compared to the XInput scheme (Xbox controller)