Members - Reputation: 665
Posted 12 February 2013 - 11:42 AM
Crossbones+ - Reputation: 1719
Posted 12 February 2013 - 02:53 PM
You will first want to start by selecting an engine or api framework that supports the graphics that you are looking to do. Many people on here will suggest SDL or SFML as good starting points. How you go from there (eg the implementation of the technology supplied by the engine / framework) will matter entirely on the suggested process of the engine or framework. Or in other words, find what you want to use and then read how they tell you to use it.
You can of course find whatever suits your needs or likes as well. You are not limited to these or any frameworks less the requirements of your project.
Professional Programmer & Hobbyist Game Developer
Members - Reputation: 1358
Posted 12 February 2013 - 09:17 PM
If you decide upon SDL I recommend LazyFoo's tutorials. I personally prefer SDL over SFML because I've used it longer, but it's really whatever floats-your-boat.
Both SDL and SFML have bindings for OpenGl if you would like to use that further down the road. LazyFoo has recently added openGL tutorials with sdl (although I would stay away from OpenGL for a while).
Link to LazyFoo SDL Tutorials: Lazy Foo' Productions
Link to LazyFoo SDL and 7 OpenGL Tutorials (Incase you want to take a peek): Lazy Foo' Productions - OpenGL Tutorials
Fly Safe 7o
Members - Reputation: 864
Posted 13 February 2013 - 09:02 AM
this is the base of the hit tests system I used in multiple of my 2D games:
with corresponding cpp:
and the whole code folders:
the geometry stuff is in tools, but you get interesting binary tree partitionning acceleration in that folder if you need.
you also have a demo to show how "simple" the usage is from a client perspective, here:
Members - Reputation: 970
Posted 16 February 2013 - 04:04 PM
If you do decide to use SDL as your API I would suggest checking out Tim's tutorials at http://www.sdltutorials.com/
His tutorials will take you through the basics of the game loop, rendering images, receiving player input, collision detection, and more. The tutorials are graded, so at first you'll start with programming a simple game - Tic-Tac-Toe, and you'll move onto something more complex - the basic elements of a side-scroller.
Members - Reputation: 116
Posted 17 February 2013 - 07:45 AM
Do yourself a favor and do not limit yourself to C++ game programming tutorials only. The most difficult part of making a game is proper game design, the translation of that design into an executable code is not as difficult (if your are fairly proficient in the language/api you are using). I have learned many amazing design tricks and code snippets from many different tutorials of varying languages and libraries.
SFML and SDL aren't really game engines or even game libraries per se - you yourself will have to build your own game engine using SFML/SDL. If you were to check out libraries of other languages that are specifically made to create games (such as Slick2D or LÖVE) you might be able to learn quite nifty tricks that you can then implement in your C++ code.