No particular error shows up in the logs, the 360 is detected but not initialized as a gamepad though. Nothing comes to mind on what's going on.
You may want to post in the Steamlink forums (https://steamcommunity.com/app/353380/discussions/0/) and post the link to your log there also. If any of the controller works by itself, then it's not a config issue and usually in situation like this I'd check if there's enough power for both the WiFi and USB at the time, but since they already work (simultaneously) outside Steamlink that can't be it.

While waiting I installed Recall box to try if it works. It's same there.

However... I found old Saitek Pad (PS2700) and it works like a charm. I decided to try xBox Controller via USB and it works like a charm.

Trying to connect via Bluetooth does not work at all. Will try to ssh and play with BT then, maybe console will tell me something.
Since I can't pair my headphones also, I think it might not be pad problem, but bluetooth.

About SteamController. There is problem with mapping of d-pad. It recognizes only swipe in one or 2 directions. Like Analog Left and Analog Up. So its more like Analogue for emulator than D-Pad.
But I think i can pass on stemController if XBox and Saitek works. I'm a fan of D-Pad. Touchpad as D-Pad is not good on SteamController.

... typos fixed above

@xboxwin said in [RetroPie x64] many many questions from beginners:

EDIT: I think I found. I have to change Analog to Digital and choose Left Analog

Yes, that's it.

To add to this I was able to get it connected again. It worked and I tested a couple games. I restarted the Pi and it would not work. If I shut down the pi and turn it back on, then turn the controller back on it connects. If I go to config to setup Joypad order it only shows '4' xbox controllers even though only 1 is connected. I shut down a couple more times like normal and booted up and controller connected. Now I shut down and boot the system back up and controller does not connect. Just blinks. When it does connect it will show player 1.

@DEWx

What would I need to do, to (re)install the xbox-controller using xboxdrv (while removing it first, incl. the other driver)

If you're talking about the Xpad driver, as long as you include --detach-kernel-driver in the xboxdrv launch command, the two drivers should be able to coexist without issue.

@alaindesjardins andreage 5 minutes ago

Hello! I've successfully connected my Xbox One Controller (model 1708) to my Pi3B via bluetooth, had to disable ERTM too. All buttons (including 'select') working. Using RetroPie 4.2

However, when I tried adding in my second Xbox One Controller (same model), It connected and mapped perfectly. When I tried configuring inputs in RetroArch, both controllers and USB keyboard stopped working.

I had to reboot and remove both controllers' BT connection and re-add the first one, it worked fine. Then tried and hooked up the second Xbox One Controller via USB to no avail. Tried it with a PS3 (via USB) worked fine.

Anybody know what's going on? What am I doing wrong?
Thanks!

@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)

I tried connecting the wireless adapter to the computer first with no luck on windows 10 and 7. I am returning the adapter and going with an xbox 360 wired controlled instead....

@herb_fargus I tried it but doesn't work: Pi3 stuck on rainbow screen after a kernel downgrade.

I had the same issue when I was using my upboard
Doing this

Hi peeps, first post on here after getting my Pi yesterday.

So, Xbox One S controllers eh, who knew they would be so much trouble? I've been tearing my hair out since yesterday, but found a solution to my issue, so hopefully someone else will find this post helpful!

It's been well documented that in order to pair or connect a modern Xbox One S controller (bluetooth) you have to disable the ertm option, and I'd had success when running this from the command line after boot up...

sudo bash -c 'echo 1 > /sys/module/bluetooth/parameters/disable_ertm'
cat /sys/module/bluetooth/parameters/disable_ertm
(the second command will return 'Y' when ertm is disabled, and 'N' when still enabled)

However I could not get it to persist using the suggested method i.e. adding it to /opt/retropie/configs/all/autostart.sh directly before the 'emulationstation #auto' line, so I would have to log in with puTTY and run the command manually every single time I wanted to use the Xbox controller! (super annoying).

So, happily I finally found another way to disable ertm for bluetooth.

Create a new file using nano...
sudo nano /etc/modprobe.d/bluetooth.conf

Add a single line to the new file...
options bluetooth disable_ertm=Y

Exit nano, saving the file in the process.

For reference, I'm using the latest release of Raspbian Stretch and RetroPie at time of going to press (December 2018), on a Pi 3 Model B+.

never mind, i changed it to a Q then solved it :-)