Tuesday, February 24, 2009

Game Design and Concepts

It goes without saying that knowing your job is essential to thriving in the business place.  I mean, duh, of course you should know your job.

But what about other people's jobs?

In our industry, some of us are focused strictly on production.  There are others who's strength lies in post production, or even pre production.

Take the latest project i've gotten myself into.  I am a small part of a larger whole, developing a video game MOD.  (I still don't know what constitutes a mod since we've rebuilding the game from the ground up :)

Music, SFX and a little programming.  That's my job.  Its split between two providers.  Game Music Inc and Bad Dog Digital.  But how essential is it for me to understand the low level game engine?  Or the SDK iteslf for this game?

I believe the answer is, quite essential.  Since my work is only a small part of the larger whole, in order for me to integrate that part into what comes before and after, I need to understand other's roles.

Instance:  The voice over recording.  We're doing that, we will work off of a script that will be provided by the level designer.  After those voice parts are complete, how do they get into the game?  We can't just stuff them into the audio assets folder and link it to the level, because the scripted action requires lip-synch between the character's textured lips and the voice over.  Is that my job or the programmer's?

Ah yes, blurred lines.   Thats why I love what I do :)

In this case, it will be the level designer's bag, since he's really doing all the scripting and I don't know how the action( Camera angle, movement) is supposed to go.

Since I know the larger part, greater than mine, I can ask these questions and best serve the others working on this project, because I understand what they need, not what they do.

Till next time
j