Hey hey!
Yes, I'm still here!
No worries.
Just a quick update since it's gotten fairly quiet since the last release: major obstacles have been overcome!
What does that mean in detail? Well first of all I am now finally a proud owner of a code signing certificate powered by
Certum. I got it within
2 days! Can highly recommend them. Now why should you care about this? Since an official certificate (thanks, Microsoft
) is
required to publish so-called Kernel-Mode Drivers (which the
ScpVBus.sys is) I had to get one in order to be able to fix/update the one released by Scarlet-Crush about 3 years ago.
Virtual Bus aka Xbox 360 Controller emulator enhancements
So why should you care? The original (speaking; the one published by Scarlet.Crush) had a nasty bug included; when being used, you can not reliably use the ScpToolkit in conjunction with real physical Xbox 360 controllers or even other XInput-compatible hardware. This I was able to track down and fix. So now you will be able to mix as many different controllers as you want and they will life in harmony serving you in your gaming needs
I also implemented detection of the "real" player index assigned in the connection order of the controllers, meaning that if your first player uses an actual X360 controller, player 2 using a DualShock will now correctly get slot 2 assigned. Even with the X360 wireless controllers. Sweet.
Another issue (multiple issues in reality) where that some users reported BSODs using the drivers. I managed to fix those too so the VBus driver is now also more robust. And who likes system crashes anyways?
Driver Installer enhancements
Due to the shocking amount of people screwing up their system I decided to completely re-write the Driver Installer and dumb it down as much as possible. This means some sacrifices for users of exotic hardware but what can you do. Giving Windows-Users freedom and powers apparently was a very bad idea
(sarcasm included)
Fake Controllers aka PANHAIs
Didn't really have much time to pick this topic up once more. Did gather a lot more Bluetooth knowledge in the mean time though. Once changes mentioned above have been published I will look into this topic again. Promised. Remember; one-man-lab
USB driver changes
Since switching from
WinUSB.sys to
libusbK.sys added virtually no benefits (other than using up more space in the setup) and maybe even introduced additional bugs the upcoming release will switch back to
WinUSB.sys and keep using it. This will require all controllers and Bluetooth dongles to be re-installed, so sorry in advance
Oh, and I need more sleep but that's a problem on my end
Thanks to all the donors, your support is very much appreciated
Right, stay tuned, over and out.