Peter Eldredge PPJ # 9

Settings Menu/UI Additions and Fixes - 2 Hours
New Incinerator Bot Behaviors - 1 Hour
Pause Menu UI - 30 Minutes

Pause Menu UI

The pause menu has been redone so it fits better aesthetically with the rest of the UI.

New Incinerator Bot UI

Incinerator Bots have gotten the rest of their functionality. They now have 2 different behaviors depending on distance. 250-1000 units from the player, the Incinerator Bot will rotate horizontally and move vertically to try and track the player. A raycast is fired in the direction of the Incinerator's movement, if it hits anything, the movement will be cancelled. The special parameters for the attack are the MoveSpeed and BufferDistance, where MoveSpeed is how quickly the Incinerator will track the player and the BufferDistance is the length of the raycast being fired. 

When the player is 250 units or closer, the Incinerator Bot will start its AttackBehavior. In this behavior, the bot will continue to rotate towards the player, but will not follow vertically. It also instantiates a heat trigger in front of it which increases the player's heat level. Any heat trigger may be slotted in or adjusted to change the size and HeaPerSecond. This heat trigger lasts for the duration of the time that the player is within 250 units. 

Settings Menu/UI Additions and Fixes

A lot of people had issues with the resolution dropdown not showing their available resolutions. This occurs because for some reason unity reads some monitor's refresh rate with decimals, and then when printed they are rounded down. However, when setting the resolution, it round up. This made creating that dropdown work for everyone and saving the correct info very annoying, and I ended up writing some really janky code to fix it. I believe it now works for everyone.

Additionally, the resolution will only update when "Apply" is pressed. This was something that bothered a lot of people for good reason.

Some people also wanted to invert controls, so I added an option for that in the settings that is saved. It uses the same toggle I made for the motion blur.

One last issue is that people were having problems with the settings defaulting to horrible values. Such as 0 vsync count and 10 fps. This wasn't happening to people on the team, but my assumption is that since I updated the saved settings object it is not being deserialized properly if people have old config files. My solution to this was to just change the config file's name, so that when people open the game the next time it will refresh their settings.

Upcoming

Final polish on gameplay features and the UI.


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