Just tested, issues still persist in my setup as outlined in my previous post. Both on a desktop setup with active XInput emulation and on Steam with controller configuration enabled. As soon as emulation is turned off things return to normal. I'm on the latest joy2 version. Found a little test .mfa I made last year to show the assignment issue. It's just one line that reads out "last input". With active XInput emulation, this value will always be dominated by one controller, while pressing the other one just induces a short flicker. Here's the Download.
As a side note: Steam just introduced "Remote Play", it's a Steam-based emulation that allows players to invite a friend elsewhere to their account for a local Co-Op session. Steam says the input will be nearly lag-free and the second player won't even have to own the game. This is such great news for us indies. We've not tested this with Outbuddies yet, think the service will launch late October, but I'll report how it behaves on XInput and Joy2. https://www.pcgamer.com/steams-remot...iplayer-games/
Could you post another example that better shows the problem?
@Yves : You have the Outbuddies .mfa, choose the generic gamepad input in the options menu, that means using joy2, then you can test if you have the same issues. For local CoOp, call the Pause menu and press joystick up. You'll then be asked to assign a device for each player. This is the first point input will fail. Also when connecting two gamepads in SP, one of them might not work, although it should always read out the "last active" one. It's honestly impossible for me atm to dissect this from this giant project. An option is to modify the thing I presented and check if narrow dead zones actually cause this, I may be able to set it up in the next weeks, but for now, I need to care about the Outbuddies release next Tuesday. Fingers crossed^^
edit: Btw, I don't think dead zones are an issue, because if this was the cause turning emulation On/Off would likely make no difference.