XBOX One S Bluetooth on Mac, non working triggers.

[Dragon]

ISSUE
Can't map triggers in steam big picture with a fully firmware updated XBOX One controller connected via Bluetooth to Mac.

OS
macOS 10.12.1

STEPS
Connect XBOX One Wireless controller via bluetooth.
Open big picture and select controller config.
Try to map all controls

EXPECTED
Triggers to map correctly.


A clue seems to be that 'joystick and gamepad tester' app shows the triggers as 'simulation usage' with smaller axis range than the sticks, so they're presumably being mapped to some sort of control input that steam is not reading.

[Hovercross]

Having the same issue on MacOS 10.12.2; both beta and non-beta Steam clients. XBox One controller works perfectly when connected via USB.

[Fiendmish]

I'm seeing the same issue

[Dragon]

Kind of annoying seeing xbox pad mapping support added in latest beta, but nothing changed on this..

[fknfilewalker]

Same probleme here, I think it's because RT LT are Analog. Shouldn't be that hard to fix because "Joystick Doctor" recognizes them without a problem.

[Dragon]

It's because they're mapped differently in the bluetooth HID to regular analog triggers, and steam isn't recognising the input category.

[UlteriorCone38]

Very sad that this has not been resolved yet... :( I just got one of these, and it worked out of the box on the Mac with Steam but Windows 10 needed the firmware updated. Now the triggers don't work. {SIGH}

I can't find a way to downgrade the firmware, but the real answer is for Steam to support the new configuration as Microsoft probably isn't going backwards.

[UlteriorCone38]

For what it is worth, I went to this page:

http://html5gamepad.com/

And the results for the updated XBox One S Bluetooth controller are:

45e-2fd-Xbox Wireless Controller

Left stick:	L<-->R  Axis 0  -1 to 1
		U<-->D  Axis 1  -1 to 1
		Click	B14	0/1

Right stick:	L<-->R  Axis 2  -1 to 1
		U<-->D  Axis 3  -1 to 1
		Click	B15	0/1

Xbox:			B0	0/1
Start:			B16	0/1
Select:			B12	0/1
A:			B1	0/1
B:			B2	0/1
X:			B4	0/1
Y:			B5	0/1

DPad:		Up	B19	0/1
		Down	B20	0/1
		Left	B21	0/1
		Right	B22	0/1

Bumper:		Left	B7	0/1
		Right	B8	0/1

Trigger:	Left	B17	0 to 1
		Right	B18	0 to 1

[Dragon]

for me html5 on chrome is giving odd axis mappings, and start/guide button not working at all.


eg triggers are axis 3 and 4, right stick is axis 2 and 5



edit: just grabbed chrome beta, and axes are correctly mapped there.

[UlteriorCone38]

I saw bug reports on Chrome about that, glad they are fixing it. I used Firefox as it wasn't working in Safari when I first tested it.

[Dragon]

Safari doesn't have support for controllers as yet, so it wouldn't.



the technical preview is supposed to, though doesn't seem to be working for me currently, but it was working before I think. ( mapped incorrectly )

[KUICHANISM]

I have the same issue.
I also experienced this issue after update xbo controller firmware.
And, when i test controller input with "joystick doctor", it can recognize trigger signal but name of trigger signal is expressed as "unknown 1" & "unknown 2".

[UlteriorCone38]

More information....

While the Firefox test above worked and showed them as analog buttons 17 and 18, the "Enjoyable" mapper did not see them, "Joystick Doctor" shows them as "Unknown 1" and "Unknown 2". "Joystick Mapper" does not find them on a scan. The above HTML test on Chrome shows them as B6 and B7. so clearly there is some wild inconsistencies going on. :( :( :(

[Dragon]

I believe the ramappings were made to be more android compatible.. evidently android has odd ideas compared to mac of how mappings are done.

[UlteriorCone38]

Saw a mention in the beta I just downloaded today about fixes for controller mappings, but seems to have no effect on this problem... :(

[BobDeBouwer]

I'm having the exact same problem. opened a topic on this myself last week hoping they would fix this but so far no luck
Wish there was a fix for this