@mitu said in 2x different 360 Wireless controllers not mapping correct at same time:

so, yes, as far as the input system is concerned, they're the same type of device.

Think I'm going to rewire them - not too hard, the wiring harness has pins I can just pull out and shove into another spot - will just have to figure out what goes where and remember the original layout if I ever want to put it back lol. Thanks for the help though.

@dochartaigh said in 2x different 360 Wireless controllers not mapping correct at same time:

On a related note: is the USB controller device order no longer implemented in RetroPie anymore? Seems like the Xbox wireless adapter is superseding anything physically plugged in on a lower USB port number, or maybe I have to reboot and test that again? (i.e. not hot swappable? - I forget if it ever was TBH).

And yes, I'm quoting myself and looking for confirmation on this. Seems like on the RP3 when all 4x USB's were 2.0, the order was something like left bottom 0, top 1, right side bottom 2, top 3.

On the RP4, I think (NOT positive, would like confirmation if possible), they run separately for the USB 2.0 side and the USB 3.0 side. I had my WIRED fightstick plugged into the left side #1, which should have superceeded the 3x WIRELESS fightsticks which were plugged into #2, but I think because the wireless was on the 3.0 side that superceeded the 2.0 side in controller order. Right now I have the wired fightstick plugged into the right side top, and the wireless 360 dongle on right side bottom and the wired one is player #1, and the wireless are #2/3/4. can anybody confirm this is how it works now on a RP4?

@owl-degree said in Initial install - Xbox 360 Wireless Analog sticks:

However, the right stick > left movement does not register. Should I simply presume it's broken?

I don't think so, try several times to register it, without pressing too hard on the joystick - just nudge it to the left.

@daveybones Update the RetroPie script and then re-install the xpad driver, it should work now.

@tgilly If you'd like to diagnose the problem, then you'd have to provide the necessary info. No, I don't think 4.4 is unstable, but your problems look like a power supply problem, the system throttling itself down automatically, or more related to the fact that your ROM folder is mounted over the network.
Check if your power supply is right up to the specs and then try running the ROMs from the sd card for a test to see if you get the same symptoms.

Thanks for trying to help anyway herb..appreciated...i had a google and found a few similar posts around so i think i'll go back to the wired 360 controllers for now.

@herb_fargus
Thanks a lot. Solved

@mnmagri

I'm not sure how far you got when setting up Moonlight but you need to find your controller's ID number and the correct corresponding button numbers by using jstest /dev/input/js0

Then you add this information into /usr/share/moonlight/gamecontrollerdb.txt

This is because Moonlight decided to use an SDL gamecontrollerdb.txt format to be able to make common game controllers work out-of-the-box. Here's the official template file:
https://github.com/irtimmer/moonlight-embedded/blob/master/gamecontrollerdb.txt

Here is the information for my wireless Xbox 360 controller. Warning: my d-pad settings are not correct and I've been meaning to fix this but I'm too lazy to do it right now!. They differ a little depending if you're using the Xpad driver or the Xboxdrv driver.

Xpad version:

030000005e040000a102000007010000,X360 Wireless Controller,a:b0,b:b1,x:b2,y:b3,leftshoulder:b4,rightshoulder:b5,lefttrigger:b6,righttrigger:b7,back:b8,start:b9,guide:b10,leftstick:b11,rightstick:b12,dpleft:b13,dpright:b14,dpup:b15,dpdown:b16,leftx:a0,lefty:a1,rightx:a2,righty:a3,platform:Linux,

Xboxdrv version:

030000005e040000a102000007010000,X360 Wireless Controller,a:b0,b:b1,back:b6,dpdown:b14,dpleft:b11,dpright:b12,dpup:b13,guide:b8,leftshoulder:b4,leftstick:b9,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b10,righttrigger:a5,rightx:a3,righty:a4,start:b7,x:b2,y:b3,platform:Linux,

More information here (Xbox 360 Wireless Receiver mapping chart):
https://github.com/irtimmer/moonlight-embedded/issues/514#issuecomment-310163270

Hey Poltro,

I just created the script to make things easier to install and setup Moonlight-Embedded. I have just updated this script today BTW to include a new menu based structure for an even easier solution. In regards to the controller mapping, this is now all stored in a txt file within the Moonlight program. It's called gamecontrollerdb.txt and contains the mapping for over 100 different gamepads. Here's what I could see in that file:

xwc,X360 Wireless Controller,a:b0,b:b1,back:b6,dpdown:b14,dpleft:b11,dpright:b12,dpup:b13,guide:b8,leftshoulder:b4,leftstick:b9,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b10,righttrigger:a5,rightx:a3,righty:a4,start:b7,x:b2,y:b3,

AND

030000005e0400009102000007010000,X360 Wireless Controller,a:b0,b:b1,y:b3,x:b2,start:b7,guide:b8,back:b6,leftstick:b9,rightstick:b10,leftshoulder:b4,rightshoulder:b5,dpup:b13,dpleft:b11,dpdown:b14,dpright:b12,leftx:a0,lefty:a1,rightx:a3,righty:a4,lefttrigger:a2,righttrigger:a5,platform:Linux,

If Right Trigger is Start, try changing righttrigger:a5 to righttrigger:b7 and start:b7 to start:a5

Let me know if that fixes it here and also, let everyone know what model your controller is and the model of the receiver as that may offer some clues as to why your mapping is different :)

Latest Video is here btw :

lt.jpg" alt=" " class=" img-fluid img-markdown" />

@matamualomia also try

"button(6), button(7)“ or
"button(6)/button(7)“

Attempted to do a little more troubleshooting tonight. I'm still mystified as to what's going on, but at least now I have a better understanding of the problem.

After a little trial and error, I realized that InputAutoCfg.ini writes to mupen64plus.cfg, so anything I put in the former will overwrite the controller values in the latter. Thinking that perhaps whatever issue I was having was specific to Super Smash Brothers, I loaded up GoldenEye 64 also using Mupen64plus-gles2 emulator, and voila(!) the game seemed to be respecting my dead zone values. I had set them to essentially be maxed out, and sure enough I couldn't move the in-game cursor without moving the left joystick to the far edges of its range. I had similar results when I tried Mario Kart 64. I confirmed that I was seeing motion when a joystick value exceeded my deadzone threshold as displayed by jstest.

So I guess now the question becomes, why is Super Smash Brothers ignoring my dead zone settings, but the other two ROMs aren't? Oddly enough, there were a few times when I loaded up Super Smash Brothers and it DID seem to respect the dead zone settings--I had to move the joystick to an extreme to cycle through menu options--but there was no way I consistently get to exhibit this behavior. Is there a config file or something similar that's overriding whatever settings I'm specifying in the InputAutoCfg.ini and mupen64plus.cfg?

I know this is an old topic but I was reading it just before I tried out the xboxdrv from https://github.com/zerojay/xboxdrv/ and I thought I'd just let you know... having built and tested it all you have to do is launch xboxdrv with the --chatpad option and it works perfectly.

I don't use retropie so I don't know where you need to make this change, but that is all that is required. My main annoyance with it is that I can't find a tab key... but it works well, I'm writing this post with it on my laptop.

no worries i figured the dongles might be 'fighting' for priority as i beleave the dongles set the controller position before then sending it to the system itself therfore 2 dongles would mean 2 controllers trying to control P1 probly a more descriptive reason for this somewhere but i guess thats what is basicly happening there glad your sorted

@nilsholgersson pcsx-rearmed is known to have a lot of compatibility issues, being fast enough on arm processor came at a cost... and don't expect fixes for this, notaz (the main developper) has been quite inactive for years.
Your best bet is to use either the original hardware or a more accurate emulator (i would recommend beetle-psx-libretro) on a hardware more powerfull than the pi (i would say something with a cpu as close as possible to 3Ghz)

Yes there seems to be differences with these cheap china dongles. Well, I got refunded all money for the dongle and did not have to return it. Will order Micro$oft genuine one next. But, if somebody has tips how can i get that cheap dongle working, i am open for suggestions. Thanks backstander for the help earlier :)

So, that cheap dongle has something wrong with it, win10 does not make the usb connection sound and is not recoqnized with device manager. But, light is lit and blinking when button is pressed. Also, RPi does not show it in lsusb list.

Check the retroarch.cfg files of faulty emulators : https://github.com/retropie/retropie-setup/wiki/retroarch-configuration .

I am also having a similar problem. You're suppose to remap it by using jstest in terminal. It will allow you to see the number the buttons are assigned to which then you assign to in the snes9x.cfg file. I have gotten to this part but nothing has changed for me. Clicking start will still exit the game for me so it's kind of frustrating. I'm using snes9x since Pisnes won't even run at all.

@yari the output of lsusb on mine is

Bus 001 Device 004: ID 045e:0291 Microsoft Corp. Xbox 360 Wireless Receiver for Windows

I'm not really sure how to troubleshoot proprietary wireless connections though