#Xinput test controller not connected drivers
#Xinput test controller not connected Pc
#Xinput test controller not connected windows

'On Windows there are two joystick drivers, a DirectInput one and an Xinput one. On the joysticks page in the docs, it says: So now my remaining option, assuming I can't rely on the Steam Input fix to come soon, is to switch to 100% DirectInput. It turns out that Steam Input also doesn't support more than 4 XInput controllers, although there is supposed to be a fix in the works for this. I should perhaps add a note to the docs to mention this issue so that it doesn't surprise anyone else in future. The limit of 16 is something I can live with for now – later on I can look at giving players the option of using DirectInput for controllers. I have now implemented Steam Input and it mostly works, although sometimes controllers randomly disconnect for a few frames and then reconnect. But perhaps they do just use DirectInput. I initially assumed that other games or libraries must do something like what I suggested – detecting additional XInput controllers as DirectInput ones. It's now obvious why this happened, but I hadn't anticipated it or seen it before because although I own about 10 controllers, most of them are DirectInput only – I'd never tested with more than four controllers which supported both XInput and DirectInput. Shortly afterwards, my game (due to be released in 3 weeks) failed Steam's build review because their review team connected eight Xbox One controllers, but only four of them worked. I first realised something was not quite right when I was doing an online multiplayer test but only four remote players could use their controllers. This mode is a more plausible way of reaching 16 players, although it does require additional upload bandwidth for each connected client. There is also Steam Remote Play Together, which turns local multiplayer games into networked games by streaming the host's screen to the clients, and streaming their control inputs to the host – the host machine sees them as additional XInput or DirectInput controllers.

#Xinput test controller not connected Pc

It's unlikely that any players will connect more than 16 controllers to a PC (the most players I've had playing at once is 12), but it's nice to be able to advertise support for more. It's a Bomberman game, and there is a 'join screen' which shows every connected controller and which button you have to press to join the game with that controller. When I upgraded to Allegro 5, a side benefit was the ability to show actual button names. When my game was using Allegro 4, it was purely using DirectInput so there was no limit on the number of controllers. You're right, it probably is a bit of a niche request.

There's probably a reason you don't see many games supporting more than 16 players on a single PC. can't give you help, it would look like you need to rethink your game mechanics / decisions and decide what's most important. You haven't really explained what your game/product is actually trying to do, so I assume it's a quiz or other party game (or not a game at all).

#Xinput test controller not connected drivers

But I looked at Raw Input API and AFAICT, it doesn't support named buttons-the names are coming from drivers and the driver is likely interfacing at a higher level (ala Raw Input API never even sees it). You're really going to have to ask some Stack Overflow magician to see if there's some super-obscure hack or API that would let you do this. So far, what you're asking seems to be so niche its beyond what any one API provides.

How about 1) hard coding them for the most common controllers 2) allowing custom controller profiles if people NEED their weird controllers? That's basically what Allegro 5 does internally anyway. One thing I'm going to try is using the Steam Input API, bypassing Allegro for controller input.ĭirectInput does not allow accurate reporting of button names, which my game shows.

But in practice what I'm seeing is that four XInput controllers show up for the host, but after that clients can't connect any more controllers. It's supposed to emulate XInput controllers until all four slots are full, and then emulate DirectInput controllers for the rest. I don't currently have 4+ XInput controllers to test with, but I've experienced a similar issue using Steam Remote Play Together, which streams the host's screen to the clients, and their controller inputs to the host. What I would have thought should be happening is that the first four are recognised as XInput controllers, and the rest are recognised as DirectInput controllers. I am in the final stages of finishing my game, but it has just been reported to me that if eight Xbox One controllers are connected, only four of them can be used.