KeyEvents?

There is no event functionaity - you will have to implement it yourself. All you can do is check if something is up or down. See gamepad.cs in spacewar - I had to implement a flag for each button to get indiviudal button presses. It would be easy to turn this into event throwing code.

Yes a slow framerate means you may miss very short presses, but since this is a game its your job to make sure you don't get a slow framerate. Its pretty standard for game programming.

You can probably do something with another thread to make it more responsive if this is a problem.

TheZMan at 2007-8-31 >

faster than 1/60 of a second. The best way to do this using XInput

would be to simply poll the gamepad more often, perhaps from a high

priority background thread. This is exactly what all Xbox fighting

games do, because the underlying native API and to the best of my

knowledge even the hardware too is entirely based on polling!

There isn't any event support in the lowest levels of the input reading

system, so you need to poll this at some "fast enough" rate for your

game. For the vast majority of titles, just reading the gamepad once

per frame will work fine.

ShawnHargreaves at 2007-8-31 >

All the commercial games I've ever worked on (mostly racing games and

shooters, on N64, PS2, and Xbox) polled input 60 times a second, and

never had any trouble with that.

I would imagine that a beat-em-up could need to go faster, but having

never written one I don't have a good intuition as to how fast would be

needed.

My advice would be to just ignore the problem until it crops up in

practice. It's the kind of thing where you could spend ages theorizing

about what might go wrong, or just write your game until you actually

see the problems for real, at which point it will be really easy to

experiment and find out exactly what polling rate is needed for good

results!

ShawnHargreaves at 2007-8-31 >