Comments on: A Basic Game Architecture

By: Getting Started in Android Game Development with libgdx – Create a Working Prototype in a Day – Part 1 | Against the Grain – Game Development

Tue, 28 Feb 2012 19:53:44 +0000

[...] very straight forward architecture based around an continuous loop. You can find out more about the architecture and the loop here and [...]

By: Building Games Using the MVC Pattern – Tutorial and Introduction | Against the Grain – Game Development

Sun, 05 Feb 2012 15:41:11 +0000

[...] know from the typical game architecture that the main loop acts as a super controller, which updates the states and then renders the [...]

By: chirag patel

chirag patel — Fri, 29 Jul 2011 13:51:55 +0000

it very help full me for understanding basic about gaming. .thnx dear.

By: Android Game Development | | Useful Resources

Android Game Development | | Useful Resources — Wed, 13 Jul 2011 19:41:47 +0000

[...] Reference: A Basic Game Architecture from our JCG partner Tamas Jano from “Against The Grain” blog. [...]

By: Impaler

Impaler — Wed, 06 Apr 2011 09:05:17 +0000

I would implement a very thin input layer and depending on the complexity of the input, would use a queue or just direct variables.
For example if you would use 4 regions of the screens for up, down, left, right, the input layer would have 4 boolean variables for the directions (isUp, isLeft, isRight, isDown) and would set them to true every time the respective region has the ACTION_POINTER_DOWN and false otherwise. The update() will read these values and act accordingly.
If it’s more complex I would use a queuing middleware.

By: Leandro Peralta

Leandro Peralta — Tue, 05 Apr 2011 20:27:59 +0000

I really like this site. I’m working on my first game project for Android now and I cannot figure our how to implement an efficient input layer. Should I make direct call to the GameEngine class from the onTouchEvent method of the activity or would it be better to implement a class that holds a queue for the input in the middle?

By: Impaler

Impaler — Mon, 28 Mar 2011 08:33:36 +0000

The higher FPS you achieve the smoother the graphics gets.
If it’s very heavy on graphics then it’s likely that the FPS will drop and then it is advised to plan for a lower one.

By: harvey

harvey — Mon, 28 Mar 2011 08:20:46 +0000

Hi,

30FPS? why not 25FPS? Do you know the replica island ?

it set 25 FPS

By: Best explanation of FPS

Best explanation of FPS — Mon, 13 Dec 2010 06:35:05 +0000

[...] Just imagine someone walking and close your eyes for exactly one second. After opening your eyes you will see the person in the position after one second. This is a 2FPS. Source – http://obviam.net/index.php/2-1-a-little-about-game-architecture/ [...]