Well, you gotta look at it from multiple angles. I try to avoid depending on latest and greatest features if they're not an absolute necessity and don't really wanna dictate the OS version users have to have. On the other end though the toolset and overall quality of the Windows Device Driver ecosystem is very compelling with the current releases of Windows 10 so I don't know, we should keep an eye on Microsoft's plans and if they manage to go "all Windows 10" (for a certain percentage ofc.) then I'll most probably follow.
FireShock v2 (the "Shibari edition") was actually my first driver utilizing UMDFv2 and I was amazed how fast I became in prototyping simply because one major factor was eliminated; a programming error doesn't result in an instant system crash. Also no need for strict signing because it's not kernel code.
I configure the controls in x360ce and it works very but when I activate the emulation in VDX the triggers (LT-RL triggers of the emulated xbox 360 controller) do not work as seen in the image. This is my problem.I use a generic USB controller
Thanks for the help Nefarius, So I just try plugging in my DS3 and it works! I think the problem is just the PS navigation controller. I'm sorry for the confusion. I was really trying to get the Navi controller to work.
NM i was able to reset the navi controller and it works now with USB. It just doesnt work with bluetooth.
UCR might be able to do this (As and when Nefarius adds the API end-points for outputting to DS4 touchpad).
We have an Interception provider for keyboard and mouse, which supports absolute mouse input. This may work with the touchscreen, not sure if you will get multi-touch, but I don't think you want that?
If the answer is no, are you predicted when it will be implemented?
I have no plans on doing this. It would involve modifying x360ce which isn't the goal of the VDX tool. It's a simple proxy application to turn any controller into either a wired x360 or DS4 controller. Nothing more, nothing less.
I should have probably worded that better, my apologies. What's flawed ist the ScpVBus, when Shaul and I analysed it years back we found a bug which may (or will) cause weird side-effects when you use a virtual SCP X360 controller in combination with a real physical one. We've attempted to fix that but then again, this was in an early time where I was nowhere near as comfortable in writing and diagnosing kernel drivers as I am today. So while SCP won't harm your machine if you use it properly, it might lead to unforeseen consequences when mixed with physical controllers.
That puts me in kind of a pickle since the documentation is still full of warnings that the project is still in an alpha state and is not an alternative to ScpToolkit, but at the same time it seems that ScpToolkit is something to be avoided.
It's just an advice. If it still works for your particular setup, hey, stick with it!
So the question is, should I transition from ScpToolkit to the new driver (I THINK it's Fireshock + Shibari, since I'm only using my PS3 controller via USB, but I'm not sure)? On top of that, the topic I linked to shows that a new version of Fireshock is coming up. So if I should transition, should I do it now, or wait for the new one? Even if ScpToolkit still works kinda fine (and probably the only reason why I could play The Force Unleashed with a controller)?
Same deal with my advice for the current situation: if SCP works for you - ignoring bugs that are not addressed - then stick with it.
It's probably a pretty stupid question, but this project feels a bit confusing to me (especially without a proper website).
Nah it isn't stupid, it is confusing, I admit but let me explain. The day only allows for a few steps of progress. If I work on a polished site, I can't research or code. If I devote more time to giving support - especially to discontinued projects - I can't research or code. You get the idea. So recently I decided to form at least somewhat of a plan: stop dumping time into the useless blog, use the forum. Stop building a polished documentation platform for something that is in itself not yet polished. Instead utilize the forum.
I also greatly underestimated the task of replacing SCP as a whole suite and pleasing everyone. I dove into driver development in mid-2016 with zero background knowledge. I had to build up know-how and confidence in the protocols involved (USB, HID, HCI, L2CAP, ...) and get familiar with kernel development, debugging and pitfalls. Besides my day job. It's nuts. If you think about it, I'd belong in a mental asylum All of the DS3-related projects (excluding ViGEm because that's stable and a project on its own) I started since abandoning SCP were really test beds and until like three months ago all my small and devoted community and I did was research and development. But now the puzzle pieces slowly all fall together and we shift from guessing to producing. Exciting times.
What I've also learned is to hold back on releases that have alpha/beta character. It just fuels the confusion and leads to more support inquiries which hold me back from coding. So the best strategy I could settle on is to publish progress like I started doing with my DS3 Bluetooth research. And if I don't get struck by lightning this will become a product you can simply install with a setup, pick up your controller and have a go