..:: PCSX2 Forums ::..

(03-15-2013, 12:34 PM)Scarlet.Crush Wrote: [ -> ]@Staahl:
@Drifter:
@sycdan:

added your hardware ids, see Post #301.

Awesome, that did the trick! Thank you so much for putting the effort into making this tool; installing it as a service was definitely the way to go. Love it. Cheers

@lesbianspankinferno: hmm, from the log your BTH dongle is started and configured correctly, the controller appears to be paired ok [the BTH master address read from the controller matches your BTH dongle - otherwise it would be auto-paired and would see a '++ Paired' in the log].

But no BTH connection attempt made by the controller in the log. Should be seeing something like the following in the log to initiate the BTH connection

Does the controller connect via Bluetooth ok on a PS3? (if you have one)

(03-15-2013, 04:16 PM)Scarlet.Crush Wrote: [ -> ]@lesbianspankinferno: hmm, from the log your BTH dongle is started and configured correctly, the controller appears to be paired ok [the BTH master address read from the controller matches your BTH dongle - otherwise it would be auto-paired and would see a '++ Paired' in the log].

But no BTH connection attempt made by the controller in the log. Should be seeing something like the following in the log to initiate the BTH connection

Code:

15/03/2013 14:07:14.445 >> HCI_Connection_Request_EV [04]
15/03/2013 14:07:14.455 << HCI_Remote_Name_Request [0419]
15/03/2013 14:07:14.455 >> HCI_Command_Status_EV [0F] [00]
15/03/2013 14:07:14.485 >> HCI_Remote_Name_Request_Complete_EV [07]
15/03/2013 14:07:14.495 -- Remote Name : 34:C7:31:A5:68:D0 - PLAYSTATION(R)3 Controller
15/03/2013 14:07:14.495 << HCI_Accept_Connection_Request [0409]
15/03/2013 14:07:14.505 >> HCI_Command_Status_EV [0F] [00]
15/03/2013 14:07:14.665 >> HCI_Role_Change_EV [12]
15/03/2013 14:07:14.815 >> HCI_Connection_Complete_EV [03]

Does the controller connect via Bluetooth ok on a PS3? (if you have one)

My controller connects perfectly to my PS3 via Bluetooth.

@lesbianspankinferno: ok, so that would suggest that it is an issue with your BTH dongle. From your ScpDriver log it does look to be a relatively early rev of the CSR chip (USB\VID_0A12&PID_0001&REV_1915)

Before installing the DS3 drivers were you able to pair any other BTH devices with it?
It sounds like the BTH Radio receiver stage in the dongle is either faulty or not getting powered for some reason. Is your PC set for High Performance?
Can you unplug the dongle from USB, then plugin again and repeat the test.

An additional test to verify that the controller is properly paired -
1. Download the Pair tool from Post #319
2. Extract the archive and place ScpPair.exe in to your ScpServer directory.
3. Stop the service "SCP DS3 Service".
4. Run the Tool.
5. Take a screenshot and post it.

(03-15-2013, 12:34 PM)Scarlet.Crush Wrote: [ -> ]@Anonanon: it looks like your using the Filter Driver from Post #1, this merely provides a Start command to the DS3. The button layouts are provided by the DS3 itsself.
Update to the new Beta drivers on Post #301, these give native XInput functionality, where the drivers map the DS3 button layout to an X360 Wired controller layout and don't require the XInput Wrapper.

I'm a USB wired user. I grabbed ScpServer-0.7.0.96.7z from post #301, ran ScpDriver.exe, pressed install, did its thing then my PC froze. Rebooted it, tried out the controlling testing tool provided, it works. However when I tried it with psxfin, no controllers were detected. I went to Windows' game controller panel, there was nothing in there. I checked Device Manager and found an Xbox 360 Controller for Windows. Weird.

@Anonanon: the new drivers work by creating a virtual Xbox 360 Controller for Windows, inputs from your DS3 are mapped to this virtual controller to give native XInput.

If no controller is showing in the Game Controller panel and Device Manager shows an exclamation on the Xbox 360 Controller for Windows you will need to update the drivers for it. Windows ships with outdated crappy drivers. Right-click on it in Device Manager, select Update Drivers -> Search automatically for updated driver software.

The drivers support Bluetooth, but it is not required, will run fine on USB only.

(03-15-2013, 09:02 PM)Scarlet.Crush Wrote: [ -> ]If no controller is showing in the Game Controller panel and Device Manager shows an exclamation on the Xbox 360 Controller for Windows you will need to update the drivers for it. Windows ships with outdated crappy drivers.[/b].

Everything is now working in order, it's recognized as a native Xbox 360 controller, works in DmC and Sonic Racing Transformed.

I just want to add some extra pointers as suggestions. The new 2009 Xbox 360 controller driver adds this weird pop-up notification function to the guide button. It shows your player port and battery life or something. I almost facepalmed because of how useless this is (typical of MS) because this prevents me from binding the PS home button to something useful like screen capture in MAME. Will we be able to bind this button in the future?

Secondly, since it's emulating an Xbox 360 controller, the triggers are recognized as an axis function. With a lot of Japanese indie games, they don't pick up any axis input and only digital on-off button. I would like to see a simple toggle between axis and digital in the testing application.

Thanks for your swift tech support and thanks for this amazing, painless driver.

i updated the files like you said and so far the newer controller is not connecting wirelessly.

@Static.Shock21: can you verify that the "SCP DS3 Service" is running. Control Panel -> Administrative Tools -> Services. See attachment. If it is not started, close ScpServer if it is running, then right-click "SCP DS3 Service" and select Start.

Plug in your DS3 to USB, wait 30secs, Unplug, wait 30secs, Plugin, wait 30secs, Unplug wait 30secs. Zip up your ScpService.log and add it as an attachment and post.

(03-15-2013, 05:06 PM)Scarlet.Crush Wrote: [ -> ]@lesbianspankinferno: ok, so that would suggest that it is an issue with your BTH dongle. From your ScpDriver log it does look to be a relatively early rev of the CSR chip (USB\VID_0A12&PID_0001&REV_1915)

Before installing the DS3 drivers were you able to pair any other BTH devices with it?
It sounds like the BTH Radio receiver stage in the dongle is either faulty or not getting powered for some reason. Is your PC set for High Performance?
Can you unplug the dongle from USB, then plugin again and repeat the test.

An additional test to verify that the controller is properly paired -
1. Download the Pair tool from Post #319
2. Extract the archive and place ScpPair.exe in to your ScpServer directory.
3. Stop the service "SCP DS3 Service".
4. Run the Tool.
5. Take a screenshot and post it.

Hmm. I've been able to pair it with phones before. I've just tested it -- still able to pair, but unable to send or receive files, so you may be right.

I'm not entirely sure what you mean by 'set for high performance', though.

I've unplugged the Bluetooth dongle and plugged it into another USB port for this test.

I appreciate the assistance - I may just order a new dongle tonight. Should've known better than to buy the cheapest dongle on DealExtreme >_>.