So, I’m wondering about that old Driver’s Education software. Now I’m
thinking this through a second time. So, it’s not using the modern
DirectInput APIs? Surely, then, since it’s worked with game port
controllers of times past, it must be somewhat similar to the parallel
port on old PCs. For Windows XP, there exists a parallel port
emulator driver that you can use to get the same direct I/O functions
you’d normally get from a parallel port in hardware. So, it must be
similar, then, with the game port. Right?
Yeah, maybe, but you’ll have to be searching a lot harder for such a
solution, keeping in mind that game port programming is a lot less
popular with the technically skilled people who publish on the
Internet.
Failed search.
20180909/DuckDuckGo directinput gameport usb emulation legacy
No, no, no. You’ve been misguided here. The picture is much more
bleak. DirectInput you ask? Well, Microsoft basically killed off all
of the sophistication and elegance that you remember from that API of
times past. What happened? After the Xbox sales really took off,
Microsoft basically lost interest in the diverse market of third party
gaming hardware. Yep, all of it. Why should they care if they can
get most of their revenue from their own Xbox hardware sales? So, the
issue at hand here is that DirectInput has been “deprecated” in favor
of “XInput.” Unfortunately, XInput doesn’t even technically match
with DirectInput! It’s not, in fact, a real replacement. DirectInput
supported controllers without limits… in terms of buttons and analog
axes. XInput comes with distinctive limits that suffocate the vital
air supply, the API, needed for more advanced controllers. Basically,
Microsoft has unplugged themself from supporting the advanced PC
gaming controllers market.
Read on →