Game Input MultipleXer

You made my day with this info Does the fix support DYI or only GPP? And of courcse when will it be available for download

The fix only adds the ability to choose which GPP/Cronus/Titan to use.
It already was possible to choose between multiple DIY USB adapters.

Check your mailbox, I've sent you a mail with a link to a test version!

Yes it was. However, they both used the same controller which resulted in hangs after a while (approximately 2 min). Or did you resolve this issue as well?

mrangry777 wrote:the same controller

The same dualshock 4?

Yes. I should've been probably clearer about that. When you start multiple GIMX instance (using DIY) they all use the same dualshock controller, even if there is more than one connected to the PC. This rises problem in multiplayer configuration. The solution I thought of was to either put a choice box to select which dualshock to use(probably the best solution from the user point of view) or to lock controllers that are already in use. The same way that GIMX lock DIY adapters that are in use.

I think this problem can be worked-around using the winusb driver instead of the libusbK driver. Could you confirm this?

By the way, did you try the test software with multiple GPP/Cronus/Titan?

I would rather not to switch to win usb drivers. I have run into many stability issues while using it thats why I switched to libusbK driver on windows machine. My workaround right now is to connect the pads in reverse order. The order being which pad is being considered default. But that is a tiring solution.

P.S Unfortunately no, I am stilling waiting for second GPP it takes up to three weeks to ship them to Poland.

mrangry777 wrote:I would rather not to switch to win usb drivers. I have run into many stability issues while using it thats why I switched to libusbK driver on windows machine.

I'm not talking about the default windows driver, I'm talking about the "Winusb" driver that is available in the Zadig tool. They are completely different.

Ahhh ok pardon my ignorance So how exactly this workaround would work?

Very simple: instead of using the libusbK driver (which supports concurrent access), use the Winusb driver (which doesn't support concurrent access). The second gimx instance will fail at opening the same Dualshock 4 as the first gimx instance. It will try to open another one.