Hacker News Reader

Comment by lsaferite | Hacker News Reader

Windows supports Generic HID game controllers with 8 axis and 128 buttons already. And a few hat switches. And if your devices needs more than that, you can enumerate as multiple devices if needed. Not sure if there is a HID type for rumble support though. So, there's no reason a Steam Controller couldn't operate without a special driver. Some functionality may require custom software to support though. I have several Virpil controls and the entire setup will function as a simple set of generic HID devices. The only special bit is some software you can optionally run to control advance per-application remapping. I don't have a Steam Controller, so I have no idea if it can show up as a generic HID controller or not.

View on HN

2 thumbsticks is already 4 axes. Add 2 triggers and it's 6 axes. Add gyroscope and it's 9 axes. That's more than 8. And I haven't mentioned the touchpads.

> you can enumerate as multiple devices if needed

A single physical USB device can enumerate as multiple virtual devices. This lets you easily side-step the limits *if* the game supports input from multiple controllers at the same time. The games I use controllers for allow you to map to multiple controllers, mouse, and keyboard, all at once. The touchpad could simply enumerate as a HID Touchpad. Apparently Windows already has a Touchpad Haptic HID Profile even.

Honestly, if Valve is making you require Steam to fully use the Steam Controller, that's disappointing because, as far as I can tell, nothing it's doing can't be accessed via HID usage.

It's a bit more tricky, a Generic HID just gives you a DirectInput device, while reasonably modern games use Xinput. Microsoft never provided a way to map DirectInput devices to Xinput. For Xinput to work a Microsoft specific USB protocol is needed, not a Generic HID device. Many third party controllers have a switch or button combination to switch between XInput and DirectInput modes for this reason.

Microsoft has a new API with GameInput that addresses this situation and allows mapping Generic HID devices onto game controller via config file, but it doesn't work retroactively, it only works for games that use the new GameInput API.

Valve could of course provide a way to switch and emulate other protocols too, just like other third party vendors do, but there is no USB standard that makes things "just work" in Windows when it comes to gamepads, you always need extra drivers, USB modes or other hacks.

On consoles the situation is even worse, modern consoles deliberately lock out any unlicensed third party controller. Playstation3 was the first and last console that supported standard USB controller, while PS5 doesn't even support PS4 controller.

Just out of curiosity, what modern game won't function with a generic HID game controller?

Most of them I would assume. Everything from 2006 forward started to use Xinput. DirectInput support only shows up in racing sims, flight simulators, fighting games and emulation. But all the big AAA games have been built around Xbox360 style control schemes for two decades.

But it's all a bit theoretical, since most modern gamepads have Xinput support, and the generic HID devices are mostly flightsticks or SNES-style gamepads that wouldn't have enough buttons and axis for modern games in the first place. Another issue is that most games don't offer input remapping for gamepads.

But with SteamInput and homebrew tools like x360ce there are many ways to make generic USB devices compatible Xinput, so it's not like you can't use them. It's just not something that works out of the box.

That may explain it then. I use flight controllers and driving controllers. Both just show up as generic HID devices and both are easily used in the games I play.

Reply on news.ycombinator.com