After a lot of breaking things, refactoring, and testing, I’ve finally merged the experimental branch of KeyActionBinder into the main branch of the project. The biggest change, of course, is making the functionality of this gamepad support library more automatic, in the sense that it tries to detect whatever game device the user has connected […]
Continue reading →When I set out to write a class to simplify game input control in ActionScript 3, I started from the assumption that Adobe AIR’s GameInput device control ids (the ids that relate to each button or axis) would be fairly consistent between platforms. The idea was that the class would just hide away the Keyboard […]
Continue reading →When testing my latest game prototype, I realized I needed certain player inputs to be time-sensitive, that is, only be acceptable if they were activated within a certain time limit. This is useful for one specific condition: jumping. In my game prototype, I had my jump activation checks like so: function gameLoop():void { // Calculate […]
Continue reading →As I mentioned in my previous post, one of the advantages of abstracting game input with a class like KeyActionBinder is that supporting more than one platform is a fairly easy, one-step process: you simply specify the expected inputs during setup of the key binder. I’m currently building a (fairly fun!) prototype and I plan […]
Continue reading →As it should be obvious to anyone following my rants on Twitter, I’ve been playing with TypeScript quite a little bit recently. And although I haven’t created any huge project with it, I have been embracing it little by little on everything I’ve been doing that requires JavaScript. This past weekend I had free time […]
Continue reading →To build the list of known GameInput controls spreadsheet, I had to build a small sandbox-like application test for controls reported by connected devices. It was my intention to make this available to other people so they could do their own tests, so here it is: just wait for the following Flash movie to load […]
Continue reading →Adobe AIR’s new GameInput APIs are great. They provide seamless, powerful input from game pads for Android, desktop and web applications created in Flash. However, it has two important problems right now. Since those warrant some explanation, I figured I’d make a post about it hopes it’ll help other people working with those APIs. The […]
Continue reading →I was curious about the latency of the GameInput API in Adobe AIR and decided to test it a bit using my game prototype. I tested it both as a desktop app, and as an OUYA game. Here’s the results, first in the desktop: And in the OUYA: Perhaps it’s not very clear by the […]
Continue reading →For my latest game prototype, aside from KeyActionBinder, I’m also using my new GameLooper class to control the main game loop. Because of the way the class has been built, it is particularly easy to integrate it with something like Box2DFlash, which is what I’m using in my prototype for physics simulation. Integration works by […]
Continue reading →In general, dealing with keyboard input in ActionScript 3 is fairly easy: you simply listen for KeyboardEvents, and react accordingly. This works very well when the user is interacting with a graphical user interface – you simply turn your event listeners on and off, and wait for something to happen. When developing games, however, this […]
Continue reading →