..:: PCSX2 Forums ::..

(03-17-2013, 11:09 AM)Scarlet.Crush Wrote: [ -> ]@protomouse: added your hardware id, see Post #301.

Thanks! It's working beautifully :).

@Zeddidragon: I've been doing some testing with Selective Suspend and my Atheros based dongle (Asus BT211).

It looks like the Selective Suspend setting in the Power Plan is ignored. Not sure whether this is a WinUSB or Windows 7 issue.

After a reboot the Dongle is in Power State D0 - normal working mode. First screenshot.

Dongle stays in D0 until the DS3 is disconnected (by L1+R1+PS for 2 seconds in this test), then after a timeout it drops to Power State D2 - device is asleep. Second screenshot.

Pressing the PS button on the DS3 initiates a connection to the dongle and it wakes up and returns to Power State D0. Third screenshot.

I think your BTH adapter is not performing the last stage correctly. This appears to be exactly the same issue that Topken is experiencing - after an Idle disconnect the DS3 is not able to reconnect.

I've attached the usbview application which you can use to view the Power State of your BTH adapter. The value is not updated automatically, so you have to select a different device then switch back to your BTH adapter to see changes.

The WinUSB documentation states that Selective Suspend for a device is disabled by default unless it is specifically enabled by the driver. Should not be seeing the adapter being suspended, I had to add a load of registry settings to get my dongle to suspend.

If we can verify that this is what is happening I can look into possible resolutions.

Ok after taking a look with the usbview app my idVendor is 0x04CA = Lite-On Technology Corp.

@Topken: even though your idVendor is displayed as 0x04CA, it does not guarantee that the BTH chipset is manufactured by Lite-On.

Chipsets are largely manufactured by a small number of manufacturers (CSR, Atheros, Broadcom, etc), these are sold on to other manufacturers who rebrand them. There is not much point designing a new chipset when you can buy them as components for pennies.

The level of customisation available may differ between chipsets. Asus have their own Vendor Id 0x0B05, but my Asus Dongle displays the Atheros Id 0x0CF3 - so either that particular chipset didn't support customisation of VendorId or Asus didn't bother customising it.

and yet its a gigabyte made products which even adds to the confusion. I know its Atheros based since it uses the Ath3k drivers in linux

https://patchwork.kernel.org/patch/1918731/

There are the ath3k and ath5k bundle of drivers

Hey, I downloaded and installed your drivers for my DS3 controller, and after setting up x360ce for Dark Souls, everything works except for 2 things. The guide button and rumble. Both my computer and x360ce detect it as Button 17, but your testing program and Dark Souls don't show any response to it. Anybody know how I can fix these 2 things, as these are what are preventing me from fully coming away from MiJ for these drivers.

(03-17-2013, 07:18 PM)Chimpii Wrote: [ -> ]Hey, I downloaded and installed your drivers for my DS3 controller, and after setting up x360ce for Dark Souls, everything works except for 2 things. The guide button and rumble. Both my computer and x360ce detect it as Button 17, but your testing program and Dark Souls don't show any response to it. Anybody know how I can fix these 2 things, as these are what are preventing me from fully coming away from MiJ for these drivers.

And also, do I really need to put the x_input file and/or x360ce for every game that I use, as that seems to be the case.

@Chimpii: if you are using the drivers from Post #1 (XInput-Wrapper-SCP-2.2.1.88.7z) then these do have limitations since it is an XInput Wrapper and you will have to copy the XInput DLL / x360ce for each game.

I have been working on a set of replacement drivers which aim to remove these limitations. The new drivers provide Bluetooth + USB + Native XInput for DS3s, and do not require the use of a Wrapper dll/x360ce. There is a link to these drivers in Post #1, or you can go there by following this link Post #301.

(03-17-2013, 09:49 PM)Scarlet.Crush Wrote: [ -> ]@Chimpii: if you are using the drivers from Post #1 (XInput-Wrapper-SCP-2.2.1.88.7z) then these do have limitations since it is an XInput Wrapper and you will have to copy the XInput DLL / x360ce for each game.

I have been working on a set of replacement drivers which aim to remove these limitations. The new drivers provide Bluetooth + USB + Native XInput for DS3s, and do not require the use of a Wrapper dll/x360ce. There is a link to these drivers in Post #1, or you can go there by following this link Post #301.

Oh okay, though I'm using my controller through USB as I don't have bluetooth on my computer. Will these still work with me?

EDIT: Oh wow, I just installed the drivers you linked, and they worked perfectly in a game that was previously not working at all, I'll go check if everything is working in Dark Souls without x360ce.

EDIT2: Just went into Dark Souls, and everything is working. Thanks so much for the driver and the help!

@Scarlet.Crush
The USB program never show my bluetooth falling asleep at inopportune times. At first, I was unable to replicate the problem. Then I gave up, smacked my laptop shut (putting it into sleep mode), and went home. After opening it again, my controller was no longer able to connect! Uninstalling and reinstalling the driver again seems to fix it.

And no, the bluetooth was not sleeping at the time I didn't manage to connect it.

Are the drivers intended to be reinstalled every session I use my computer?