Richard Kang PPJ Final

Positive: 

  • Learned a lot about some unity and code practices that I haven't touched as in-depth before.
  • Constructed plenty of frameworks that were used or iterated upon to the final build of the class.
  • The core game is very enjoyable to play, and it seems that other players agree
Negative: 
  • The work we put out seems smaller in comparison to other games produced by previous classes.
  • My work seems to be less obvious than the artists and the other programmers (Yes, I know I'm being petty)
  • Work was slower due to external events outside our control, and less time meant all classes were rushed
Learned:
I had worked with several systems that I haven't as different programmers have different practices.
A new method for goal tracking
More proof that Git and Unity are terrible together

Comments

Post a Comment

Popular posts from this blog

Sean McFadden Final PPJ

Positives: Got to work with some incredibly interesting tech and apply it creatively Game felt really fun to play and the movement system is very well crafted Systems were very well designed and allowed for easy integration with other systems Negatives:  Some of my work took longer than expected and most was finished very close to the deadline  Some of the scope of art assets were scaled back and not everything got finished  HacknPlan was used often but at some occasions it was not used to it's fullest potential
Read more

Rex Christian Personal Postmortem

Personal Postmortem Things that went right: 1:  Group member roles and workloads were typically very well defined and separated. We had very few issues with overlapping or conflicting work. 2: We communicated pretty effectively and easily contacted each other when we needed help or coordination while adding to the game. 3: We all mostly agreed on our vision for the game, and never really had any arguments or disputes regarding how the game should play or look. Things that went wrong: 1: Most of our work happened 1-2 days before the due date, and sometimes we'd even be patching bugs and getting things working mere minutes before class started. 2: Though we met on most weekends, we only planned our work during those meetings. We actually DID the work separately, only to meet right before class and compile it all at the last minute. 3: Sometimes features that were largely complete wouldn't make it in the week that we'd made them because we'd encounter a bug or ...
Read more

Sean McFadden PPJ#7

Overview:  Time Spent: Procedural Mesh Research: 3 hours Compute Shader / GPU offloading: 3 hours Compute Shader planning and UML: 2 hours Positives: Spherical clouds have the potential to be very cool Negatives: Subtraction volumes scrapped Upcoming: Finishing procedural mesh clouds
Read more