Follow-up: I did some more digging and read somewhere on the xpadneo github that they have a hypseus module in the code. I never thought to try hypseus, I guess I had it stuck in my mind that Daphne was "the" laserdisc emulator. I installed hypseus and it works with the Xbone controller. I only had to configure the select and start buttons. The exit as configured in ES (start + select) works as well. In Daphne the start+select to exit didn't work and I had to configure another button.

Big props to @DirtBagXon, I found your github and followed the instructions: https://github.com/DirtBagXon/hypseus-singe. Thank you thank you thank you.

I hope this helps anyone else stumbling into this issue. I like my xbone controllers and am trying to get away from Xbox 360 controllers + dongle.

TLDR: Xbox One controllers will not work with Daphne. Use hypseus.

@Wlcina Yes, the xpadneo driver installation already does that, that's why I recommended installing it.

@mitu Thank you for your quick response !

I forgot to mention before, when first posting i had installed xboxdrv, xpadneo and xpad.

I have uninstalled xboxdrv, restarted, and tried to connect with xpadneo and xpad installed. Only 2 of them worked (same result as before)

After this i had uninstalled xpadneo and xpad -> then installed xpadneo only -> restarted -> try connection -> still same result.

@mitu

This fixed the issue. I was under the false impression that a clean install from an imaged I downloaded would be the latest version.

Thank you for your help.

@w0nderw0rm You can map the dpad to the left joystick in retroarch options. Also if you use LR-MAME2003, there is an option in that emulator to map the face buttons to the right joystick for games like Smash TV and Total carnage. I think it's on by defualt.

@cagancelik88 Please add more info about your system, as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

Did you install any additional drivers (xboxdrv maybe) ? For the S models, you should install the xpadneo driver from https://github.com/atar-axis/xpadneo, it should work better with the newer Xbox controller models.

Thanks for the info.

THX!
It looks like there was a hidden sign (copy and paste failure)

I remember a topic a month ago with a similar problem - the pairing of Xbox controllers worked, but they acted as a single controller. The solution was to install an alternate driver for the controller - xpadneo (https://github.com/atar-axis/xpadneo).
If you want to give it a try, the installation is quite easy:

Remove any Bluetooth controller from the RetroPie script Bluetooth configuration. Remove the xpad driver from the RetroPie setup script, from the drivers package section. Install xpadneo (run this from the SSH session): git clone https://github.com/atar-axis/xpadneo.git cd xpadneo sudo ./install Reboot and then redo the Bluetooth pairing for the controllers.

See if you get 3 devices (/dev/input/event[0-2]) and Emulationstation detects all your controllers after the installation.

@liquidchild101 can't find much about xow online so thought I'd ask in here, do you find the adapter gets crazy hot

I did what you said and now it works just fine! Thanks!

@mitu
Actually, I think I did update it and that caused some of the issues again with it not working properly. It's working well enough as is so I'm a little leery of messing with it at this point. I don't have any games that require thumbstick or trigger input so I'm happy enough with the good D-pad.

Circling back around to this post after a bit just to update anyone who may be having the same issue that I was and put some finality to the issue. The issue was with the Xbox One Bluetooth controller having some driver compatibility issues. I believe the solution is still a WIP, but atar-axis wrote a driver called xpadneo that works amazingly well with Xbox One in Bluetooth mode. It solved all of my controller issues. Jstest now shows the dev input perfectly, and includes rumble support. Really great stuff!

So... doesnt matter. i use now my gaming latop and emulationstation...

yes the controller was updated with win10 and ertm is disabled - the conroller works in emulation station perfectly - inclusive the "select" button and the "round x box one" button. But in the retroarch GUI it does not work any longer.

Well, I don't think that this issue's gonna get fixed but because I was impatient I decided to flash regular Raspbian and I think that I'm gonna just dual-boot Lakka (Since it uses more of RetroArch functions natively).

I know this post is a couple months old, but I've just set up moonlight today on my Retro-Pie setup, using the same controller, and ran into a similar (if not the same) issue... But I managed to come up with a solution which (I think) will hopefully help others.

Long story short, I replaced the line matching the controller's ID (030000005e040000dd02000003020000) in /usr/share/moonlight/gamecontrollerdb.txt with this:

030000005e040000dd02000003020000,Microsoft X-Box One pad (Firmware 2015),platform:Linux,x:b2,a:b0,b:b1,y:b3,back:b8,guide:b10,start:b9,dpleft:h0.8,dpdown:h0.4,dpright:h0.2,dpup:h0.1,leftshoulder:b4,lefttrigger:b6,rightshoulder:b5,righttrigger:b7,leftstick:b11,rightstick:b12,leftx:a0,lefty:a1,rightx:a2,righty:a3,

When I start moonlight it outputs an error about the config not being correct now, but it actually works (button mappings matched what Steam/games wanted, with no manual config necessary within steam or games).

I came up with this mapping by running the SDL "controllermap" utility. I compiled it using the steps laid out here

Now it's very possible I did something wrong, but when I ran controllermap, all I got was a blank screen (apparently you're supposed to see prompts asking you to assign/map buttons, but I never saw this). The first time I ran it I just mashed buttons until it exited. What this accomplished was it allowed me to get an idea of what order it took the inputs (based on the order it output them in the configuration string that was output when controllermap exited. Then, using this order as a reference, I ran controllermap again I pressed the buttons/joysticks in the order seen in the configuration string. This time controllermap output the string I included above. Then, as I said, I replaced the existing mapping in moonlight's config file. Then I rebooted (probably unnecessary) and launched moonlight again, and my controller was working.