XInput Wrapper for DS3 and Play.com USB Dual DS2 Controller

[Ba'al]

@Scarlet.Crush

The controls and vibration are working well over USB and BT on my DS3 model CECHZC2U. The newer versions also fixed the problem when putting my pc to sleep.

I like the automatic power saving feature the service has now. Do you have plans to make the timer adjustable? I often want to manually shut off the controller quickly, but Steam pops up any time the Guide button is held (and I haven't found a setting in Steam to disable or change it).

Would it be possible to prevent the DS3 USB and BT devices from being shown in the "Safely Remove Hardware" list? It seems odd for a controller and a dongle to have an eject option.

[mikezilla2]

couldn't find any ghosts , having done everything youv asked and having everything installed that was asked of me , controller model is a CECHZC2H

this is what i see - running in blutoooth - still the same

[Image: hmmm_zps546ab098.png]

[Scarlet.Crush]

@Ba'al: Yes, I'm thinking of adding configurable idle disconnect which can be set from ScpMonitor.

I also find Steam popping up it's "Big Picture" mode when holding the PS button a bit of a nuisance. I was thinking of adding something like holding L1+R1+PS for 2seconds as a trigger for a quick disconnect of the DS3 - so it can cut in before Steam, and still have the Steam functionality available.

The Dongle & DS3 drivers use Microsoft WinUSB, I haven't found a way to configure it to remove them from the "Safely Remove Hardware" list yet.

@mikezilla2: Scp Virtual Bus is not showing up as a node, hence no XInput. Can you stop the Service, Right-Click ScpDriver.exe and select "Run as administrator", uncheck "Configure Service". Click Install, after it has finished copy the log from the text box and post it here.

[mikezilla2]

not quite what you asked , couldn't stop it " access denied" so disabled it from msconfig and restarted , ran the driver as admin , unchecked configure installed heres the log note i didnt wake the controller up or connect it via usb when i did this tho i probbly should have , controller is flashing now to


Selected WIN7 configuration.

INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - No matching devices found in INF "C:\Program Files\DS3 drivers\ScpServer\bin\System\ScpVBus.inf" on the Machine.
INFO - RETURN: DriverPackageInstallW (0xE000020B)
INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing INF file 'C:\Program Files\DS3 drivers\ScpServer\bin\System\BthWinUsb.inf' (Plug and Play).
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing devices with Id "USB\VID_0A12&PID_0001&REV_5276" using INF "C:\Windows\System32\DriverStore\FileRepository\bthwinusb.inf_amd64_neutral_c061481799a84ceb\bthwinusb.inf".
INFO - Will force install because driver is not better and force flag is set.
INFO - ENTER UpdateDriverForPlugAndPlayDevices...
SUCCESS - RETURN UpdateDriverForPlugAndPlayDevices.
INFO - Installation was successful.
SUCCESS - Install completed
INFO - RETURN: DriverPackageInstallW (0x0)
INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - RETURN: DriverPackageInstallW (0xE000020B)


edit got the phantom crap to show - wow umm thats alot of entries - an underlying problem i guess is a few of those entires would be to do with "IEEE 1394 BUS HOST CONTROLLER " well that is fire wire - never could get that to stop installing thats more or less moot but its probbly a few of the entries

now re moving everything to do with motion joy

Install Succeeded.

-- Install Summary --
Bluetooth Driver

edit - woke the the contorller up via usb -installing device - sees qoute saying somthing to the tune of " installing motion joy controller" gah how the heck do i get rid of that - theres obviously entries for it still in the registry and like wise i couldnt find it listed anywere

edit - plugged in the USB woke up the controller this time did the same as before
SCP Bluetooth Driver Installer 0.6.0.93

Detected - Microsoft Windows 7 Ultimate Service Pack 1 (6.1.7601.65536 AMD64)
Selected WIN7 configuration.

INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - No matching devices found in INF "C:\Program Files\DS3 drivers\ScpServer\bin\System\ScpVBus.inf" on the Machine.
INFO - RETURN: DriverPackageInstallW (0xE000020B)
INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing INF file 'C:\Program Files\DS3 drivers\ScpServer\bin\System\BthWinUsb.inf' (Plug and Play).
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing devices with Id "USB\VID_0A12&PID_0001&REV_5276" using INF "C:\Windows\System32\DriverStore\FileRepository\bthwinusb.inf_amd64_neutral_c061481799a84ceb\bthwinusb.inf".
INFO - Will force install because driver is not better and force flag is set.
INFO - ENTER UpdateDriverForPlugAndPlayDevices...
SUCCESS - RETURN UpdateDriverForPlugAndPlayDevices.
INFO - Installation was successful.
SUCCESS - Install completed
INFO - RETURN: DriverPackageInstallW (0x0)
INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing INF file 'C:\Program Files\DS3 drivers\ScpServer\bin\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_neutral_08870722fa4ead35\ds3winusb.inf".
INFO - Will force install because driver is not better and force flag is set.
INFO - ENTER UpdateDriverForPlugAndPlayDevices...
SUCCESS - RETURN UpdateDriverForPlugAndPlayDevices.
INFO - Installation was successful.
INFO - Phantom Device with Hardware/Compatible Id 'USB\VID_054C&PID_0268&REV_0100' already has 'C:\Windows\System32\DriverStore\FileRepository\ds3winusb.inf_amd64_neutral_08870722fa4ead35\ds3winusb.inf' installed on it.
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.
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)

Install Succeeded.

-- Install Summary --
DS3 USB Driver
Bluetooth Driver

[Scarlet.Crush]

@mikezilla2: so I think I know what's happening.

The bus driver is based on the Windows DDK Toaster Sample. From Prototype -> Alpha, I replaced the GUIDs used in the sample with new ones. I left a check in ScpDriver.exe to test for the legacy GUID, so that people upgrading would not get multiple Bus installs, with the intention of removing it for a Beta release.

It looks like one of your drivers (most likely Daemon Tools) is based off the same code but has not changed the GUIDS for their own ones.
To verify this, open Regedit and search for D35F7840-6A0C-11D2-B841-00C04FAD5171, expand the nodes, you should see a device name.

I've attached an archive, with the ScpDriver.exe I have been preparing for the Beta release, which has the legacy GUID check removed. Replace your existing ScpDriver.exe with it and re-run the Install as before. (output is now saved to ScpDriver.log)

Elevated Command Prompt : Right-Click on Command Prompt and select "Run as Administrator".

[mikezilla2]

thanks very much had a look in regedit - hmm nothing in there that that i can identify with just some none set values and system root and a few numbers attached - not many rows any who i did also remove the left overs for motion joy so thats all gone and yea interesting - it could have been motion joy interfering all along i say this becasue now windows thinks its 360 controller for srue im not srue if thats just the windows drivers i installed( from MS ) or just the your implamenttaion - in delphin when i first tried this over usb it was picking it up as a ps3 controller as youd get button layout X , S y etc now its pad N E , B etc so yea im pretty happy over all just a bit more sensitive that what it was and yea 360 controller shows up under devices would any of the things like lilly pad or such force native support ? ie getting the buttons to show up as what they relly are rather then xbox buttons just a moiner annoyance but it would just make it less confusing when configuring layouts instead of A:B Bad N it would be A:Y B:X if its not somthing that can already be done then maybe something that could be implemented at a later date im pretty happy over all or tho games do feel like im playing with an xbox pad not a feeling iv ever enjoyed but im happy

its redundant now but did you want to see what was under D35F7840-6A0C-11D2-B841-00C04FAD5171 ?

thanks very much i apprentice your help and your work on this project

[Scarlet.Crush]

@mikezilla2: don't need to see the registry, just needed to know that there was a device listed under that GUID.

When a DS3 is connected (via USB or BTH) ScpService sends a message to the Bus driver, the Bus driver then informs the OS that an X360 controller has been connected. The OS then installs X360 drivers for the X360 controller (if it hasn't been created before).
ScpService reads reports from the DS3 (button presses, axis changes) packages them and sends them to the Bus, the Bus then forwards them to the OS, which presents them as Xinput/DInput to any application (game) which is using the X360 controller. [Reverse for Rumble requests].

The custom Lilypad provided (in bin\Win32) presents a native DS3 input for PCSX2, with pressure sensitive buttons. Drop a copy of bin\Win32\LilyPad-Scp-r5350.dll in to your <pcsx2>\Plugins folder, and a copy of bin\Win32\XInput1_3.dll in to your <pcsx2> folder. Configure as per screenshots in Post #177.

[mikezilla2]

cheers ( no i didn't skim what you typed) thanks but not currently using PCSX2 or any PS emulators for now just dolphin - err i konw im asking the wrong person but ( maybe not) is guess its just a matter of dropping it in a simler folder in delphin ? i just wonder what that folder is

[Scarlet.Crush]

@mikezilla2: sorry, no idea, I've never used Dolphin.

[KrossX]

Just try and put it DLL alongside the main EXE, and during input setup select "XInput". That should do the trick I think. Unless using the latest version with native XInput, then just select XInput when mapping the controls.