Jump to content

  • Log In with Google      Sign In   
  • Create Account


I think I'm ready to start....but....where?


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
7 replies to this topic

#1 Riyoha   Members   -  Reputation: 102

Like
0Likes
Like

Posted 01 February 2013 - 07:29 PM

I'm looking into the idea of making some simple games in my spare time (of which I have a lot due to being unable to work a normal job) with a view to eventually making something I can actually get paid for.

 

I know some C++ (enough to make a complex text game/simple 2D game like Pong or something) and I'm starting to learn OpenGL (I own the fifth edition of the super bible so I'm hoping between looking stuff up in there and maybe asking here if I'm truly stumped I can get figured out)

 

I'd rather not use an engine because I want to teach myself to make my own engine (yes I know I could make games a lot faster using Unity or something, but I don't know....I just think it would be kinda cool to learn everything I need to make games on my own, plus there's the fact I don't wanna have to pay a tonne to license an engine if I ever did decide to go commercial)

 

I could just search google forever and read a million tutorials but I'd probably learn better by diving in and fiddling about, I can handle most of the tasks myself with a little guidance, it's just....I'm a little stumped on where to even start.

 

My eventual goal would be a Monster Hunter type of game, or before that maybe some kind of cross between Minecraft and Pokemon and JRPG styleness.

 

I'd also like some advice on how to design the game BEFORE I start coding, what should I do with that? (That's an area I know nothing at all about)

 

Anyway...I hope this rambling weird post isn't too confusing! ^_^



Sponsor:

#2 AdrianC   Members   -  Reputation: 602

Like
3Likes
Like

Posted 01 February 2013 - 07:45 PM

One thing I want to say is, if your goal is to make a game, going the OpenGL is going to waste a ton of time. I mean years, if you want to have anything half decent. If you want to do it as a learning experience, then yeah, definitely go for it, but if you mainly want to actually create a game, then use an engine.



#3 Serapth   Crossbones+   -  Reputation: 5325

Like
2Likes
Like

Posted 01 February 2013 - 08:08 PM

Start here.



#4 Agbahlok   Members   -  Reputation: 262

Like
0Likes
Like

Posted 02 February 2013 - 12:13 AM

Some time ago I was lost same as you. I'll try to do my best to give you few advises on what you could do at the moment. As I understood from your post you have pretty decent knowledge on C++ ( I assume that OOP paradigm [at least the basics like types of constructors and how to use them, inheritance, maybe polymorphism etc.], at least basics of STL (very, very useful in game programming at least for me), strong foundation about raw pointers/smart pointers are not something that is difficult for you ) as well as I hope you spent some time to study IDE you are using - especially the debugging aspect, as it can save you from hours (literally!) of frustration while looking for some dumb bug like forgotten semicolon at the end of class definition laugh.png

Well, about the tips. Firstly, it's very good that you have a goal you'd like to achieve and in my opinion you should stick to that goal and do everything that's possible to make it happen. Most important in order to "survive" is to find a realistic goal, then to make sure that you possibly could make it happen with the knowledge and assets that are available to you and then just keep going for it and remember to NOT TO abandon what you already have started, because of laziness as it will bring MUCH reluctance to future projects or maybe even programming. That's why you should always keep in mind to keep your goals relatively simple and doable.

Next tip would be ( when you already have started some project ) to try to split bigger tasks into easier ones like:
"Implement basic logging to my engine" could be broke into:
  • "Make an decision what single log line should contain"
  • "Create an abstract skeleton class containing only what's most necessary"
  • "Fill methods with code"
  • "Instantiate logging class where it's necessary"
  • etc.
Above breakdown could be done far better with some time spent on it, but it's just an example, which I hope is quiet clear and understandable. Bare in mind that even tasks that are child of parent tasks can be broke into even easier tasks if you find them to complex. Just don't go for something like: "Wash my teeth", please happy.png

First thing I propose is - don't try to create an engine pointlessly. If you are serious about making a game from scratch with help of OpenGL first thing you'd have to do is to spend some time to gather thoughts about what kind of game would it be, what would it need, would you be able to make it, would you be able to find necessary assets ( I assume your first game wouldn't be a commercial one ) or maybe some people could possibly make them for you ?

Then break it down to smaller ones just like with programming tasks, so for example if you'd like to make a game similar to Minecraft you should ask yourself any question about the gameplay you can think about, like would it be from 3rd person or 1st person or maybe side camera ? Would it just be single player or do I have necessary skills/could I learn necessary skills to make it multiplayer ? Would the world be generated based on seed or would I rather use presets ? etc. etc.

After finding an general outline you can and you should break down those thoughts into even more detailed and so on as long as there are any thoughts in your mind about the game. Oh, and remember to note EVERYTHING. It's really, really essential to do so. After you are done with non-technical description you should try to transform it into a kind-of framework documentation though not really a one. Just clean-up your thoughts into some framework-compatible order, maybe try adding some technical comments about implementation details, maybe try to attach some pseudo-code, umm you could try UML as well.

Basically that's what you should do before you start coding. Project planning as well as project management are HUGE fields to play with and you could find tons of books about it, but as you are programmer it's not your goal to be an expert in that field ( as long as you do not want to be one, but in my opinion as a beginner you shouldn't bring too much on yourself ). Remember to keep doing it in funny way to make the creation process entertaining as well. It will help you work longer. You could try to involve your friends as well, even if they are not programmers or 3D-artists or 2D-artists or audio-engineers they can still give you some ideas and make your game just better.


That's about it for my tips for now. If I'll remind myself anything more I'll edit my post later.
Most probably you won't take what I wrote here seriously ( I wouldn't not so long ago ), but just that you read it makes it count.

Best of luck to you !

Btw. Unity3D is free for commercial use as long as you do not exceed 100,000 $USD of income yearly though free version is a bit stripped you could still find it very useful. Commercial license is not that expensive as well. It's 1,500 $USD if I remember well.
Btw2. UDK by Epic Games and CryENGINE 3 SDK by Crytek are both something that could possibly interest you as they are very cheap ( CE3 SDK is free for indie devs if I remember well ) and very mature and advanced tools built by efforts of dozens of programmers and artists from all over the world through the last decade.
Btw3. It's totally your call, but I personally find Direct3D much easier to understand and much clearer in code then OpenGL. You could also make yourself familiar with the quiet a bit of lecture in here http://programmers.stackexchange.com/questions/60544/why-do-game-developers-prefer-windows

Edited by Agbahlok, 02 February 2013 - 12:21 AM.


#5 warnexus   Prime Members   -  Reputation: 1394

Like
1Likes
Like

Posted 04 February 2013 - 10:44 AM

It's nice to write the code yourself IF it does not exist in a library. But remember: do not waste time REINVENTING THE WHEEL! People made these libraries to make your life easier.



#6 Fs02   Members   -  Reputation: 383

Like
0Likes
Like

Posted 05 February 2013 - 06:16 AM

if you want doing all from a scratch, why don't you start with more simple liblary like (sfml and box2d) ?

and then going 3D with Ogre3D/Irrlicht and Bullet Physic.

 

OpenGL is a low level and need huge efforts for making a game without any library :)


[my game in #ggj14 : http://www.indiedb.com/games/romance-stalker [my blog : http://surya.volge.net ]


#7 GearTreeEntertainment   Members   -  Reputation: 322

Like
0Likes
Like

Posted 06 February 2013 - 10:06 AM

I know very little on c++ programming. The only real game I programmed was a text based adventure game that was only a little advanced. But I do know how design and develop a game. There are a couple steps in the process. Here they are:
-What theme is the story gonna be? Fantasy, si-fi, present day?
-Then think of the world its gonibg to be in. Is it going to be like J RR Tolkiens middle-earth, or like the famous starwars galaxy.
-The think of your character. Is he humble, proud, evil, emotinal?
-Once you hit all the things about the story, create a map of the world. This will give you a basic idea of where the character will be going through, and wont leave you always thinking of the world, but the gameplay.
-Once you got this, think of what kind of game its going to be. Like space invaderz, mario, golden axe?
-Then think of special things you can add to the game. Like bioshock has plasmids, portal has portals, and so on.

Once you get all this done(make sure to write down everything) start programming. If anyone else has something else to say you can just.reply to my reply.

#8 3Ddreamer   Crossbones+   -  Reputation: 3133

Like
0Likes
Like

Posted 06 February 2013 - 08:54 PM

SDL could be a good one for ya.  Take a look at it.


Personal life and your private thoughts always effect your career. Research is the intellectual backbone of game development and the first order. Version Control is crucial for full management of applications and software.  The better the workflow pipeline, then the greater the potential output for a quality game.  Completing projects is the last but finest order.

 

by Clinton, 3Ddreamer





Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS