I sent him an email this morning, my thoughts are he could change the hid/pid he is using for his virtual 360 controller to something the replacement driver wouldn't pick up, as any device can identify itself as an xinput device. This would in theory work.

Ill bring it up, but with vigem and fireshock under development he seems pretty busy. Even so, not sure what he could do about that, if you replace a driver its going to apply to virtual controllers as well because the pc simply doesnt know any better.

It feels like that concern is quite justified, probably better not to implement it at this point.

Maybe we should approach Benjamin Höglinger with this, his FireShock hidusb filter for Sony Dualshock 3 and 4 seems to not be all to far away from what would be needed, conceptually.

Have you had any direct contact with him so far?

do you know if it still works in modern Windows? Could possibly add support for their driver, but the down side is the virtual controller that you create with IM may also be effected thus defeating the purpose.

This reminds me of the XBCD project, it's a driver replacement for the 360 and original controllers, to get more full fledged direct input support, at the cost of xinput support.

Without some sort of driver replacement no as 360 support is rooted deep in windows.

Will it be possible to gain exclusive mode over a 360 controller?

In a way I want to take away control from windows when it comes to controllers as much as possible.

Simple things like re-assigning what control has which number would be great for example.

Benjamin is still working on some driver bugs. But it should work fine in IM.

Real name is Kenny, NES or NESGamepro is just my username.

Glad to hear it sounds like you'll be able to get the Nav controller to work. It should be great for old RPG's. I don't know if you remember this from back in the day:



It was so hyped up in Nintendo Power and never came out in the US, crushing a tiny childhood dream (let's not go into N64DD).