@nefarius That's cool! I thought it might be the same case of XBOX One controllers (where one needs the real controller to authenticate (as implementing a software solution would cause license issues), but I'm happy that's not the case!
This I do not know. Yes, it's unfortunately becoming more common to embed protocol encryption or at least some sort of authentication handshake because the big vendors - understandably - don't like their hardware being ripped off by some foreign replica creators while not contributing to licensing and the software behind whatsoever. If the device requires crypto, it's not impossible but at least for me annoying enough to not deal with that ever.
In short: AirBender was a more or less direct port from the SCP sources and therefore has all of it's flaws - which I discovered afterwards - inherited and therefore I discontinued it, since not worth fixing. This will become the successor.
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