Jump to content

  • Log In with Google      Sign In   
  • Create Account


Member Since 04 Jan 2013
Offline Last Active Sep 01 2016 08:41 AM

Posts I've Made

In Topic: Things you MUST learn before coding in games?

19 January 2016 - 04:45 PM

When you say '2D layering', are you talking about something more complicated than for e.g. background art made up of different image layers (so that they are independent of each other and complete a picture), or is there some context to that I'm missing?

In Topic: Things you MUST learn before coding in games?

19 January 2016 - 03:31 PM

I mean concepts like 2D layering, parallax scrolling, cartesian coordinates, etc.

Are those by any chance things I should know about?  

In Topic: Which type of sounds you are looking for most ?

18 January 2016 - 06:36 PM

As a sound designer I would say I only 'need' sounds I can't create myself (or at least not to a certain level of production).  I suppose the answer has to be dubstep drum samples.  Outside of that I'd be interested in the sound of a tokay geckos mating call because you really can't plan a studio session for a tokay gecko to do that.  

EDIT:  This one ain't bad actually 

In Topic: Things you MUST learn before coding in games?

18 January 2016 - 06:27 PM

The best way to learn conventions and common patterns is to read code made by others, by writing code (and rewriting it for improvements), and getting your code reviewed.

Definitely!  I learned a considerable amount from reading through the source files of an open source library I was using.  On the other hand, I feel that without a complete understanding of how the (or any) entire library works, one might be lead to incorrect assumptions or confusion over /why/ code has been structured in certain ways.  

I'm really looking for theoretical topics to study here though.  For e.g. I had trouble with including header files at first for a couple of reasons, but it can be boiled down to this...

What I knew:  typing #include 'myheader.h' will make the code from my header work in the scope of this piece of code
What I didn't know:  ANYTHING about linkers.  

This meant that when one of my included files didn't work, I didn't know how to troubleshoot the problem because I lacked core theoretical knowledge.  I think there are probably similar gaps in my knowledge - I'm just not sure what they are.  All I really know is how to code inside the C++ box, but I lack most knowledge at a lower level. Coming into game programming I at least want to make sure I know how to keep things as optimized as possible and not create any bottlenecks at runtime.  That's all I'm really looking for! 

In Topic: How Important is an Honours Degree in Games/Audio Industries?

18 January 2016 - 11:59 AM

Cool, thanks for the advice!  My mental health has already improved just knowing I don't having something to worry about anymore.  

If I got any full time work just now, I probably wouldnt have much time to focus on self-learning.  Doing my own projects includes learning about the full graphics side of game dev, as well as learning as much as I can to improve my coding.  Getting work experience would be great, but I'm sure any job I would be offered anytime soon wouldn't be too strong on graphics or programming in terms of day to day work.  Those are topics I really need to get up to speed just now.   I am doing a game jam in two weeks though - intend to network and possibly find projects to be involved in with teams, so hopefully my plan won't be too unproductive.