The USB DS4 must be plugged in, is it? Does it spit out any error?
My pattern matching may have been a little strict, try v1.1 v1.2 just uploaded at same url
Okay Nice! v1.2 actually spits out device ID's and it works. USB even works when DS4Windows is already running. Nice job!
Run tool once for Bluetooth. Run tool every time USB is plugged in. That's pretty much it. Next is to integrate within InputMapper/DS4Windows and do it automatically. Until Microsoft fixes things of course. Workarounds aren't something we want to keep doing.
Just need someone with a DS3 to send me the instance ID that uses so I can add DS3 to the app aswell.
i am using w10 pro 64bit DS4Windows was working fine,after this redstone update of w10 hide DS4 option is not working its says ''Warning:Could not open DS4 1C:96:5A ..... You must quit other applications like Steam,Uplay before activating ''Hide DS4 option''. all applications are closed but its still gives this error please help me
(08-03-2016, 11:45 PM)ReflexAction Wrote: [ -> ]i am using w10 pro 64bit DS4Windows was working fine after this redstone update of w10 hide DS4 option is not working its says ''Warning:Could not open DS4 1C:96:5A ..... You must quit other applications like Steam,Uplay before activating ''Hide DS4 option''. all applications are closed but its still gives this error please help me
Scroll up... You literally posted right below where we discussed the fix...
(08-03-2016, 05:36 PM)jhebbel Wrote: [ -> ]Just need someone with a DS3 to send me the instance ID that uses so I can add DS3 to the app aswell.
Maybe browse through ScpToolkit's source or ask nefarius. Something like this?
Code:
https://github.com/nefarius/ScpToolkit/blob/1c333a49e99477600ed33d2f95e7481fecb4b82f/ScpControl/ScpControl.ini
[DualShock 3 Controllers]
; GUID to identify supported DS3 controllers
; DO NOT CHANGE unless you know what you are doing!
DeviceGuid = {E2824A09-DBAA-4407-85CA-C8E8FF5F6FFA}
; HIDs of supported DS3 controllers
; EXPERIMENTAL: add you own HIDs here for tests
HardwareId = USB\VID_054C&PID_0268
HardwareId = USB\VID_054C&PID_042F
HardwareId = USB\VID_0E6F&PID_0214&REV_0580
HardwareId = USB\VID_045E&PID_028E
; Quad Stick
HardwareId = USB\VID_16D0&PID_092B
https://github.com/nefarius/ScpToolkit/blob/1c333a49e99477600ed33d2f95e7481fecb4b82f/ScpControl/WinUSB/Ds3Controller.inf
%DeviceName% = USB_Install, USB\VID_054C&PID_0268
%DeviceName% = USB_Install, USB\VID_054C&PID_042F
%DeviceName% = USB_Install, USB\VID_0E6F&PID_0214
%DeviceName% = USB_Install, USB\VID_16D0&PID_092B
https://github.com/nefarius/ScpToolkit/blob/987878db60495418d3520c435727e0b4fbc34a4a/README.md
USB\VID_054C&PID_0268 - Original Sony DualShock 3 Controller
USB\VID_054C&PID_0268&REV_0100 - BigBen BB4401 PS3PADRFLX (3rd Party Controller)
USB\VID_0E6F&PID_0214&REV_0580 - Afterglow AP.2 Wireless Controller for PS3 (3rd Party Controller)
Those may be it, added them to v1.3 of the tool, unable to test it though.
(08-03-2016, 04:45 PM)jhebbel Wrote: [ -> ]A good way to make this hands off for now is to create it to be executed from a task (this allows for elevation without prompt so completely hands off), then create a batch file to execute the task then launch IM/DS4Windows/SCP. Then add that batch to windows startup if desired or just make a desktop shortcut and use it instead of your normal application shortcut.
Would you be willing to write up a small tutorial showing how to do this? I'd love for the fix to work at Windows startup, but I'm a little lost when it comes to the "executed from a task" stuff.
(08-04-2016, 02:42 PM)pedrovay2003 Wrote: [ -> ]Would you be willing to write up a small tutorial showing how to do this? I'd love for the fix to work at Windows startup, but I'm a little lost when it comes to the "executed from a task" stuff.
Never done it myself, this one seems good though:
http://www.digitalcitizen.life/use-task-...ac-prompts