![]() ![]() Launch a 4 player game (say, Mario Kart 64 on Mupen64 plus core).(Obvioulsy - doesn't have to be this exact combination, but multiple XInput gamepads are needed). Connect 2x XBox One gamepads wirelessly, and 2x DS4 gamepads wirelessly (via DS4Windows).all gamepads should be switched off and Retroarch not started), do the following: Steps to reproduce the bugįrom a 'cold start' (i.e. The assignment of XInput devices to players literally seems random. As one scrolls through the 'Device Index' in a 'Port X Controls' screen, they do indeed appear to be in DInput order, but gamepads are very quickly shown to be in an unexpected order as soon as one starts binding individual buttons.ģ60 gamepads often get confused for XBox One gamepads. I would expect the devices to be mapped in either DInput order (the order they appear in the Windows' 'Game Controllers' tool (joy.cpl), or by XInput UserIndex order. There is no rhyme or reason to how these devices are polled, and they are consistently muddled up. But - when I try to bind the controls to verify this - I notice that it is in fact bound to an XBox One gamepad, or even the other 360 gamepad. I will often go into, say, 'Port 2 Controls' and see that 'Device Index' is set as an XBox 360 controller. I certainly do not expect the XBox One and XBox 360 devices to get mixed up, but this happens more often than not and is not just a superficial / visual error. In other words: RA seems to toss a coin each time it tries to assign a gamepad to a user, such is the randomness. "Controller (XBOX 360 for Windows)( #1)") in RA is fact the #2 gamepad, and vicaversa. Sometimes, a gamepad that is marked as the first instance (e.g. The opposite can happen just as frequently. When one looks at the 'Port X Controls' screen, the Device Index may state that a player is assigned to a 360 pad, but by attempting to bind buttons, one realises that player is in fact assigned to an XBox One controller. I have been testing this extensively in recent weeks and will happily elaborate and perform further testing.ģ60 gamepads often get confused for XBox One gamepads. RA gets very confused about attached XInput devices when the Input Driver is set to XInput and multiple gamepads are attached (only tested with all wireless gamepads). I am quite confident that the emulated gamepads are not casuing problems here, as I often see RA get muddled and swap controllers when I just test with my two XBox One gamepads. The other 2 controllers are XBox One gamepads. Note that I use two DS4 controllers and emulate them as XBox 360 gamepads via DS4Windows. I have been testing how RA handles up to 4 players (all wireless gamepads). ![]() ![]() The following input issues occur regardless of the core selected, and have persisted for at least the last 2 weeks (may be much longer). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |