• Advertisement
Sign in to follow this  

erasing text

This topic is 1906 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Advertisement
To be specific, if you want to complete a game you need to pick one game to make, pick one language, and pick one library and then stick with those choices until the game is really finished. You will make mistakes, and you will run into difficulties -- but you can fix your mistakes and you can learn to overcome your difficulties if you stick with it and work hard.


In your position I would "give and up try something else" one last time -- don't spend too much time on the decision, but re-examine your options and choose a programming language and library to work with. Pick a game to make -- I think Pong is probably the best choice though. Then stick with the language and library that you choose until your game is completely done.

Given your experiences from previous attempts good choices might be C# with XNA, or C++ with SDL, but anything you feel comfortable to use will be fine. I would suggest spending some time practising the programming language first and then work through some basic tutorials on your chosen library -- then attempting your game again.




Alternatively, if programming really isn't your thing you can still create games using tools such as Construct 2, Game Maker, or others. These tools allow you to assemble games using point & click interfaces, sometimes with a bit of scripting in highly simplified languages, and if used properly can actually make much better games than a lot of people give them credit for -- there have even been commercially successful indie titles made with these types of packages.

Another option to allow you to participate in the creation of games without programming would be to learn about another discipline such as creating art or sound assets.

Remember though that using "game maker" packages or creating assets also requires you to stick with things if you want to be successful.


Whatever you do, if you continue moving from project to project, library to library and from language to language every time things get difficult you won't make progress.


I hope that's helpful and I wish you good luck! smile.png

Share this post


Link to post
Share on other sites
I'm going to make another suggestion here; either approach may be valid for you.

Your pattern seems to be that you begin something, hit a roadblock, can't get beyond it, then give up and try something else. Rinse and repeat.

Unfortunately those roadblocks seem to happen quite early and with quite findamental things, but yet you obviously want to do this kind of programming.

So my suggestion is that - instead of starting from scratch - why not take an existing open source game engine - one of the Quakes perhaps - and bash at it for a while?

You won't be dealing with the best, cleanest or most nicely written code in the world, but you will be dealing with code that works. With code that has already solved the problems you seem to get stuck on. There's no need to get too ambitious at an early stage, just trace through it, learn how things are structured, get a feel for what's done where, and remember that it's often going to be nasty gnarly code, so maybe try to rewrite some of it to be nicer, with the safety net of always being able to roll back if you mess up. Build up some experience that way and it might help you with some of the things you get stuck on in your own work.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement