There are definitely ways to send backwards compatible data when required and separately support additional features in a new iteration of an API. This wouldn’t be in the top 10 backwards compatibility challenges MS has figured out.

But in any case, I don’t care if they call it XInput2 or Game Input. I just need it to support all controller features in all games. It’s a bit hard to tell whether Game Input will ever do that, but so far it seems more concerned with acting as a layer to explicitly support a bunch of different hardware, each with its own standards, than a XInput replacement for controllers. There doesn’t seem to be a concept for a “Game Input controller” there at all, actually, just supported controllers you can listen for regardless of what they’re sending through.

I guess over time if they stick with it and it does end up working as a Steam Input-style intermediary layer that just recognizes anything you’d just ship controllers that match whatever format with gyro support and Game Input-enabled games would just pick them up fine more or less universally, but that doesn’t seem to be what it does right now, or at least not something that either games or manufacturers are relying upon.

Anyway, this was interesting and informative, but I think I’m good now. I definitely don’t want to have a conversation formatted as an argument in which nobody is disagreeing with anybody else. Those are exhausting.