Direct Input is almost completely dead (Microsoft has deprecated it).Īs far as input latency goes: Raw Input > XInput > Direct Input.
So while I think that in any instance the amount of lag we are talking about is inconsequential, if anything, 360 gamepads should be faster.Īctually, you're wrong. you can dump it directly into a xinput_state structure and it's ready for use in the game code. no usb handling nonsense and no need to parse. The report data is like 16 bytes sent at once (if I'm remembering correctly. which is exactly how old consoles and arcade machines did it. meaning it has to ask the state of the devices in the game loop. In addition xinput requires active parsing. Xinput devices show up as device 1-4 and they are pre configured as they are plugged in. Mind you it isn't a huge amount of lag in terms of human reflexes, but keep in mind that Xinput was introduced to streamline this. DirectInput is event driven, meaning if an event occurs, it fires a generic function in which the device and type of event has to be parsed, filtered, and then handled. Keyboard input on modern pc games is typically handled through directinput. The problem is they only work when you use the actual keyboard.Īnd since I'm so fond of pummeling horse corpses. With both the IPAC and keyboard plugged in at the same time, it appears the controls do work depending on what you set them to.
Quote from: evh347 on April 20, 2015, 03:27:16 am I downloaded today's update for the PC version, but I think they still have a ways to go. So instead of FP, BL, ->, etc.it shows the key that's associated with that move. So if your keyboard is unplugged, the only way to back out is to completely quit the game by shutting down processes (CTRL-ALT-DEL).Įqually as unhelpful is the fact that in Practice Mode, the actual moves stream along the side as the key that is registering from the keyboard. The issue with having only the IPAC plugged in (and not your keyboard) is that you can't map an ESC (back out) option. So it seems that MKX is not programmed to see more than one keyboard at a time. The IPAC registers correctly then as I've designated in the "wireless controller" settings. I have to back out of the game, unplug my USB keyboard, and then start the game. I have found only one way to get the IPAC to register correctly. My IPAC shows up fine (registers keystrokes) outside of MKX, but not within MKX. In the character and stage selection screen, the IPAC is completely unregistering as well as once the fight begins. In menu selection screens, my IPAC will allow up/down movement and ENTER selections, but that's it. The problem is they only work when you use the actual keyboard. I downloaded today's update for the PC version, but I think they still have a ways to go.