Jake McKenna - PPJ 02


General Updates:

This weeks theme was ironing out the kinks in the pipeline. We've identified a number of issues that are going to get worked out in the coming week. Even so, we made a lot of progress on the game. There was a really good meeting about the story direction and world building. We got a new UI in, and made a new tutorial level. There were updates to the play test survey, and a new build. 



Personal Updates:

I had a bit of a trial by fire with the Git-Hub this week. I came out the other end having learned how to properly use it, but there were some small losses.

 I built a new tutorial level. It's not super pretty, but it teaches you a bit about the movement,  environment, and combat. I plan on refining it a lot more in the coming week. I hope to go through and make a few more meshes in Maya to help with blockouts. Right now the level isn't really air tight either, so that's something I need to address in the next couple days. 

I also went back to the previous week's level and added in a "choice" I wanted to see how it would feel to choose between two paths. The idea was to present the player with two options, prompting them to double back and try the other one, or potentially plan their route to hit the missed path. I'm not sure how I feel about it yet. I'd like to do some more refining and see what the playtest feedback says. 

Additionally,  I helped work on the playtest survey.  I didn't do too much, Malcolm and Jake D. deserve the credit on that one. I ported over some of the questions from our Journey's End survey and advised on rewording some stuff. 

I also attended the Design and Art meetings. I helped walk the team through the process of doing a ground up world build from a writing perspective. It seemed to help answer a lot of questions about where the art direction should go. I hope to continue help with that process as much as I can. 

Finally I, with peter's help, made another core prefab for the checkpoint based levels. This way Malcolm and I can easily create levels of either type in the future. 



Total Time: 9-11 hours if you include the meeting 8 if you only include work. 



Work Samples:



Comments

Post a Comment

Popular posts from this blog

Peter Eldredge PPJ #1

Image
Team Meeting - 2 Hours Gameplay UI Rewrite - 3 Hours Gameplay UI Rewrite This week I decided to rewrite the UI to be more modular. Before, nearly the entirety of the gameplay UI was handled in a single script. I broke that up into a bunch of components that handle different aspects of the UI individually. Now, there is a Health UI Controller, Heat UI Controller, Score UI Controller etc. Additionally, each screen has its own component and can handle itself. This should make it much easier to expand the UI effects, and overall just make it easier to work with the UI.  This ended up being more work than I thought, as now what was once a 300 line file is now repurposed as a sort of UI helper that can be referenced for overall UI things such as enabling/disabling the UI, timescale manipulation for pausing, and input handling. The rest was separated into 7 different components which all are derived from a Base UI Controller class which basically just automatically subscrib...
Read more

Rex Christian Personal Postmortem

Things that went right: I got to do what I love: Making 3D models of sci-fi stuff. Having more artists on the team this quarter allowed us to divide and conquer, working on multiple levels at once and getting a lot more done each week. Meetings were a lot more talkative with the increased team size, and we had lots of discussion and feedback regarding our plans each week. Things that went wrong: We had some communication issues early in the project, resulting in overlapping or incomplete work since we didn't fully understand what each member was working on in some of the earlier weeks. Though we got our work done earlier in the week than last quarter, we still had a tendency to make last minute patches and updates just before class. I personally didn't communicate as well with level designers as I should've; I sometimes pushed model and texture updates to scenes without notifying anyone, only for them to be discovered later. This never caused any real problems, just some oc...
Read more

Ethan Scheidlmeier PPJ 9

What Went Right: The Game- Though there were many hiccups along the way and the game doesn't look exactly as we expected, we made a game that is functioning and fun to play.  The Assets- While they had their own challenges, I believe the models for the game turned out fairly well and make the game interesting to play. The Leadership- The team leads did a great job informing us on what we needed to do each week. Though the overall communication within the group could have been improved, the team leads instructed the meetings very well.   What Went Wrong: Communication- Many of us, myself included, struggled to communicate to the group as much as we should have. This led to many things not being implemented until the builds and the ideas to not be fully fleshed out until the next week. Story/Narrative- The story of this game was a lot larger when we first discussed this project for the term. Week by week, more and more cuts were made to it. Eventually, it got to the point w...
Read more