Sean McFadden PPJ#2



Overview:
 Time Spent:

  • Noise Generation: 5 Hours
  • Raymarching Shaders:  2
  • Cloud Research: 6 Hours
Positives: Clouds seem promising, volumetrics are very interesting in Unity
Negatives: Can't make any assumptions about cloud performance at the moment, so I don't know how they will hold up when working with large volumes.
Upcoming: Continuing cloud work, player reactive heat shader as well

Comments

Post a Comment

Popular posts from this blog

Peter Eldredge PPJ #6

Image
Bug Fixes/ Random Tweaks and Testing/Polish - 3 Hours Code Refactoring - 1 Hour Post Processing - 2 Hours Rumble Implementation - 2 Hours Overview I think artistically and game feel wise this week was very productive. This was thanks to the menus being filled out with 2d art and the implementation of Unity's Post Processing as well as the Beautify, another processing solution. Additionally rumble was added which adds a lot of impact to the collisions in the game, as well as allows the player to feel in heat increase better. Bug Fixes Tons of minor bugs were fixed and time was spent tweaking values. Not all of these are worth mentioning but I'll list the biggest ones: Fixed a issue where the player would rotate inappropriately after colliding with an object, causing the player controls to become inaccurate. Fixed issues where the prefabs were not consistent between scenes and not being saved properly. Fixed an issue where pausing the gam...
Read more

Sean McFadden PPJ#2

Overview:  Time Spent: Git Write-up and Practices Update: 2 hours AWS setup and Webhook setup: 2 hours Website rebuild into Vuejs: 2 hours Positives: Updated Git practices are incredibly helpful Negatives:Website broke at the last minute due to the EC2 instance Upcoming: Finishing the website and updating compute shader clouds
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