..:: PCSX2 Forums ::..

(03-03-2013, 03:47 AM)Scarlet.Crush Wrote: [ -> ]@dak224: I don't see the DS3 being disconnected from USB in the Service log. [log is cleared every time you restart the service (reboot) so as not to eat up disk space]. Can you do the following -

1. Plug in your DS3 to USB.
2. Reboot your machine.
3. Unplug your DS3 from USB.
4. Wait 30 seconds.
5. Plug in your DS3 to USB.
6. Wait 30 seconds.
7. Unplug your DS3 from USB.
8. Wait 30 seconds.
9. Zip up the ScpService.log and post it as an attachment.

Couple of questions also -
1. Do the lights keep flashing when you disconnect from USB?
2. Is your controller a genuine Sony DS3?

Your dongle is a very early REV of the CSR chip - 0134. Mine for example is 7558.

The lights on the controller go from all 4 flashing to just 1 flashing when I disconnect it, and yes its a genuine controller.

I've attached the logs (sorry - couldn't get attachments to work on my last post)

if anyone has any game compatibility issues, try checking and possibly removing any other game controllers that may be connected.

Scarlett, I don't know why, but I noticed an issue specific to Battlefield 3, which first and foremost, im pretty sure is a bf3 problem, since it only occurs there. Anyways, for the last several days I couldn't get my DS3 controller to work with BF3, though all other games/emulators worked fine. I even managed to get a game to work which previously crashed with motioninjoy (planetside 2), but BF3 refused to see my controller. I recalled pairing my Wii remote the other day, and once I went into hardware manager and removed it, BF3 started seeing my controller again.

Can anyone explain why this is? I would like to keep my wii remote paired, and still have the DS3 Controller work if possible. Again, this is only an issue in BF3, everything else works. although I do recall the other day having to re-configure my DS3 controller for project64, but I couldn't even get BF3 to re-configure at all.

Firstly, kudos to you all for your efforts and this little gadget. I had been using Motioninjoy for a while and though it never really worked 100% for me, it's so simple to use and even more so to install. I much prefer this tool to that one though for many reasons.

That being said, I've got some feed back for you. I found this post entirely by accident while trying to figure out how to configure PCSX2, while not actually feedback, I'll be sure to tell my pals about your efforts here. (Though it'd be a waste, they all went and got wired 360 controllers anyways. it's the thought that counts though right?)

Second; It would have saved me 3 hours of frustration and time if in the first post it said 'this is not a stand-alone install' on the DL. (this part was much longer but it really just boils down to including a read-me with your download that says update the 360 controller drivers from Microsoft's webpage and the scpserver.exe is the one that makes the controller work)

Here's some things I noticed whilst trying to make this work; The wrapper by itself sort of worked. Buttons were being wonky and weren't the correct buttons at all. This was before I noticed the server.exe though.
During this point I loaded up Dead Space 3 and noticed under controllers it said 'DS3 Controller for windows' in the list. Later it changed to Xinput device when working 100%. it's still that way now.
I tested my controller (CECHZC2U) in Dead Space 3 launched via Origin, PCSX2, ePSXe, Dead Rising 2 off the record retail, Dark souls PTDE launched via Steam, and the stand alone mod Black Mesa. Holding the PS button brings up the big screen thingy.
After installing the full tool, looking at my 'Devices and printers' page it showed a generic controller labeled 'Playstation 3 controller' And also 'Xbox 360 controller for windows' with a trouble shooting icon. After installing the latest 360 controller drivers it all started working and the troubleshooting icon disappeared. This is when I did my testing.
My USB cord is just some standard micro USB cord I had lying around. I do have a second controller here somewhere but I don't have any samescreen MP games.
Edit: I had accidentally unplugged it after getting it working by taking my headphones off that had coiled around the cord. Plugged it back in and it resumed working. Not sure if relevant to anything or needed at all though.

Requested feature: minimize the server to task tray option! (Forgive me if you can already do this, I have no idea how to.)
A confirmation for closing the server if it's currently running.

relevant system info: Win 7 64 bit home premium, AMD platform. Do not own a BT connector; done via USB cord (planning on getting one though.)

@dak224: the logs show that your DS3 is correctly paired, and connects to the service correctly. The controller switching to 1 led flashing indicates that LED updates are being sent to the DS3 successfully.

BTH 00000000 None - on ScpMonitor inicates that the BTH Dongle is not receiving input from the DS3. 00000000 is the packet counter, None is the Battery status - no packets read.

DS3s send their input as EDR (Enhanced Data Rate) packets, so your Dongle is not understanding these. It does report itsself as being being BTH 2.0 + EDR capable, but as I mentioned is a very early REV of the CSR chip and looks like it don't support EDR properly.


@unvaluablespace: sounds like BF3 is doing something strange when searching for controllers. Couple of things to try -
1. Before starting BF3, on Game Controller settings - click Advanced and set Prefered Controller to be your Xbox 360 Controller for Windows.
2. Before starting BF3, Turn off or disable your Wii Remote.


@Braethias: when you run ScpDriver it installs ScpService.exe as a Windows Service, this provides a background task which implements the Server functionality and runs automatically. ScpServer.exe is a foreground task, which is included mainly for debugging purposes, you shouldn't need to run it.

The most common issue for the Service not being able to start is that it has been installed somewhere that is a special folder. eg on your Desktop. Zip up your ScpDriver.log and post it as an attachment.

From Post #301.

Quote:Important - make sure your Bluetooth dongle and DS3(s) are plugged in via USB before running ScpDriver.exe. Make sure you have the latest DirectX redist installed and the latest X360 drivers available.

@Ashnal: I've got XBCD fully compatible with the Virtual X360 now, barring the BSOD if setting Full Range + Deadzone 0 - which is purely an XBCD on x64 systems issue.

Attached an update for the Bus, screenshots of config and calibrated DInput. Can you test on your system.

Scarlet I have an issue using my DS3 with the emulator PSX the sticks are rotated 90degrees counter clockwise to what they should be. They came up as Axis 1 for left stick and Axis 3 for Right stick.

This is using PSX V1.13

I am getting so very sick of this thing not reconnecting to bluetooth after idling out on long cutscenes. I plug it back in and it connects I unplug to reconnect to bluetooth and all 4 lights flash for a while before turning the controller off. Heres the log. A reboot of the system does not help one bit neither does shutting it completely down then turning it back on.


*sighs* For now I am back to using my old Logitech Dual Action Gamepad sucks not hacing both rumble and having a cable that is to short for my needs hence the use of my extra DS3 over Bluetooth so I could get around the short cable issue.

@Topken: on DInput the stick axis are represented by half-axis values : X+, X-, Y+, Y-. Sounds like a configuration issue in that emulator. I don't have that emulator (or any PS1 emu) so can't say for certain.

I don't see any BTH connection attempt by the DS3 in the logs. Possible reasons -
1. Battery on the DS3 is very low - leave connected to USB until status switches from Charging -> Charged.
2. DS3 is not re-setting properly - press the reset button with a pin, small hole to the right of the centre screw.
3. Your Dongle is somehow going into a low power state and not waking up on a connection request - try re-setting the device in Device Manager.
4. Disable the Idle Timeout - right-click ScpMonitor Task Icon and select Configuration. Slide the slider to the far left .

Will this allow me to use my DS3 in native mode with pcsx2?

edit: connected via usb, I don't have a dongle

@Gvaz: yes, for DS3 native mode [pressure sensitive buttons] you have to use the supplied Lilypad-Scp or Pokopom plugin, and copy the XInput Wrapper [bin\Win32\XInput1_3.dll] to your PCSX2 directory.

Drivers run on USB only with no issue.

Oh, so it does. I checked my services and it wasn't running, so I restarted it up and it's all working now. I was either exhausted and closed it without thinking or it didn't start when windows launched, Don't pay any attention to me. Thanks for the reply though!


Question out of curiosity: Why can't the service launch with the exe, why does it need the CMD+ prompt to run?
Edit bonus question: If I get a dongle, nothing really changes though? No need to run server?

@topken: Why the older version? They released a new version not to long ago, 1.8.0, it has the option to assign each axis seperately. I had the same issue for a while until I realized I wasn't pushing the stick directly in one direction, but at an angle causing it to read as whichever way it leaned first.