Everest Expedition - Postmortem

Everest Expedition - Postmortem


I have been working as a programmer on the game Everest Expedition for CAGD 370 at CSU-Chico. It is a prototype for a game based around climbing a mountain with a pickaxe using the Unity collision and physics systems. We just finished our very last sprint in the process and are no longer working on the project, and throughout the 5 sprints I think I had a pretty rough start due to some personal issues I was dealing with, but ended up finishing it off pretty well.


Center puzzle of the level using my system

In the first two sprints, I only finished 2 points worth of cards, which is clearly not enough for a full 2-week sprint. I was dealing with some personal issues during this time that massively distracted me from my work and caused me to fall behind in the prototype progress. On top of this, I was deeply struggling to try to understand the unity collision and physics since this was the first time I had ever massively relied on them before in a project. I had about a dozen failed scripts to try to make the player’s pickaxe function as intended, and had to continuously change my approach to try to find a way to make the game work. This was also the first time I had worked with Unity’s joint system, so I had to do a huge amount of research to learn how to use each one correctly, which took a considerable amount of time and testing to learn. Looking back on this I definitely should have gotten help on this sooner, and I should have communicated with my professor better about what had been going on outside of class to make sure that he and my group knew I would be lacking a bit.

After these 2 sprints though, I picked up the pace a lot more. I was able to complete 6 points in the 3rd sprint, which was a massive improvement, as well as finally getting the physics to function as they were intended, which was a huge relief for me. On sprint 4 I lacked a little bit more with 4 points, though it was not nearly as bad as my first few. In our most recent 5th sprint, I was able to finish off the prototype with 5 points, closing out the project and doing much better than I had started. By this time, I was much more familiar with all of the systems our game was based on and was able to fine-tune all of the systems we had been working with so the game would feel a bit better to play for the players. I was able to correct my old, primitive colliders to new, more accurate ones, and fix some faulty force and gravity numbers that made it extremely difficult for the players to navigate at some points.



Fixed weight and force numbers


This means that in all I was able to complete 19 points over the span of the project, which is much less than I had hoped. If I had maintained the pace I had in the last 3 sprints, I would have had closer to 25 points in all, which means the first 2 sprints brought my total down by just about 6 points, give or take since I may have done less or more. Seeing this lack out of my first few sprints shows me that in my next project, I need to do my best to communicate with people about what is going on and what I need help with, and I need to learn how to pick up momentum and push through hardships. There were a lot of things that went poorly during this process, namely the early stages of it, but I was able to learn from my mistakes and figure out all the new issues being thrown at me. What went well through the project though is that I learned a lot about Unity’s different systems that I can work into my future endeavors. I also learned a lot about C# that I had not known before since I hadn’t done a ton of programming. I had to research a lot of the scripts I was trying to write, but in the end, it taught me a ton about writing scripts and how to organize and set them up well.


Fully finished joint script.


Overall, I didn’t end up performing as well as I had hoped during this project. If I could go back to the beginning with the knowledge I know now, I definitely think it would have been a smoother process, but I am planning to apply this new knowledge in the future and I believe I have grown as a person and developer because of this hardship. I am looking forward to my next project and have confidence that I can do well all the way through.


Comments

Post a Comment

Popular posts from this blog

CAGD 373 - Destiny 2 Tower - Sprint 5

Image
My name is Kyle Ramser, and I am currently working with my group to recreate the Tower, a social space from Destiny 2. We just finished up our fifth sprint of the project, which means we are nearly at the deadline for the game scene. This sprint was a fairly productive one for me, as I was able to finish nine cards, all which were very important to the main layout of our scene, and was able to make some progress on the modeling of a pistol for the main player character. So far, this has proven to be one of the most difficult models I have ever tried to create. This sprint, I focused on finishing the last of our main models. This includes things like the vault wall, the giant overhang in the back of the map, and a modular wall to be used for the left side of the map.I was able to model and UV each of these, as well as add a few smaller things like a target for the shooting range and a Unity local fog to block off the underside of the tower. All I need to do now is to import these models...
Read more

Blog Post 4 - Zomb-Merge

Image
  Blog Post 4 - Zomb-Merge My name is Kyle Ramser and I am currently taking Mobile Game Development at CSU - Chico. I have been a part of a team that is working on the mobile game Zomb-Merge, and I am currently acting as the designer on this project. Our team just finished the 4th sprint of our 7 sprint process and had our second digital playtest within the class, allowing our classmates to critique and give feedback on how our game is coming along so far. This sprint was more productive for me than the last one, and I was able to get our +1 design into play, which was my main goal for these past few weeks. To start off, I will bring up the issues I encountered during this sprint. For a large portion of the sprint, I was blocked on a lot of my cards and was unable to complete my cards such as adding a losing screen, adding a victory and switching cities state, and most importantly adding an attack function to the 2048 style puzzle. Without a scoring system, there was no way for me ...
Read more

Zomb-Merge - Sprint 3

Image
  Blog Post 3 - Zomb-Merge My name is Kyle Ramser and I am currently a student in the Computer Animation and Game Development major at Chico State. I am focusing on level design and am currently working as the designer on a mobile game with the working title Zomb-Merge for the Mobile Game Development class 377. Our team, Graveyard, just finished up our third sprint out of seven sprints in the semester and had our first digital playtest during this sprint. So far, we are a bit behind our ideal schedule, but now that the game is functioning and the major scripts have been implemented, the rest of our sprints should be able to pick up the pace a bit and put the game in a good place by the end of the process. As for the work that I completed this sprint, it was definitely somewhat lackluster. I had a very long week and did not put in quite as much time as I should have, but was able to put out some of the cards I had assigned. All in all, I have gotten the level completely laid out wit...
Read more