GP2X How Do I Even Start Game Programming?

[Saido]

I really want to make games for the GP2X.
I can program in C/C++ and some SDL but i have no idea on how to start.
The only thing i can create atm is this: googly

 

[Digitalrat]

Did you look at the tutorials on http://www.libsdl.org/tutorials.php? I think that some mention game concepts.

 

[Prophet]

http://gameprogrammer.com/programming.html

http://cone3d.gamedev.net/cgi-bin/index.pl...ls/gfxsdl/index

Seem like good tutorials.

 

[Digital Awakening]

I like Sol's tutorial, been using that myself, started 2 days ago. And thanks to Prophet for the links. On SDL's tutorail page I found the link to this page that covers a lot of the basics of game making, looks like great stuff:

http://cone3d.gamedev.net/cgi-bin/index.pl...ls/gfxsdl/index

 

[Saido]

uh guys i don't want to know how to learn SDL , that's finding out how the function works.
I want to know how to create games, the only thing i know is how to create a game loop with states.

 

[Digital Awakening]

Well, they are game oriented tutorials if you just take a look...

The one(s) I linked to as well as Sol's.

 

[TreeFrog]

I guess the question is then, what do you want to do that your state-based loop won't let you?
There isn't really a generic answer to how to write games...

 

[Prophet]

You could get some source code for an open source game that is similar to what you want to do. If it's well documented at all, then you could pickup some good ideas that way.

 

[yaustar]

http://gamasutra.com will give you an insight to games. Learning about state machines would be a good start. If you are still learning C++ then grab Thinking In C+ Vol 1 and 2 from http://www.bruceeckel.com for free. As treefrog said there isn't a generic anwser to it, its more learning and apply to your concepts.

Also http://www.gamedev.net/

Start off with a simple clone like space invaders and work your way up...

 

[Saido]

Well i already know C/C++ but i am used to writing tools for windows.
But thanks for the links all.

 

[GP40]

Good links thanks

WooHoo. I was worrying I'd need to learn linux and a 'SDL language'. But I can see from the links, its all C++, sort of like .NET h34r: and it looks easy to understand

Do I need to use the 1.2.9 version or the 1.0.8 version?

 

[pea]

Well, if you already know c/c++, then games are just an extension of what you already know. Just break it down into all the blocks you need and figure each one out individually. Look at it from a high level perspective first and then drill down until you get to code level and then code it Like has been mentioned, there is no set way to do it.

You already mentioned a game loop and game states, which is a really good start. What else do you really want to know?? :blink:

Basic game loop:

STATE 1 - in game
1) Process input
2) Update game objects based on input
3) Process AI
4) Update game objects based on AI
5) Check for object interaction (colisions etc)
6) Change state based on interaction
7) Render scene

STATE 2 - lose life
1) Process input
2) Change state based on input
3) Render scene

STATE 3 - level up
1) Process input
2) Change state based on input
3) Render scene

etc...
A flow digram would be the best way after that to break each state down further.

HIH

 

[Saido]

Well, if you already know c/c++, then games are just an extension of what you already know. Just break it down into all the blocks you need and figure each one out individually. Look at it from a high level perspective first and then drill down until you get to code level and then code it Like has been mentioned, there is no set way to do it.

You already mentioned a game loop and game states, which is a really good start. What else do you really want to know?? :blink:

Basic game loop:

STATE 1 - in game
1) Process input
2) Update game objects based on input
3) Process AI
4) Update game objects based on AI
5) Check for object interaction (colisions etc)
6) Change state based on interaction
7) Render scene

STATE 2 - lose life
1) Process input
2) Change state based on input
3) Render scene

STATE 3 - level up
1) Process input
2) Change state based on input
3) Render scene

etc...
A flow digram would be the best way after that to break each state down further.

HIH

​

Thank you for your help this is exactly what i meant.