Game gets confused with inputs from xbox360ce joysticks

[Lancer[DL]]

I have a composite USB game controller that features 4 joysticks, which I was hoping could be used to play Overcooked. I configured xbox360ce to use it with other Steam games (successfully), but for Overcooked I see the following odd behaviour right at the start.

The first time I hit "A" on Joy1 to start a game, it causes Joy2 to join in. If I hit "A" again on Joy1, it registers a 3rd controller to play. If I hit "B" it quits the most recently added controller, and so on. If I hit "A" all the way through, I end up playing the game with one controller controlling 4 characters. Very odd.

Definitely Windows, xbox360ce and most other applications see them as independent joysticks, without crossing their inputs. I've had some issues with another Unity game confusing the inputs from xbox360ce, so perhaps it has something to do with how Unity manages game controllers?

Not sure if this is helpful as the game ought to be seeing the emulated joysticks instead of the real ones, but being a composite joystick, all of the game controllers have the same VID/PID and interface name (thanks to Windows only reading the first interface's string for composite joysticks). A further token is needed to identify each interface; eg: MI_(0-3).

[76561198103597845]

Hey Lancer[DL],


Thanks for getting in touch to report this.
Unfortunately, the game only officially supports the XBox and Steam controllers.
In order for Unity / the game to recognize these inputs as individual controllers, you might need to spoof their existence to look like separate XBox controllers.
I'm not sure which third party software you're using for mapping, but it might be possible to generate separate profiles for each one.
For further assistance, I could only recommend that you get in touch with the input device manufacturer directly.


Thank you,
BenTeam17

[Lancer[DL]]

Thank you for your reply.

In my case, I'm using the Xbox360 Controller Emulator to do the spoofing; it might be one of the most popular tools to this end. The emulator setup does see the joysticks as separate, and doesn't crossover inputs or anything when configuring. I've been able to use this emulator with some other multiplayer games successfully; "Capsule Force" and "Nidhogg" for example, but I don't think they're Unity-based.

Without xbox360ce, I don't believe Overcooked recognized any inputs from my joysticks. With it, I get the above behaviour. While handled oddly, I think it's probably the right spoofing tool to use (unless you could suggest a better one, that would be appreciated). I can check for additional emulation options with this tool that might help further distinguish the controllers, but it's doing it to some extent already.

I could try hooking-up a separate controller and see if it has the same effect while being emulated, and maybe that could shed some more light on the issue? The issue might only be with controller registration, with Unity seeing 4 joysticks (emulated) on a device but not sure which one it's getting inputs from. I've read that Unity doesn't make it very easy to match Joystick names with their devices, which is the reason why I'm suspicious of Unity here.

Thanks again.

[Lancer[DL]]

One thing I discounted was that the problem could be with xbox360ce itself. I don't have any issues with games that don't require xbox360ce (except perhaps Steam Big Picture mode), and while the emulator works with some games, I shouldn't assume it works with everything.

If my bug report brings up anything obvious from your (the developer's) side, please let me know. Otherwise, I'll pursue xbox360ce as the primary cause for now.

[Lancer[DL]]

I have discovered the problem was due to xbox360ce being misconfigured somehow. All I knew was I had other things working at one point but my recent configs weren't working for any games (all with the same problem). I had to delete all the related xbox360ce files, including the content in ProgramData/X360CE to essentially start from scratch and the next config attempt worked fine.

[Gueynar]

Hey,
I know it's a little late to answer, I had a similar problem and just wanted to let you know how I solved it (already opened a new discussion for it):
In my case I had two controllers which were recognized by the game without any emulator and one controller which wasn't. I used the Xbox controller emulator to get them all working and the problem appeared.

The solution was to clear all the controls for the controllers which already worked before in the emulator, so that only the one that didn't work before was mapped.

So my advice is: If you are using 360ce, remove it from the game folder and test all your controllers without it first. If they get recognized by the game without the emulator, delete their mapping from the emulator file.