I get the impression I'm missing something here. I've got a DualShock 3 (model number CECHZC2E) and I've installed both SCPFilterDriver and SCPDriver (initially attempted this with just SCPDriver alone until I found a post saying SCPFilterDriver was required).
The DualShock 3 functions when connected via USB, and my Bluetooth dongle is showing a valid host address with HCI version 3.68 and LMP version 3.3, but whenever I unplug the USB cable to play via Bluetooth, the DS3 LEDs just flash and obviously have no connection. The pair button is usually grayed out when the cable is connected (and on the rare occasions that it isn't, it doesn't seem to do anything besides update the log claiming that the controller has been paired). I've got the PS3 turned off, have reset the DS3 a couple of times already, but still can't get it to work.
Any help?
(03-14-2013, 08:32 PM)Anonanon Wrote: [ -> ]Is there a way to detect itself as an Xbox 360 controller like MotionInJoy?
I'm having trouble playing games like DmC and Sonic Racing Transformed. In DmC, my DS3 isn't recognized at all, but it's fine in device manager and such. Sonic Racing Transformed picks up my DS3 only in the launcher, won't work ingame. On top of that, the launcher configuration won't let me bind X and square.
I also tried using it in emulators such as PS1 ones and MAME, the problem is that the button numbering is beyond whack. The D-Pad are recognized as sequential buttons rather than POV hat, the face buttons have absurd numbering like 8-12 or something like that, and the triggers are stuck as digital on-off buttons rather than axis analog. While this digital on-off L2/R2 are obviously good for emulators, I need it to be the opposite for modern racing games with sensitivity input.
Can anyone help me out?
sounds like you may have some other sort of issue. scarlett's driver makes the ds3 controllers emulate a xbox 360 controller. unfortunately, I cant say for the games you mentioned as I don't have them, but I don't know why your having issues in emulators. All the emulators I have tried haven't had any issues detecting scarlett's drivers at all. what version of windows are you using? 32 or 64 bit? and were you using any other drivers prior to using scarlet's? (motioninjoy, etc?) the numbering is probably a result of emulators noticing the controller as a regular gamepad, they might not have built in xbox controller support, which is normal. as for the triggers, I believe scarlet is working on it, and honestly I don't know much about it, but I can tell you in some emulators (dolphin for instance) they notice the triggers as analog, just depends on the action needed. for example, mapping the gamecube controller's "A" button with the analog R2 controller is going to result in a digital "on/off" response, as the A button is not analog. however, the Gamecube's analog R button gets noticed by the DS3's analog R2 button, so pressure sensitivity adjusts accordingly. older console systems did not have analog controls (other than analog sticks) up until the PS2 era of systems, in which case, to properly use pressure sensitive controls, you need to use the lilypad plugin. if you read through this thread you should find a discussion about how to enable pressure sensitivity for the PS2 controls.
good luck
(03-14-2013, 06:42 PM)Zeddidragon Wrote: [ -> ]I have tried that. I'm messing around with the controller some more today. It no longer seems to randomly shut off, and the right stick is no longer a bit off-center. Instead, the right stick is permanently pointing 100% up no matter what I do with it. the x-axis and anything else on the controller works fine, on the other hand.
I imagine whatever circuitry is responsible for sending the numbers for the right stick got a jolt of too much electricity through itself somehow and fried.
not sure what to tell you. Bluetooth should not have any sort of capability to "jolt" electricity through the controller, at least not enough to damage it. usb I believe only supports up to 5 volts, which I still don't think is enough to damage a DS3 controller, as im sure sony quality control should make sure of things such as that during assembly. then again, maybe you just have a defective controller? I can't see how a simple driver can stop a hardware related device from functioning. It's one thing if it just isn't working properly with scarlet's drivers. its another thing entirely when after using the driver, suddenly it doesn't work properly anymore on a ps3 itself. :-\
(03-15-2013, 07:47 AM)lesbianspankinferno Wrote: [ -> ]I get the impression I'm missing something here. I've got a DualShock 3 (model number CECHZC2E) and I've installed both SCPFilterDriver and SCPDriver (initially attempted this with just SCPDriver alone until I found a post saying SCPFilterDriver was required).
The DualShock 3 functions when connected via USB, and my Bluetooth dongle is showing a valid host address with HCI version 3.68 and LMP version 3.3, but whenever I unplug the USB cable to play via Bluetooth, the DS3 LEDs just flash and obviously have no connection. The pair button is usually grayed out when the cable is connected (and on the rare occasions that it isn't, it doesn't seem to do anything besides update the log claiming that the controller has been paired). I've got the PS3 turned off, have reset the DS3 a couple of times already, but still can't get it to work.
Any help?
getting a new controller to pair sometimes can be tricky. I just got a brand new ds3 controller and it would not pair initially, so I plugged it into my ps3 to test it, then because it paired with the ps3, it kept turning on the ps3 when I unplugged from pc via usb lol. I finally unplugged my ps3 altogether, reset the controller, restarted the DS3 service in windows, then holding down the PS button on the controller, plugged in via usb, while still holding down the ps button. I continued doing this for about 20 seconds, just to be safe. eventually, the controller finally paired.
so if you have a ps3 constantly getting in the way, try unplugging it to make sure the controller doesn't try to pair elsewhere lol.
(03-15-2013, 09:06 AM)unvaluablespace Wrote: [ -> ]sounds like you may have some other sort of issue. scarlett's driver makes the ds3 controllers emulate a xbox 360 controller. unfortunately, I cant say for the games you mentioned as I don't have them, but I don't know why your having issues in emulators. All the emulators I have tried haven't had any issues detecting scarlett's drivers at all. what version of windows are you using? 32 or 64 bit? and were you using any other drivers prior to using scarlet's? (motioninjoy, etc?) the numbering is probably a result of emulators noticing the controller as a regular gamepad, they might not have built in xbox controller support, which is normal. as for the triggers, I believe scarlet is working on it, and honestly I don't know much about it, but I can tell you in some emulators (dolphin for instance) they notice the triggers as analog, just depends on the action needed. for example, mapping the gamecube controller's "A" button with the analog R2 controller is going to result in a digital "on/off" response, as the A button is not analog. however, the Gamecube's analog R button gets noticed by the DS3's analog R2 button, so pressure sensitivity adjusts accordingly. older console systems did not have analog controls (other than analog sticks) up until the PS2 era of systems, in which case, to properly use pressure sensitive controls, you need to use the lilypad plugin. if you read through this thread you should find a discussion about how to enable pressure sensitivity for the PS2 controls. good luck
Yes I know these drivers are picked up as merely generic gamepads by emulators, but it's this driver's fault that UP/LEFT/DOWN/RIGHT is JOY4/JOY7/JOY6/JOY5, when it should be POV HAT in all formality. Tri/Square/Cross/Circle right now is identified as JOY12/JOY15/JOY14/JOY13 in these drivers, which is completely whack. It should obviously be JOY0 to JOY3. I just wish instead of having these drivers add itself as a generic gamepad (DS3 For Windows) it would identify itself as a genuine Xbox 360 Controller For Windows, so any XInput game works out of the box like most modern PC ports.
(03-15-2013, 09:22 AM)Anonanon Wrote: [ -> ]Yes I know these drivers are picked up as merely generic gamepads by emulators, but it's this driver's fault that UP/LEFT/DOWN/RIGHT is JOY4/JOY7/JOY6/JOY5, when it should be POV HAT in all formality. Tri/Square/Cross/Circle right now is identified as JOY12/JOY15/JOY14/JOY13 in these drivers, which is completely whack. It should obviously be JOY0 to JOY3. I just wish instead of having these drivers add itself as a generic gamepad (DS3 For Windows) it would identify itself as a genuine Xbox 360 Controller For Windows, so any XInput game works out of the box like most modern PC ports.
ah, well I better understand what you are saying now, and yes that is rather odd that the buttons are out of whack, but what I was saying in my previous statement is that the drivers don't show as a generic gamepad, they show as a xbox controller. But what im saying is that if a program or emulator doesn't have xbox controller support, then it will show inputs like a regular gamepad. BUT it sounds like your problem is something totally unrelated, so I can't help you there. Your going to have to wait for Scarlet's response, or someone more familiar on the matter. the only thing I can personally think of is if more than one device is connected, or your using some third party software (XBCD for example) and its making the controller think the buttons are higher in number, Because personally, for me, My dpad on all of my DS3's show as the POV hat, and only two emulators show them as regular buttons (but they are odd emulators anyway, and show every controller as that for me), and the triangle, square, etc buttons are all proper numbers (Button 1, Button 2, etc.) :-\ sorry I can't help you more.
@unvaluablespace: can you try disabling your Wii remote in Device Manager before starting BF3 and let me know if it fixes your issue.
@zoomHYPERIONzoom: the log is showing that the controller is not responding to the PSM 01 Service Channel request, so is less compatible than your previous knock off controller.
@Staahl:
@Drifter:
@sycdan:
added your hardware ids, see
Post #301.
@Zeddidragon: as Rama said, it is highly unlikely that your DS3 can be damaged by the drivers themselves. The only way that it could get damaged is if your USB port has some sort of fast charge capability which is out of USB spec.
Your DS3 will shut itsself down after a short period if the battery is very low. How old is your DS3? It may be that the battery is on it's way out.
@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.
@Static.Shock21: it looks like you are using an old version of the Bluetooth drivers, update to the 0.7.0.96 drivers on
Post #301.
@lesbianspankinferno: Sounds like you have a mismatch in your drivers. ScpFilterDriver is only to be used with the Filter Driver from Post #1.
Make sure you are using the 0.7.0.96 drivers from
Post #301.
@Scarlett.Crush The controller's about two years old. I recall getting the console when Castle Crashers came out for it at the end of 2010. I don't even use it all that much, so that seems like a bit of a short lifespan.
I do have a second PS3 controller. If this malfunction is as unlikely to come from your drivers as is claimed here, perhaps I shouldn't worry so much about trying to plug that one up and use it instead.
(03-15-2013, 12:34 PM)Scarlet.Crush Wrote: [ -> ]@lesbianspankinferno: Sounds like you have a mismatch in your drivers. ScpFilterDriver is only to be used with the Filter Driver from Post #1.
Make sure you are using the 0.7.0.96 drivers from Post #301.
I uninstalled SCPfilterDriver and have installed the 0.7.0.96 drivers you've recommended. No joy, unfortunately.
@Zeddidragon: can you try the following with your controller - plug in to USB, run bin\Win32\ScpUser.exe, check Advanced, check Extensions. Rotate both sticks a couple of times, then let them centre. You should see similar to the attached screenshot.
The extensions are received from a direct feed from the DS3 and bypass XInput/DInput, so should be able to see if the DS3 is reporting any offsets on the stick axis.
The drivers themselves do not set any Voltage or Current supplied to the DS3, these are handled purely by Windows. Can you verify that ScpMonitor shows 'Charging' and switches to 'Charged' after a period of being connected via USB. [Battery status is displayed from reports read from the DS3]
@lesbianspankinferno: 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, 02:19 PM)Scarlet.Crush Wrote: [ -> ]@lesbianspankinferno: 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.
I can confirm the SCP DS3 Service is currently running for the log you've requested.