Peter Eldredge PPJ # 8

Settings Menu Button Rework - 2 Hours
New Victory and Defeat Screens - 1 Hour
Object Pooling System - 1 Hour
Misc Unity Tasks/Help - 2 Hours

Settings Menu Button Rework

I redid the way changes were applied in the Settings menu. Changes no longer take effect until the "Apply" button is hit. If you back out of the menu your changes will not be saved, and then upon re entering the menu you will see the last applied settings. When the "Revert" button is hit, the settings will be reverted back to their default values from when the game was loaded for the first time. Its possible it should be renamed to "Default".

This involved quite a bit of reworking to the menu, but now it is significantly more modular than before and relies on an event to update itself.

Additionally, the settings can now be tied to the post process profiles in game, in this case, the motion blur is now working.

New Victory and Defeat Screens

The UI for the Victory and Death screens was redone. They now have a bit more data and look better, although I would like to add some movement to them at some point. Its a decent start though.



Object Pooling System

I also finally got around to adding an object pooling system, which I guess unsurprisingly greatly improved performance.

It is a pretty basic implementation that favors performance over perfect accuracy. You can set the enum that is used to reference an object, the prefab that is instantiated, and the number of objects in the pool. These are added to a Dictionary that has a key of the enum and a value of a Queue referencing the pooled objects of that type.

When a pooled object is requested, it is dequeued from the list and then immediately enqueued. The consequence of this basic pooling is that if more objects are requested very quickly, as in quicker than the pooled objects deactivate themselves, then you could run into an issue where the received pooled object is currently active. This isn't a big issue, but I may end up implementing a solution anyway. I do like how fast this is, on every level I get performance gains of 50-100%.

Upcoming

I want to add more movement to the UI and improve the behaviors for the incinerator bot. Other than that just continue polishing and improving performance.



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