{"action":"opened","issue":{"url":"https://api.github.com/repos/libretro/RetroArch/issues/7870","repository_url":"https://api.github.com/repos/libretro/RetroArch","labels_url":"https://api.github.com/repos/libretro/RetroArch/issues/7870/labels{/name}","comments_url":"https://api.github.com/repos/libretro/RetroArch/issues/7870/comments","events_url":"https://api.github.com/repos/libretro/RetroArch/issues/7870/events","html_url":"https://github.com/libretro/RetroArch/issues/7870","id":395134070,"node_id":"MDU6SXNzdWUzOTUxMzQwNzA=","number":7870,"title":"UWP?  Second player game pad is unusable","user":{"login":"DavidRieman","id":11418078,"node_id":"MDQ6VXNlcjExNDE4MDc4","avatar_url":"https://avatars2.githubusercontent.com/u/11418078?v=4","gravatar_id":"","url":"https://api.github.com/users/DavidRieman","html_url":"https://github.com/DavidRieman","followers_url":"https://api.github.com/users/DavidRieman/followers","following_url":"https://api.github.com/users/DavidRieman/following{/other_user}","gists_url":"https://api.github.com/users/DavidRieman/gists{/gist_id}","starred_url":"https://api.github.com/users/DavidRieman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DavidRieman/subscriptions","organizations_url":"https://api.github.com/users/DavidRieman/orgs","repos_url":"https://api.github.com/users/DavidRieman/repos","events_url":"https://api.github.com/users/DavidRieman/events{/privacy}","received_events_url":"https://api.github.com/users/DavidRieman/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-01-02T02:09:06Z","updated_at":"2019-01-02T02:09:06Z","closed_at":null,"author_association":"NONE","body":"## Description\r\nAdditional game pads are detected, but cannot be used.  The default configuration has one game pad controlling multiple players.  I don't know if this is specific to UWP yet.\r\n\r\n### Expected behavior\r\nDefault game pad bindings should be:\r\n* While one game pad is connected, it controls just player (port) 1.\r\n* While two game pads are connected, the first one controls player (port) 1, and the second one controls player (port) 2.\r\nRegardless of defaults, we should be able to reconfigure to have both game pads control separate game ports to successfully play any typical two player game.\r\n\r\n### Actual behavior\r\nWhen a second game pad is connected, we get the yellow \"XInput Controller (User 1) configured in port #X\". messaging for a bunch of ports in a row.  In a two-player game, the one game pad controls both players by default.  Upon navigating into the \"Input\" settings, I see User 2 Device Index is bound to \"XInput Controller (User 1) (#2)\" even when only one game pad is connected.  I can scroll through the (#2) part up to (#16) but I don't know what this means.  With the second game pad connected, we still cannot scroll to any entry containing anything like \"(User 2)\"\r\n\r\n### Steps to reproduce the bug\r\n1. Launch RetroArch UWP on Windows or Xbox One.\r\n2. Connect / activate a second game pad.\r\n3. Try to play a two player game.\r\n\r\n### Bisect Results\r\nDid not attempt to bisect, because the new UWP version is the only version that has ever successfully built for me.  The 1.7.5 (non-UWP) Windows version from installer does not exhibit this problem though; the second player's controller shows as an entry like \"XInput Controller (User 2)\" without the (#X) part.\r\n\r\n### Version/Commit\r\n541dc13d64f6d12697431196e00760a52edd141b and a sync from yesterday also exhibited the problem.\r\n\r\n### Environment information\r\n- OS: Windows 10 and Xbox One\r\n- Compiler: VS2017 defaults\r\n"}}
{"actor":{"display_login":"DavidRieman"}}