Thread Rating:
  • 16 Vote(s) - 4.88 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ScpToolkit (XInput Wrapper aka ScpServer Reloaded)
Hi, first of all, thanks for your all work and attention Smile

I want to ask you about the remap function of the scpMonitor aplication, because i want to remap the L1 and R1 triggers to L2 and R2 ones, and yes, i alread know that there is an existing profile that does that exact thing, but there is my problem: if i select that profile (and save+activate it), it works, BUT ONLY in the main window of the scpMonitor, the one with the ps4controller design, i mean, i can see in there the change between the triggers, BUT it doens't works at any games, or in xpadder (that continues to recognize the standard map of the triggers), or in any place except the main window of the scpmonitor :-?....any ideas?

P.S. And, for some reason, when i close the scpMonitor, it erases all the profiles :-/ so, i have to be reinstalling the driver over and ovr, for nothing, because like i said before, the profiles only works in the scpMonitor itself Sad

Sponsored links

(09-16-2015, 11:32 PM)dcardoso Wrote: That's ok. I can also edit the source and compile to help you in debugging.

That would make my life so much easier Happy How should we pull it off? Are we even in the same timezone? Laugh
(09-17-2015, 11:04 AM)Nefarius Wrote: That would make my life so much easier Happy How should we pull it off? Are we even in the same timezone? Laugh

Well I'm from Portugal, so UTC+00:00, GMT+01:00. I'll send you a pm.
Hi Nefarius:

I make a game controller for quadriplegics that uses the same USB report format as the Afterglow controller that you have been supporting, but has a different VID and PID.  

Adding the following two lines to the ScpControl.ini file:

[DualShock 3 Controllers]
...
HardwareId = USB\VID_16D0&PID_092B

and under:

[HCI]
; DualShock 3 (partial) product name
SupportedName = PLAYSTATION®3
SupportedName = Quad Stick

...has been working well, however, I noticed a few hours ago, you made a change in the Afterglow detection to start using the VID/PID instead of the report length, which is a good idea, but that is going to prevent ScpServer from working with the QuadStick.

Would it be possible to change the following lines in UsbHub.cs:

                       #region Afterglow AP.2 Wireless Controller for PS3 workaround

                       // if Afterglow AP.2 Wireless Controller for PS3 is detected...
                       if (current.VendorId == 0x0E6F && current.ProductId == 0x0214)
                       {

with the vid/pid for the QuadStick:

                       #region Afterglow AP.2 Wireless Controller for PS3 workaround

                       // if Afterglow AP.2 Wireless Controller for PS3 is detected...
                       if ((current.VendorId == 0x0E6F && current.ProductId == 0x0214) || (current.VendorId == 0x16D0 && current.ProductId == 0x092B))
                       {

plus add the two lines to ScpControl.ini?

There may be other places that are affected, but that is the place I noticed.

Fred
(09-18-2015, 02:15 AM)QuadStick Wrote: Hi Nefarius:

I make a game controller for quadriplegics that uses the same USB report format as the Afterglow controller that you have been supporting, but has a different VID and PID.  

Adding the following two lines to the ScpControl.ini file:

[DualShock 3 Controllers]
...
HardwareId = USB\VID_16D0&PID_092B

and under:

[HCI]
; DualShock 3 (partial) product name
SupportedName = PLAYSTATION®3
SupportedName = Quad Stick

...has been working well, however, I noticed a few hours ago, you made a change in the Afterglow detection to start using the VID/PID instead of the report length, which is a good idea, but that is going to prevent ScpServer from working with the QuadStick.

Would it be possible to change the following lines in UsbHub.cs:

                       #region Afterglow AP.2 Wireless Controller for PS3 workaround

                       // if Afterglow AP.2 Wireless Controller for PS3 is detected...
                       if (current.VendorId == 0x0E6F && current.ProductId == 0x0214)
                       {

with the vid/pid for the QuadStick:

                       #region Afterglow AP.2 Wireless Controller for PS3 workaround

                       // if Afterglow AP.2 Wireless Controller for PS3 is detected...
                       if ((current.VendorId == 0x0E6F && current.ProductId == 0x0214) || (current.VendorId == 0x16D0 && current.ProductId == 0x092B))
                       {

plus add the two lines to ScpControl.ini?

There may be other places that are affected, but that is the place I noticed.

Fred

Hi,

I read about the QuadStick, fantastic work! So you are the original author? Pleased to meet you Smile I abandoned this thread a while ago and opened my own, maybe we should shift this topic over there. In the meantime I'll merge your suggested changes into the source.

EDIT: sorry about the link confusion; simply had too many open Tabs  Laugh
New release up!
(09-19-2015, 11:26 AM)Nefarius Wrote: New release up!

Tried new version, but still have same error "Installation result: WDI_ERROR_NOT_FOUND". Please help me with this error
Question 
Nefarius
I tried replace file "Scarlet.Crush Productions\libwdi\x86\libwdi.dll" from version ScpServer v1.4.5706.37073 to ScpServer v1.5.5740.18577 and driver will installed without errors, but gamepad not work, scp monitor not see him. Maybe you wrong compiled libwdi.dll for x86 or this file broken or something else? 
Code:
19.09.2015 13:18:35 [INFO] - SCP Driver Installer 1.5.5740.18577 [09/19/2015 13:18:35]
19.09.2015 13:18:35 [DEBUG] - Preparing to load DIFxAPI
19.09.2015 13:18:35 [INFO] - Running as 32-Bit process
19.09.2015 13:18:35 [DEBUG] - DIFxAPI path: C:\Program Files\Scarlet.Crush Productions\DIFxApi\x86\DIFxAPI.dll
19.09.2015 13:18:35 [DEBUG] - Loaded library: C:\Program Files\Scarlet.Crush Productions\DIFxApi\x86\DIFxAPI.dll
19.09.2015 13:18:35 [INFO] - Microsoft Windows 7 Service Pack 1 (6.1.7601.65536 x86) detected
19.09.2015 13:18:35 [INFO] - Selected Win7 configuration
19.09.2015 13:18:38 [INFO] - Virtual Bus Created
19.09.2015 13:18:38 [INFO] - ENTER:  DriverPackageInstallW
19.09.2015 13:18:38 [INFO] - Looking for Model Section [SCProductions.NTx86]...
19.09.2015 13:18:42 [INFO] - Installing INF file 'C:\Program Files\Scarlet.Crush Productions\System\ScpVBus.inf' (Plug and Play).
19.09.2015 13:18:42 [INFO] - Looking for Model Section [SCProductions.NTx86]...
19.09.2015 13:18:42 [INFO] - Installing devices with Id "root\ScpVBus" using INF "C:\Windows\System32\DriverStore\FileRepository\scpvbus.inf_x86_neutral_21ca245c0e23d7a5\ScpVBus.inf".
19.09.2015 13:18:42 [INFO] - ENTER UpdateDriverForPlugAndPlayDevices...
19.09.2015 13:18:50 [INFO] - RETURN UpdateDriverForPlugAndPlayDevices.
19.09.2015 13:18:50 [INFO] - Installation was successful.
19.09.2015 13:18:50 [INFO] - Install completed
19.09.2015 13:18:50 [INFO] - RETURN: DriverPackageInstallW  (0x0)
19.09.2015 13:18:50 [DEBUG] - Preparing to load libwdi
19.09.2015 13:18:50 [INFO] - Running as 32-Bit process
19.09.2015 13:18:50 [DEBUG] - libwdi path: C:\Program Files\Scarlet.Crush Productions\libwdi\x86\libwdi.dll
19.09.2015 13:18:50 [DEBUG] - Loaded library: C:\Program Files\Scarlet.Crush Productions\libwdi\x86\libwdi.dll
19.09.2015 13:18:50 [INFO] - Device with specified VID (054C) and PID (0268) found, preparing driver installation...
19.09.2015 13:18:52 [INFO] - Driver "Ds3Controller_17d456a7-82a2-4580-975c-f6f5f1e5ae3f.inf" successfully created in directory "Driver"
19.09.2015 13:19:37 [INFO] - Installation result: WDI_SUCCESS
19.09.2015 13:19:37 [INFO] - Installed driver for DualShock 3 controller USB\VID_054C&PID_0268
19.09.2015 13:19:44 [INFO] - SCP DS3 Service Started.
19.09.2015 13:19:44 [INFO] - Install Succeeded.
19.09.2015 13:19:44 [INFO] - -- Install Summary --
19.09.2015 13:19:44 [INFO] - SCP DS3 Service installed
19.09.2015 13:19:44 [INFO] - Bus Device installed
19.09.2015 13:19:44 [INFO] - Bus Driver installed
19.09.2015 13:19:44 [INFO] - DS3 USB Driver installed
(09-19-2015, 12:29 PM)DANTE1613 Wrote: Nefarius
I tried replace file "Scarlet.Crush Productions\libwdi\x86\libwdi.dll" from version ScpServer v1.4.5706.37073 to ScpServer v1.5.5740.18577 and driver will installed without errors, but gamepad not work, scp monitor not see him. Maybe you wrong compiled libwdi.dll for x86 or this file broken or something else? 
Code:
19.09.2015 13:18:35 [INFO] - SCP Driver Installer 1.5.5740.18577 [09/19/2015 13:18:35]
19.09.2015 13:18:35 [DEBUG] - Preparing to load DIFxAPI
19.09.2015 13:18:35 [INFO] - Running as 32-Bit process
19.09.2015 13:18:35 [DEBUG] - DIFxAPI path: C:\Program Files\Scarlet.Crush Productions\DIFxApi\x86\DIFxAPI.dll
19.09.2015 13:18:35 [DEBUG] - Loaded library: C:\Program Files\Scarlet.Crush Productions\DIFxApi\x86\DIFxAPI.dll
19.09.2015 13:18:35 [INFO] - Microsoft Windows 7 Service Pack 1 (6.1.7601.65536 x86) detected
19.09.2015 13:18:35 [INFO] - Selected Win7 configuration
19.09.2015 13:18:38 [INFO] - Virtual Bus Created
19.09.2015 13:18:38 [INFO] - ENTER:  DriverPackageInstallW
19.09.2015 13:18:38 [INFO] - Looking for Model Section [SCProductions.NTx86]...
19.09.2015 13:18:42 [INFO] - Installing INF file 'C:\Program Files\Scarlet.Crush Productions\System\ScpVBus.inf' (Plug and Play).
19.09.2015 13:18:42 [INFO] - Looking for Model Section [SCProductions.NTx86]...
19.09.2015 13:18:42 [INFO] - Installing devices with Id "root\ScpVBus" using INF "C:\Windows\System32\DriverStore\FileRepository\scpvbus.inf_x86_neutral_21ca245c0e23d7a5\ScpVBus.inf".
19.09.2015 13:18:42 [INFO] - ENTER UpdateDriverForPlugAndPlayDevices...
19.09.2015 13:18:50 [INFO] - RETURN UpdateDriverForPlugAndPlayDevices.
19.09.2015 13:18:50 [INFO] - Installation was successful.
19.09.2015 13:18:50 [INFO] - Install completed
19.09.2015 13:18:50 [INFO] - RETURN: DriverPackageInstallW  (0x0)
19.09.2015 13:18:50 [DEBUG] - Preparing to load libwdi
19.09.2015 13:18:50 [INFO] - Running as 32-Bit process
19.09.2015 13:18:50 [DEBUG] - libwdi path: C:\Program Files\Scarlet.Crush Productions\libwdi\x86\libwdi.dll
19.09.2015 13:18:50 [DEBUG] - Loaded library: C:\Program Files\Scarlet.Crush Productions\libwdi\x86\libwdi.dll
19.09.2015 13:18:50 [INFO] - Device with specified VID (054C) and PID (0268) found, preparing driver installation...
19.09.2015 13:18:52 [INFO] - Driver "Ds3Controller_17d456a7-82a2-4580-975c-f6f5f1e5ae3f.inf" successfully created in directory "Driver"
19.09.2015 13:19:37 [INFO] - Installation result: WDI_SUCCESS
19.09.2015 13:19:37 [INFO] - Installed driver for DualShock 3 controller USB\VID_054C&PID_0268
19.09.2015 13:19:44 [INFO] - SCP DS3 Service Started.
19.09.2015 13:19:44 [INFO] - Install Succeeded.
19.09.2015 13:19:44 [INFO] - -- Install Summary --
19.09.2015 13:19:44 [INFO] - SCP DS3 Service installed
19.09.2015 13:19:44 [INFO] - Bus Device installed
19.09.2015 13:19:44 [INFO] - Bus Driver installed
19.09.2015 13:19:44 [INFO] - DS3 USB Driver installed

I'll set up a Windows 7 32-Bit test VM and see if I can replicate the problem. I only use 64-Bit systems so it could be entire possible that the x86-Lib is somehow damaged and I didn't notice. I'll keep you informed.
(09-19-2015, 11:26 AM)Nefarius Wrote: New release up!

Sorry for the question, are you the official manteinter or this are unofficial releases?




Users browsing this thread: 1 Guest(s)