Has anyone found a fix for two wireless Xbox controllers on Retroarch beta/nightly?

[keltoigael]

Currently on 1.0.0.2 Stable release you can use two wireless xbox controllers and map either of them perfectly fine. On the beta and nightly releases you can only map one. Either wireless controller will over map the existing controller, so basically player 1 and player 2 switch off back and forth. Any gurus here find a way around this yet? I know I know, beta yatta yatta but a lot of guys here are using it in their current set up for the PSP and Atari cores support versus Stable release lacking those.

[marxkemp]

If you go through the menus with a keyboard.. then hit x on binding the user 1 controller. Bind the buttons. Then go to the user 2 controller with the keyboard. Hit X again and start binding your 2nd controller.

Hope above makes some sence. Orelse just do it in the cfg file by hand.

[keltoigael]

If you go through the menus with a keyboard.. then hit x on binding the user 1 controller. Bind the buttons. Then go to the user 2 controller with the keyboard. Hit X again and start binding your 2nd controller.

Hope above makes some sence. Orelse just do it in the cfg file by hand.

That's not the issue, the issue is that the Xbox wireless receiver/controller is showing up for both player 1 and player 2 as the same controller rather then two distinctive controllers. I have done the manual way and it still over rides one another.

[marxkemp]

Ah. I could change it with the keyboard and manual way to the second controller. Worked fine with the nightlies i tried.

[keltoigael]

Ah. I could change it with the keyboard and manual way to the second controller. Worked fine with the nightlies i tried.

I will give it another go, if it fails again I will try to grab some screens of the issue.

[marxkemp]

Well thats how i solved it. Maybe turn autoconfig of when you cant select user 2

[keltoigael]

Well thats how i solved it. Maybe turn autoconfig of when you cant select user 2

Thanks will look into later this evening. Kudos.

[Trnzaddict]

That's not the issue, the issue is that the Xbox wireless receiver/controller is showing up for both player 1 and player 2 as the same controller rather then two distinctive controllers. I have done the manual way and it still over rides one another.

I feel your pain. When I built my htpc last year I ran into this issue. Are you running the latest 360 drivers?

Iirc once I updated my drivers they started showing up as separate in Windows 8.1.

[keltoigael]

I feel your pain. When I built my htpc last year I ran into this issue. Are you running the latest 360 drivers?

Iirc once I updated my drivers they started showing up as separate in Windows 8.1.

I am still using Windows 7 x64, as far as I know I have the latest drivers for the wireless 360 controllers.

[keltoigael]

Well, I got the buttons mapped seperately now, so thats a plus. Both D pads are still married. Player one up looks like h0up, player two looks like h1up. Player one input device=0. player two input device=1, grrr I cant figure out what it is.

[keltoigael]

Finally! I figured it out, player two also needed to be h0up, etc. My Xpadder for some reason cloned my player 1 profile over to player 2 when ever the second controller connected. The D pad arrow keys was causing a D pad marriage making it impossible to control. I made a new blank profile for player 2, which I will do for 3 and 4 as well. Everything is mapped and working now!

[fissionch1ps]

Been following this thread for some time. Setting up an Alienware alpha with a Kodi front end to launch steam, hyperspin and some various other programs.

I use wireless 360 controllers in my steam games without a problem but have been getting the following issues in hyperspin, rocketlauncher and retroarch:

One wireless controller works well. Two wired controllers work. Two wireless controllers cause chaos.

Hyperspin: becomes uncontrollable via the 360 controller. The second controller takes control.

Retroarch cannot play two player games. Second controller retains control. First controller doesn't work.

Any forward motion on these issues since September? Any advice on getting two wireless 360 pads working?

[fissionch1ps]

A follow up after digging some more. Roms work fine when launched directly through retroarch. The damage is being done somewhere in the hyperspin/rocketlauncher mess. Any thoughts?

[fissionch1ps]

So... When launching a game through retroarch, it will initialize my wireless 360 controllers through Xinput, no problem. Rocketlauncher, when looking at preferred controllers, only shows the wireless receiver.

So, first, sorry for all the posts. Second, is there a cfg ninja here that can help me allow retroarch to interface raw with my xbox 360 game pads, but maintain the esc exit back to hyperspin?

[grantoswisey]

I remember having a similar problem with wireless Xbox pads in retroarch,try binding player 1 controls then set player 2 and then set player 1 again I think that's how I did it but give it a try