(07-02-2013, 07:06 PM)Tetsuo3K Wrote: [ -> ]jj026, if you haven't tried it already, I had to disconnect and reconnect my controller once before it would sync.
I tried disconnecting by pressing L1 + R1 + PS and by unplugging and replugging the usb cable. In both cases the PS3 controller disappear from device manager.
did you meant something else by disconnect and reconnect?
Nope, that was it. By my understanding, your controller should sync automatically when you plug it in. This didn't seem to happen when I first installed the USB and BT drivers, so I disconnected and reconnected and that took care of it. I figured maybe that might be what was going wrong for you, but evidently not.
My next step would be to press the sync reset switch on the underside of the controller, and then see if it'll sync. If that doesn't do it, I'm afraid I'm out of suggestions, hopefully someone else can help you.
I reset my DS3. Oddly enough, the BT works only if I unplug the usb cable from the pc but not if I disconnect the cable from the controller.
Whatever, it works and now I get to use a wireless analog stick on PC without MiJ
thanks tetsuo3k
edit: Well my success was a bit premature. I can't get it to sync again
Hi Scarlet,
I was wondering if it's possible add the Hori PS3 Wireless Fighting Stick 3 to the list of PIDs/VIDs:
HID\VID_0F0D&PID_0032&REV_0001
HID\VID_0F0D&PID_0032
HID_DEVICE_SYSTEM_GAME
HID_DEVICE_UP:0001_U:0005
HID_DEVICE
It uses a USB RF dongle to connect to the PC and appears as "HID-compliant game controller" in the device manager.
Thanks a lot!
(07-01-2013, 10:53 PM)TheGershon Wrote: [ -> ]I get this
Still waiting for a reply, just sayin.
Hey Scarlet.Crush,
first of: thank you for your hard work. MotionInJoy is just the worst, but your package works perfectly fine and you're even sharing the source code, which is great in case something has to be fixed sometime.
I'm sure you're getting a ton of these questions, but could you please add VID_0489&PID_E00D to the signed driver list?
I'd like to try it out, I'm pretty sure it's going to work, it's an onboard BT-component built into some Lenovo notebooks. I'll provide feedback here asap.
Thanks again,
dibas
I bought a DS2 adapter to use my old DS2 with this wonderful tool.
However I had to uninstall my previous working Scp driver that I painstakingly installed. Painstaking because I have 2 bluetooth adapters, 1 which is internal and 1 which is just a dongle. When I installed the Scp bluetooth driver it installed over both my internal bluetooth and the dongle. So to install it only on the dongle I had to open up my laptop and physically disconnect the internal bluetooth adapter.
I can't install the bluetooth driver using the above method this time due to a quirk with my DS2 adapter where I have to uninstall and reinstall the Scp driver everytime I connect it. Needless to say it's impractical for me to open up my laptop whenever I connect the DS2.
Therefore I opened up the BthWinUsb.inf file and deleted the 2 references
(%DeviceName% = USB_Install, USB\VID_8087&PID_07DA) to my laptop's internal bluetooth adapter. I hoped by doing this my laptop's internal bluetooth adapter driver will not be overwritten. But unfortunately editing the BthWinUsb.inf file like that caused the Scp bluetooth driver to not install at all. The error code I'm getting is this:
RETURN: DriverPackageInstallW (0x103)
Code:
INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - RETURN: DriverPackageInstallW (0x103)
INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - RETURN: DriverPackageInstallW (0x103)
INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing INF file 'C:\Program Files\Scarlet.Crush Productions\System\Ds3WinUsb.inf' (Plug and Play).
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing devices with Id "USB\VID_054C&PID_0268&REV_0100" using INF "C:\Windows\System32\DriverStore\FileRepository\ds3winusb.inf_amd64_15691982ca5c21ae\Ds3WinUsb.inf".
INFO - ENTER UpdateDriverForPlugAndPlayDevices...
SUCCESS - RETURN UpdateDriverForPlugAndPlayDevices.
INFO - Installation was successful.
INFO - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_054C&PID_0268&REV_0100' for reinstall on next plug-in.
INFO - Marked Phantom Device with Hardware/Compatible Id 'USB\VID_054C&PID_0268&REV_0100' for reinstall on next plug-in.
SUCCESS - Install completed
INFO - RETURN: DriverPackageInstallW (0x0)
INFO - SCP DS3 Service Started.
Install Succeeded.
-- Install Summary --
SCP DS3 Service
DS3 USB Driver
Scarlet.Crush can you please help? Otherwise I'm stuck with wires.
(Rolling back to the original driver is not an option, it's grayed out.)
So Scarlet, remember
that glitch I mentioned before? Well it finally occurred again, and this time I got a pic. See SCPglitch.jpg attached below. Normally it uses Xinput 0 in dolphin, but suddenly it didn't work. Dolphin was reading it at Xinput 1. Yet SCP thinks it's still "Controller 1" (which is normally Xinput 0). Also note that the Xbox 360 driver display also thinks the controller is set to Controller 2 (upper right quadrant). Apparently, there is some confusion between SCP and the 360 drivers. Putting Xinput1_3.dll into my dolphin folder instantly fixes it.
Doing
what you instructed (renaming the Xinput1_3.dll files in win32 and win64 then trying SCPuser) got the result that is in SCPglitch2.jpg. SCPuser now matches Dolphin and the 360 accessories program in believing the controller is Controller 2, while SCP Monitor still lists it as Controller 1.
I also uploaded my ScpService.log and ScpDriver.log files. Hope it's enough. It should be noted that it worked fine yesterday, and that it just went into and came out of standby, something it has done a billion times without any issue, and then stopped working when I tried to use it after that. I'm running 1.0.0.103 Vanilla, btw.
@Trafford Devil
While I can't fix your SCP issues, I can make it a little easier for you. You can use the device manager to disable your internal bluetooth when installing the SCPdrivers. Also, if you install the SCP drivers while both are connected, you can use the device manager to pick the original drivers,
as I outlined once before.
@Scarlet
I'm noticing some repeats of issues in the thread here. Maybe you should create a FAQ?
(07-06-2013, 04:45 AM)MaJoR Wrote: [ -> ]@Trafford Devil
While I can't fix your SCP issues, I can make it a little easier for you. You can use the device manager to disable your internal bluetooth when installing the SCPdrivers. Also, if you install the SCP drivers while both are connected, you can use the device manager to pick the original drivers, as I outlined once before.
Brilliant! Thanks man that did it! I had read your post before when I went through the whole thread trying to solve it but I must've glanced over the bth ds3 device. I kept trying to update drivers for "Bluetooth server", "bth ds3 device" was under usb devices in my device manager so I didn't bother with it.
Great work on these, I used the MotionJoy drivers before these for a few years. I hated them but hey, they "worked".
But this method is the best. Thanks for this!
I have only one feature request, and I don't know if it is possible.
But I is kinda hard to know how much battery level is left on the controller.
Normally it should show in the middle when you press the guide button, but because the software thinks its connected wired that doesn't work.
No idea if you could work a way around this, or have like a something else.
Blinking lights would be fine, but so far I've always run out of battery without noticing.