The number of controllers listed seemed to be related to the number of times I tested my build of the ScpDriver.exe, but I wasn't counting exactly. The joy.cpl controllers list does not show this, just in Steam's BPM.
I have no idea where to suggest looking for that issue. This was not the case with the original ScarletCrush driver. In my Steam Big Picture Mode controller settings, I see over a dozen XBox 360 controllers available in the controllers list, even when nothing from ScpServer is currently installed.
I think a side effect is some other system list of game controllers never gets cleaned up. I think you may be aware that the ScpDriver uninstall does not uninstall the PS3 driver itself and the user has to manually do so in the Device Manager. It was hidden in the Game Controllers list after the ScpDriver install and moving it updated the virtual XBox 360 controller values when the Server or the Service were running. The good news is I was able to add "SupportedName = Quad Stick" and "HardwareId = USB\VID_16D0&PID_092B" in the appropriate places in the ScpControl.ini file in your build and the Quad Stick (which shares its USB report format with the AfterGlow) worked just fine. Install logs.txt (Size: 3,52 KB / Downloads: 213)
and the ScpDriver text logs from both your and my builds attached. I downloaded the source as of a few minutes ago and was able to successfully build both SLN projects in Visual Studio Community 2013, however, when I run ScpDriver.exe, the installation log shows an error: More progress on doing a build from scratch, but still some problems:
0 kommentar(er)
