Windows 10 blue tooth controllers not seen, wired controller works.

[dabone]

I'm setting up a simple am setup with windows, but it doesn't take any input from my bluetooth controllers.
The controllers are setup and working fine with retroarch, and windows sees them correctly. But when I try to map an input using them in am, it never sees the input.

Controller 0 and 1 are bluetooth, controller 2 is a wired logitech.

When I map a button with the wired controller, it is seen as Joy2.

Any clues?

Thanks.

[dabone]

Ok, I've built a different machine and same thing.
Single controller attached, it's a red samurai controller from gamestop.
Works fine under retroarch, and the windows game properties, but attractmode doesn't see anything from it.

When I got to controls and try to define anything, it never sees any input from that controller.

Is this a know bug, or a new one with the windows build?

Thanks.

[dabone]

And once more, I have been using windows 10, so I loaded windows 7, and got the same results...

Controller works anywhere but attract mode.
Is there a verbose logging mode to see what controllers it detects on startup?

Thanks.

[verion]

And just to be sure - when you are in AM settings (controls section) can you map your joystick keys for any functions or not?

[dabone]

And just to be sure - when you are in AM settings (controls section) can you map your joystick keys for any functions or not?

No, when I'm trying to add a input in settings, it never sees the input from the bluetooth controllers.
I can plug in a wired one, and I can map those all day, and adding keyboard inputs work, it's just not seeing the bluetooth ones.

The controllers show up under windows control panel just fine, and work in retroarch just fine.
Just for fun I also tried the html5gamepad.com, and it also sees them.

[dabone]

Ok, looking more into this, I tracked down another joystick tester based on the SFML library. It doesn't see the bluetooth controllers either.

http://fluxrobotics.blogspot.com/2012/06/joystick-test-application-qt-sfml.html

So it's a SFML issues, not attract mode.