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

[xavis75211]

nevermind, im a dumbfuck, i needed to put it into the usb 3.0 slot

[Scarlet.Crush]

@Alien: added your hardware ids, see Post #639

@Ba'al: how are you launching ScpDriver.exe?

The code is written in C# as an "Any CPU" target (launched by a 64bit process it runs as 64bit, launched by a 32bit process it runs as 32bit). On a 64bit system, if it is launched as a 32bit process it runs under WOW and will have a 32bit environment (hence it displays x86 in OS info) [Task manager will display it as "ScpDriver.exe *32" indicating it has been launched as a 32bit process.

In order for the drivers to install correctly ScpDriver.exe must run as a 64bit process on a 64bit OS. There is a check made to ensure this which is failing - 32bit process on 64bit OS.

Can you try the following :
1. Open a Command Prompt window
2. cd to your Install directory
3. run - echo %PROCESSOR_ARCHITECTURE%
4. verify it displays AMD64
5. run - ScpDriver.exe
6. verify it displays your OS info correctly
7. verify ScpDriver.exe does not have *32 in it's name in Task Manager.

@unvaluablespace: the documented features of XInput do not expose the Guide Button, as it has specific functionality in Windows Live games. There are however undocumented API calls in XInput (which KrossX uses in Pokopom) which allow the Guide Button to be used by applications (eg Steam). It should be possible to write an app as you described by using these undocumented API calls.

[tbx09]

Having a strange issue with my setup when using bluetooth. I added my hardware id to the inf file (%DeviceName% = USB_Install, USB\VID_413C&PID_8160)

I followed the instructions for installing (SCP-DS3-Driver-Package-0.8.0.100.7z). This installed the drivers and both USB & BT functionality worked as expected. I then stopped the service, installed the updated files (modifying the inf again with the above hardware id) and relaunched the service and once again the device worked fine via both USB and BT. Verified everything was working fine in both the test app and Steam.

However, whenever I restart my machine, the Scp DS3 Service does not automatically run. This isn't a major problem as I can just launch it via the services.msc window. However after doing so the Bluetooth functionality simply will not function/pair with my controller any more (connecting it via USB still works fine, but after disconnecting it refusing to pair up again via BT - the LED's flash for a few seconds then turn off.). Seemingly the only way I've found to fix this is completely uninstalling the Scp drivers, reinstalling the standard bluetooth drivers and following the whole process through from the beginning, obviously not ideal.

Any ideas as to what can be causing it to behave this way whenever I restart the machine? I'm re-pairing the controller to the system via USB after the restart but it simply won't function the next time I turn on my machine.

[Scarlet.Crush]

@tbx09: is it an on-board BTH adapter? It sounds like the original drivers for it do some non-standard initialisation. Does it run with the Windows Bluetooth Stack, or only with a 3rd party stack (ie BlueSoleil).

[tbx09]

Yeah, its onboard using the widcomm stack.

[andixa90]

hello scarlet,..
idle timeout not work for me,.
i have set idle timeout for 5 min, but my ds3 not disconnected,....

[unvaluablespace]

Ah ok. Well thanks for the heads up Scarlett, I will see if I can find anyone wiling to create this. It would be awesome for people like myself and others, as it would be convenient. It would not only benefit ds3 controllers but Xbox 360 controllers as well I would assume. I found a program some guy made for Xbox controllers that allow you to turn off the controllers, I assume he is using this undocumented API call to do this. Curious, but I wonder by using this API call, would it stop other guide button functions from working? Say if this app is running with steam, allow the command INSTEAD of big picture mode in steam? Or would they both be called at once? I ask cuz I can already see one drawback to this app I want, if so.

Also, does your driver allow for some sort of command to be sent to turn off the controller? I know ds3 and 360 controllers power off differently, so I ask in that if I WERE able to find a willing developer, to know if its possible to allow a pop up to turn off controllers. Oh and finally, how about a call to re-assign controllers similar to the ps3 allows? Thanks for your help, I'm just trying to get some of the bigger questions out of the way before I bother, lol. As I'm sure finding a willing developer will be no easy task.

[Ba'al]

@Ba'al: how are you launching ScpDriver.exe?

The code is written in C# as an "Any CPU" target (launched by a 64bit process it runs as 64bit, launched by a 32bit process it runs as 32bit). On a 64bit system, if it is launched as a 32bit process it runs under WOW and will have a 32bit environment (hence it displays x86 in OS info) [Task manager will display it as "ScpDriver.exe *32" indicating it has been launched as a 32bit process.

In order for the drivers to install correctly ScpDriver.exe must run as a 64bit process on a 64bit OS. There is a check made to ensure this which is failing - 32bit process on 64bit OS.

Can you try the following :
1. Open a Command Prompt window
2. cd to your Install directory
3. run - echo %PROCESSOR_ARCHITECTURE%
4. verify it displays AMD64
5. run - ScpDriver.exe
6. verify it displays your OS info correctly
7. verify ScpDriver.exe does not have *32 in it's name in Task Manager.

I normally just double-click the exe.
Running echo %PROCESSOR_ARCHITECTURE% from command line returns AMD64.
ScpDriver.exe displays Microsoft Windows 7 Home Premium Service Pack 1 (6.1.7601.65536 x86). Ran from both command line and double-clicking.
Task Manager shows ScpDriver.exe *32

[Scarlet.Crush]

@tbx09: looks like the drivers are not compatible with your on-board BTH adapter.

@andixa90: the Idle Disconnect is a battery save feature and is for Bluetooth connections only, is not used when connected via USB.

Threshold values are used to determine whether the DS3 is idle, if your Sticks are offset or are floating outside of the threshold values it will not be detected as being Idle.

@unvaluablespace: there is no way to stop Steam or a Windows Live game from receiving the Guide button presses, so yes both would receive it.

The drivers allow a BTH connected DS3 to be turned off (L2+R2+PS for 2 seconds), but not when connected via USB.
Ultimately it's XInput that assigns controller Id's, and there is no API call in XInput to re-assign them.

@Ba'al: ok, so it looks like somehow your system has been configured to run "Any CPU" targets under WOW. May have been something you have installed or configured since the last time you installed the drivers.

There is a .Net command line tool which configures this behaviour - Ldr64.exe.

1. Open an elevated command prompt
2. cd C:\Windows\Microsoft.NET\Framework64\v2.0.50727
3. run - Ldr64.exe query
4. if Current Status is 0x00000000 run - Ldr64.exe set64

Screenshot attached showing disabling and enabling the 64bit flag.

[Ba'al]

@Scarlet.Crush

Yep, that fixed it. Got it installed and running fine now. Thanks.
I remember having to set the setwow option a while back to get an app to run. I can't recall which one it was though. I guess I'll find out when something else quits working, lol. I guess I should have known changing settings to fix one thing would break another.