(02-25-2014, 10:40 PM)Scarlet.Crush Wrote: @InhexSTER: attached a build of DS4 tool which can share the ScpVBus with the Scp Drivers, I'll be releasing Scp Drivers which leverage this functionality shortly.
@electrobrains: Tested the XInput Plugin/Unplug behaviour on Win 8.1, it appears to have the same behaviour as XP/Vista/7.
Appears to work perfectly with a DS3 and DS4 in the sense that I can disconnect and reconnect each at will. Turning on the X360 (wireless), it grabs position 3 now. Every single device thinks it is device 1 and is reporting it is device 1 out of 4, but when you hit the Guide/PS/Xbox buttons, they correctly report which they are and they do not shuffle around.
DS4 on 1, DS3 on 2 still claiming it is 1 according to the LED, and X360 still on 3 claiming it is 1 via LED. Disconnect DS4 from 1, no reshuffle occurs. Disconnect batteries on X360 and reconnect, now it's on 1/4 (which DS4 was on.) Power on DS4 and it immediately grabs 3/4 again. Power off DS3 and it appears to not be relinquishing the Xinput device automatically -- is that something related to me having an older version of the DS3 Service running?
"So far so good!" What problem were you seeing? I was able to have DS3 Service and DS4 Tool working simultaneously on different BT adapters before but I admit to not testing it extensively. I've mostly just been playing single player games.
Edit: Strange behavior. Controllers in this state: X360 1/4, phantom (semi-disconnected) DS3 2/4, DS4 on 3/4. Hitting PS button on DS4 makes the XBox guide show up with either 2/4 or 3/4 selected. Pressing it again may make it go away, or make the other show up. So something weird going on in the shuffle there.
OH, wait, started two DS4 tools, hold on.... Okay, that weird behavior was a red herring. I am, however, still seeing the DS3 not relinquish its virtual ScpVbus instance and return it to the Xinput pool. Definitely the X360 controller and DS4 are lying about being on 1/4. They never were, even for a moment, initially when I was trying that. I think we are supposed to figure out which of the 4 Xinput slots we're going to get, and assign it ourselves, or we'll get the LED controller number reporting wrong.
Edit2or3: Okay, tried again. This time I reproduced the weird interaction, both DS3 and DS4 got slot 1/4. Restarting DS3Service caused the DS4 to disconnect, so it sent a force disconnect to the 'wrong' device. I want to help work on this some more later, but maybe you have some theories.