English Amiga Board Amiga Lore


Go Back   English Amiga Board > Support > support.WinUAE

 
 
Thread Tools
Old 24 August 2016, 09:40   #1
locvez
Registered User

 
Join Date: Aug 2016
Location: UK
Posts: 6
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
locvez is offline  
AdSense AdSense  
Old 24 August 2016, 10:52   #2
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 42
Posts: 19,560
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)
Toni Wilen is online now  
Old 24 August 2016, 13:47   #3
locvez
Registered User

 
Join Date: Aug 2016
Location: UK
Posts: 6
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
locvez is offline  
Old 24 August 2016, 14:00   #4
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 42
Posts: 19,560
Quote:
Originally Posted by locvez View Post
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..
Toni Wilen is online now  
Old 24 August 2016, 16:21   #5
Devlin
Sorcerian

Devlin's Avatar
 
Join Date: Nov 2005
Location: Bradford, UK
Age: 31
Posts: 224
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.
Devlin is offline  
Old 24 August 2016, 18:12   #6
locvez
Registered User

 
Join Date: Aug 2016
Location: UK
Posts: 6
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
Attached Files
File Type: txt winuaebootlog.txt (29.6 KB, 52 views)

Last edited by locvez; 24 August 2016 at 18:40. Reason: edit
locvez is offline  
Old 24 August 2016, 18:45   #7
locvez
Registered User

 
Join Date: Aug 2016
Location: UK
Posts: 6
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"
Attached Files
File Type: txt winuaebootlog.txt (12.9 KB, 49 views)
locvez is offline  
Old 24 August 2016, 18:54   #8
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 42
Posts: 19,560
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)
Toni Wilen is online now  
Old 24 August 2016, 19:11   #9
locvez
Registered User

 
Join Date: Aug 2016
Location: UK
Posts: 6
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

Last edited by locvez; 24 August 2016 at 20:19. Reason: more info
locvez is offline  
Old 25 August 2016, 13:21   #10
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 42
Posts: 19,560
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.
Toni Wilen is online now  
Old 25 August 2016, 17:34   #11
locvez
Registered User

 
Join Date: Aug 2016
Location: UK
Posts: 6
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!
locvez is offline  
Old 05 September 2016, 15:46   #12
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 42
Posts: 19,560
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.
Toni Wilen is online now  
Old 06 September 2016, 15:43   #13
mark_k
Registered User
 
Join Date: Aug 2004
Location:
Posts: 2,481
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.
mark_k is offline  
Old 06 September 2016, 15:52   #14
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 42
Posts: 19,560
AFAIK that fixed some buggy behavior where some games saw the pad twice or something like that.
Toni Wilen is online now  
Old 07 September 2016, 06:53   #15
MacMahoun
Registered User

 
Join Date: Sep 2016
Location: Wutoeschingen
Posts: 1
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.
MacMahoun is offline  
Old 07 September 2016, 12:38   #16
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 42
Posts: 19,560
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.
Toni Wilen is online now  
Old 18 September 2016, 11:27   #17
Michael Sykes
WinUAE end user

Michael Sykes's Avatar
 
Join Date: Jan 2014
Location: Bremen
Age: 38
Posts: 623
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...
Michael Sykes is offline  
Old 10 June 2017, 21:17   #18
PeterMac
Registered User

 
Join Date: Jun 2017
Location: W
Posts: 2
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 ?

Last edited by PeterMac; 10 June 2017 at 21:29.
PeterMac is offline  
Old 10 June 2017, 21:34   #19
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 42
Posts: 19,560
It was driver bug that was fixed in Windows 10 "Creators Update". (Affected rawinput mode which WinUAE uses)
Toni Wilen is online now  
Old 10 June 2017, 22:10   #20
PeterMac
Registered User

 
Join Date: Jun 2017
Location: W
Posts: 2
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

Last edited by PeterMac; 10 June 2017 at 23:07.
PeterMac is offline  
AdSense AdSense  
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
Xbox 360 controller problems kep support.WinUAE 16 11 June 2015 19:47
XBOX 360 controller disappointment Zak Retrogaming General Discussion 20 20 December 2013 15:07
PS3 / Xbox Controller question Girgl support.FS-UAE 2 25 November 2013 10:05
Problems with an XBox 360 Controller? JohnnyWalker support.WinUAE 7 25 June 2011 18:46
Xbox 1 controller Parsec Retrogaming General Discussion 4 18 January 2011 11:15

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 12:01.


Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
Page generated in 0.23800 seconds with 12 queries