CAGD Blog

  I have been working on the game “Everest Expedition” with my group members Ishmael and Dylan for the last two sprints. In all honesty, this most recent sprint, “Sprint 2” was not the best work that I could have done with the time I had put away. I was dealing with some difficult personal issues during this sprint and did not perform to the level that I know I am absolutely capable of. So for most of this blog post, rather than talking about what I did complete during this time, I am going to be talking about what I plan to do with my next sprint, since I know I can do better work than what was completed within these last two weeks. I will start off the post with what I got done and then converge into what I plan to have done by the next sprint, as this sprint was quite short in terms of cards completed, I would much rather focus on what I will be doing going forward from here. For what I did during Sprint 2, I got our basic motion working. This means that I got our W and S keys...

  Everest Expedition - First Sprint     I am currently working as the programmer on a game for CAGD 370 called Everest Expedition. The main idea of the game is that you use your mouse, which controls your trusty pickaxe, to scale the side of Mount Everest while using WASD to traverse through the world. Now that we have finished the first sprint of our prototyping process, I have realized how much I underestimated the difficulty of getting the Unity physics system to do what you want it to. The first thing that I did for the project was set up the GitHub, which wasn’t too difficult or anything and took me roughly 20-30 minutes to set up and get running. After this, I set up a unity project and attached it to GitHub and with this, our group was able to start working on the digital prototype. Broken joint system A large portion of my time was spent trying to learn how to use joints and make colliders work, and in the end, scrapping all the time I had spent since it was not w...