Xbox One S - Bluetooth Controller Issue

Hi all,

I have been using WinUAE with a 360 controller for a while now with absolutely no issues whatsoever but I recently picked up an Xbox One S Bluetooth controller, I have it setup in windows ok, it works with my frontend, BigBox and Launchbox ok but I can't seem to get it to work with WinUAE.

the device is listed in the game controller section as "microsoft bluetooth controller" but when it is assigned to a port and I run the test/remap it doesn't pick up the controller input.

I am using the latest 3.3.0 from the installer on winuae.net

Any advice or suggestions?

Many thanks

[Toni Wilen]

I don't have one, at least not yet. (Don't seem to be available here yet. "Normal" non-S wireless Xbox One controller works)

Attach winuaebootlog.txt. (Check Paths panel for location of the log file)

Assuming you have Win 10 v1607, it also could be some controller weirdness that was introduced in 1607 causing S controllers (New bluetooth only?) to be detected twice. (XInput and DirectInput or something like that)

Thanks for the quick reply Toni,

Will attach the logs when I get back home, will also try a fresh install of win10 in case it was the anniversary update that screwed it up

[Toni Wilen]

Originally Posted by locvez

will also try a fresh install of win10 in case it was the anniversary update that screwed it up

Don't bother. Anniversary update (1607) is required for using XBox One S with bluetooth..

[Devlin]

try plugging it in via USB, and running the "Xbox Accessories" app and making sure the controller firmware (what? yes i know >.>) is up to date. Most Xbone pads won't work in windows wirelessly without up-to-date firmware.

log attached, still to try connected via usb, trying that shortly

edit - wired via usb fails to detect gamepad in WinUAE, displays in windows not in WinUAE

edit2 - Disconnecting the USB N64 adapter allowed the xbox one controller to be detected when plugged in wired

edit3 - Disconnecting the USB N64 adapter allowed the xbox one controller to be detected wirelessly via bluetooth...interesting, plugging the usb N64 adapter in makes it vanish from the drop down

Here is the log after disconnecting the usb N64 controller, you can see the xbox one controller is detected as "bluetooth XINPUT compatible input device"

[Toni Wilen]

Log looks fine.

Does anything change if you run winuae with -norawhid command line parameter? (actually run with -log -norawhid and check if anything strange appears in the log window when you try test/remap options)

get a lot of this in the log with -log -norawhid when both USB N64 controller and Xbox bluetooth controller connected, only when test/remap is selected.

interestingly picks up both controllers now

RAWHID unknown input handle 00020041
RAWHID unknown input handle 00020049

If i disconnect N64 adapter the above no longer appear.

Also, running WinUAE without the -norawhid switch prevents the bluetooth controller being detected when usb n64 controller is connected

[Toni Wilen]

That log message is harmless (I think I forgot to disable it..), it only means winuae got rawinput messages from device that was not enabled in winuae.

It looks like I need to add XINPUT support for devices that are not HID devices.

Sweet, thanks very much Toni, I appreciate the quick response and help to get up and running. It's very interesting that having a USB device connected stops the bluetooth controller from being detected without the -norawhid switch.

I've added the switch to my frontend launcher for now and all games work perfectly!

[Toni Wilen]

I have the pad now and I can confirm that it does not work with rawinput, which is weird because rawinput enumeration detects the device but there is no events..

I also remembered why I haven't implemented xinput support: it is too simple API, there is no way to detect between two (or more) identical xinput devices.

-> There is no way to map device to device's custom input config.

[mark_k]

Probably won't help but the changelog for the August 31 cumulative update for Windows 10 1607 (KB3176938, OS build 14393.105) mentions this:

Improved compatibility of using Xbox One controllers with various games.

[Toni Wilen]

AFAIK that fixed some buggy behavior where some games saw the pad twice or something like that.

Just wanted to let you know, that my two wireless connected standard xbox one controllers suddenly stopped working. They are still present in configuration but no inputs were recognized. This is on Windows 10 64bit. I have a feeling it has to do with last windows updates. Other emulators i tested still work fine.

[Toni Wilen]

I haven't tried "normal" xbox 360/one pads recently but this sounds similar to rawinput bugs during Windows 10 "redstone" insider builds.

It was very common that hid rawinput didn't work, sometimes it worked, sometimes it didn't, sometimes it worked once (run winuae after reboot: works, quit winuae, run again: nothing..) and only way to make it work again was reboot.. Device emumeration always worked, but no WM_INPUT messages.

Mouse/keyboard rawinput always worked fine, rarely used generic hid rawinput did not.

[Michael Sykes]

I wanted to get rid of the darn cable on my old 360 pad,
so I bought the new white S version yesterday.

Saved me 5 €uros compared to the old wireless version, wich needes a dongle.
Now I have to suffer for my stinginess...

EDIT: S - because it suxx...

Same problem with Xbox One S controller via Bluetooth but only on my Dell Venue 8 Pro tablet with Win10 Anniversary Update 32bit, on my desktop PC with same system but 64bit version controller work fine, why ?

[Toni Wilen]

It was driver bug that was fixed in Windows 10 "Creators Update". (Affected rawinput mode which WinUAE uses)

thank you for information, so only solution is update system to Creators Update ? maybe someone can share this driver for 32bit system, would be great.

Edit:
I added to launch file " -norawhid" and work perfect it's detected as Xinput Bluetooth controller, now I can play on my Dell Venue 8 Pro tablet