Project Advice

Discussion in 'I wanna be a Game Programmer' started by Alphabat, Sep 27, 2008.

  1. Alphabat

    Alphabat Lurker Not From Round Here

    Hello Everyone,

    After giving much thought, I came up with a project idea that I will have fun working on for the next few months. This happens to be a "simple" 3D game in which I will be hopefully showcasing my skills in game programming. I have done a lot of research and was hoping for a final push in the right direction.

    You see, I'm not exactly sure what tool I should use for my project;
    In one hand I have OpenGL/DirectX which would allow me to practically create a game from scratch, but on the other I have 3rd party engines which have a lot of the lower level stuff already implemented, leaving time for the game to be made fun.

    Personally, I would like to someday work as a gameplay programmer, but I know that it is not always what newbies get to work on when they start. So although this project is definitely for me to learn some more skills in order to become a game programmer, it is ultimately about about me creating a project that I can show to employers.

    What I wanted to find out from you is whether you thought that creating a project like this in OpenGL/DirectX, and going through that type of experience (of creating something from "scratch") was more important than working mainly on the gameplay code itself inside an engine.

    The engine I am looking at, A7, does allow for C++ programming so it is not just a scripting environment.

    Just a little bit of background on me:
    I have worked on various small game related coding projects, including another complete game demo in which me and some buddies used C# and the XNA framework. Though I'm still a beginner by all means I say this to let you know that I'm not the random complete newbie that wants to make the next WoW. This one project would be pretty much my go to project to work on for the next year pretty much so I wanted to make sure that I was doing the right thing when choosing the right tool for the job with the above goals. Let me know which appeals more to you.

    Thanks in advance!
    Will
     
  2. yaustar

    yaustar Industry Professional One Of Us

    Personally, if you are aiming to be a gameplay programmer then the 'game' part of the code is more important then the 'engine' part. Knowing some OpenGL or DirectX is good but I would prefer to see a complete game over a complete engine.
     
  3. Alphabat

    Alphabat Lurker Not From Round Here

    Thanks very much for your take Yaustar.

    It makes sense to me to work on the game itself because of what I want to do in the industry. However, there are others who I have consulted who have expressed that the short term goal of learning the different components of a game engine and how they go together would make me a better programmer in the long run.

    I am curious to know what everyone else thinks. Please keep your feedback coming =)

    note: I've noticed a lot of views in the post before I got a reply, if there's anything that I can do to help you help me, just let me know.
     
  4. IFW

    IFW Not allowed to say NFTS are shit One Of Us

    Dont try to run before you can walk.

    I'd start with something like torque. Yeah it does use script predominantly but will show you understand a lot of the underlying stuff. It'll also amaze you how much c++ you'll probably have to write extra to it too.

    As for engines.. sure.. BUT - It's probably one of the hardest fields to get into and work in (as things change so much). But as you state that you want to be a GAMEPLAY programmer - i dont see why you'd want to do this?

    Problem is with starting from scratch is there's a lot to it (the engine, tools, etc etc) you probably wont ever finish the project. At least starting with an engine and FINISHING a full product - you can show:

    1) You're passionate about games
    2) You know the steps involved in making a game from beginning to end

    And as a plus - you might be able to sell it and get rich! :p
     
  5. IFW

    IFW Not allowed to say NFTS are shit One Of Us

    One more thing - try not to get TOO complicated. Finished project/demo says more about you as a "finisher" than an unfinished thing with the POTENTIAL of being great.. Hell I've seen people employed in the past who's demo consisted of a game of pacman/space invaders - But they were FULL games (i.e. complete with high scores, menu systems, input redefining, installers, etc etc) and were totally polished and "professionally" done.

    That's not to say that a game of pacman will get you a job.. Just to say a simple FINISHED game/demo is better than a lot of unfinished nice ideas... IMHO
     
    • Thank Thank x 1
  6. Alphabat

    Alphabat Lurker Not From Round Here

    It seems like it's really split between the different professionals who I've asked this question. Half say go lower level and the other half say go with the 3rd party engine.

    However, I've noticed that the main idea that everyone shares is that it is very important for me to have a FINISHED game or three. (but always going one step at a time)

    Thanks for the advice!
     
  7. NightCreature

    NightCreature Lurker One Of Us

    It kinda also depends on the company that will employ you on which things you are going to work when you start.
    A frend of mine is starting of as working for multiple different teams the first 9 months. And after that he can choose were he wants to work. I started off in Front end because I wanted to do graphics.
     
    Last edited: Oct 7, 2008