Razer Atrox Arcade Stick (Xbox One) and trigger "buttons"

[Blodia]

Hi everyone!

I'm quite new to MiSTer, but what I've been able to discover/do so far has been nothing short of terrific. I seem to have hit a small snag when trying to define my arcade joystick (Razer Atrox Xbox One version) and the RT/LT trigger buttons. They just won't register when I try to define them in MiSTer. All the other buttons and joystick work, just those two buttons (RT/LT) don't register. I know they actually work because when I hook it up to my Xbox One, it works.

I know this controller also has issues with PC, where those same two buttons wont work either, unless you redefine the controller as an Xbox 360 controller.

I'm wondering if there's a workaround in place for this? Perhaps I'm missing something quite obvious.. I also see that in the xpad.c source code, that this arcade stick is defined.

{ 0x1532, 0x0a00, "Razer Atrox Arcade Stick", MAP_TRIGGERS_TO_BUTTONS, XTYPE_XBOXONE },

Any ideas?

Controller in question:
https://www.razer.com/console-controlle ... 50100-R3U1

[Sorgelig]

That's probably these buttons generate keyboard codes which is not compatible with MiSTer. I don't know what's the reason behind it. Probably it can be fixed in driver since it already knows this controller. May be someone with this controller and ability to develop in Linux can check if possible to fix.

[Mellified]

I own two of the Razer Atrox Xbox One sticks. The issue you're seeing is due to a hardware difference with the Atrox. Apparently Microsoft decided they wanted an alternate for LT/RT with a range of 0-1 instead of the standard triggers with 0-255. Unfortunately Microsoft didn't enforce this generally so only the Atrox Xbox One and Madcatz TE2 Xbox One arcade sticks use the "correct" standard. Also, support was also never ported to Windows 10 except for UWP apps. This is discussed in more detail here and here.

Sadly supporting this stick's triggers is very special case. Given Microsoft doesn't even support it properly in Windows 10 I'm not sure it is worth the trouble.