Currently, I putting the final touches on the first draft of the script for the game, appropriately titled What Comes Before.
Now, for the second part: how did I get here?
When coming up with the idea for a Senior Thesis, I wanted to address what I thought Senior Thesis should really be all about. For me, it was a time to do one of two things:
- Explore a topic or field that I had been interested in and never had the chance to. I would be able to do my own research and complete a project that I truly wanted to create, not adhere to someone else's expectations.
- Create a project that was an all encompassing piece to properly demonstrate all of my skills and interests in something I could call my own.
So the question for me was not really which of the above two options was a better fit for me, but what sort of project would best fit my interests? Luckily, I am also in a game design course, so it did not take long for me to decide that I would be making a video game for my senior thesis.
Logically, the next question was "What is the game going to be about?" I was not going to simply make a game for the sake of making a game, nor was I going to throw in a story for the sake of having a story. As I said, I want to be a writer, so there was going to be purpose to whatever narrative I create.
As with all stories I tell, I wanted to aim to introduce a new perspective or new light to something we already have our impressions on, but pose the idea that those impressions might not be entirely accurate. Most of my stories look at society and cultures in a very large scale. I wanted to challenge myself to come up with something on a more personal level.
Thus, I created the idea of What Comes Before. (For the initial proposal, you can view it here.)
What Comes Before builds off of a number of different concepts and themes, from meta stories to interactive movies. As my first major project, I wanted to go big.
Unfortunately, a major part of going big involves large hurdles. In my case, most are technological. This is a big project that will require a lot of work with many of the different aspects. Fortunately, I have some shortcuts.
I will be using the Kinect extensively through the creative process. KinectFusion will be my main tool for importing real-world objects into the world of What Comes Before, allowing me to scan them in with their color data. I will also be using an application I created that allows real time skeletal motion capture using the Kinect and Autodesk Maya, saving me the trouble of creating all animations by hand (yes, they will still need to be tweaked, but that is nothing compared to the time I will save). Finally, while doing the recording sessions, I will be using the Kinect to record facial animations, expediting the process of getting lips to sync with the audio. This is an application that still needs completing.
| KinectFusion |
I consider this project to be more of an interactive movie than a game. While Heavy Rain is a very interactive experience, I still must view it as a game because of the fact that the decisions are apparent. It establishes a barrier for the audience and detracts from how immersive the experience could be. I want the game to react to the player's choices without the player being aware of it. I want it to come across as a linear experience, but when friends discuss the events of the game with each other, they realize that their playthroughs were very much estranged from one another's.
So this brings me back to where I am now. I am finishing the script (I begin writing the story as a book, thinking that would be an acceptable framework and medium of telling this story, but decided against it) and will be soon reserving the school's recording studio to record the voice overs. For my game design class, my final assignment is to create an animatic for any scene in my game, which I will utilize to plan out the opening cutscene (the only cutscene in the scope of this project.)