Corona-cation (Day 19)

Git Commit: 439d000

Git Commit: b2162a7

"Finished timer and added post process effect" & "Added time reversable cubes"


    Today took a bit of a turn from what I expected yesterday. I thought I would be working more on the multiplayer system for top-down game, but instead I started work on a game jam project. The theme being "Step back" our team decided on a puzzle game where time steps back every so often, helping or hindering you as the player. 
    I took on the job of doing the time mechanic. As far as I know, the only objects that will reverse will be the boxes. The boxes reversing will in turn activate or deactivate pressure plates opening/closing doors etc. 
    Today I started a first person project and added the timer and the boxes. The timer was very simple and is controlled by the level blueprint. It loops a timer and the timer on the player's screen will follow that timer, getting remaining time if time is going forward, and elapsed time if time is reversing. When the timer loops it will also change a post process effect volume. I plan to make the transition smoother in the future but for now it just snaps. 
    The boxes were entirely handled by this video. I don't like how much data it stores, it stores the transform of the box every tick, so in the future I would like to find a better way to do it. Maybe checking if the position has changed enough from last frame could be a start? We'll see. 


First video is when I had just finished the timer at the top of the viewport and the post process change
Second video is when I had finished the reversable cubes
Last video is a test of multiple cubes




Comments

Post a Comment

Popular posts from this blog

Polishing the Foundation

Image
     This sprint was relatively uneventful; mainly cleaning up the existing foundational elements of the game (the first person character and spell component) and continuing to improve the necessary elements of the game like the pause screen. Player Character & Spells      The improvements to the player character come in two parts; the ability to have, use, and change spells, as well as interaction via an interface. Both of theses are as simple as I could make them. Utilizing inheritance from USpellBase using the spells is only really a single line, and changing out the spells we can use the NewObject factory to make a new spell very simply. FirstPersonCharacter.h FirstPersonCharacter.cpp      As for the interaction interface, it only consists of two functions right now, one to fire an interaction event and one to check if the object can be interacted with. This second function is used mainly to show UI on the player's screen like...
Read more

Progress Update #13

Image
  Niagara Asteroids in UE4     These past few days I have continued work on asteroids. Only that now I have ditched instanced static meshes in favor of getting my hands on the new-ish Niagara particle system.  Learning Niagara     I have decided that since this is an entirely new subsystem of the engine I would do everything in blueprint first, then transition everything to C++ when I knew it was working reliably. Additionally, because Niagara is still relatively new, the official documentation is sparse if existent at all. So with most tutorials at this time geared towards blueprint implementation, starting in blueprint will give me the highest likelihood of finding a solution to any problems I may come across. The Niagara Workflow     The first thing I learned about Niagara is that the workflow has changed significantly from what cascade was. Where in cascade (to my limited knowledge) you worked in one particle system where e...
Read more

A New Chapter

Image
     This week has presented the biggest change probably since the release of Mini Solar System; I was offered a full-time position as a junior programmer at Studio 369 which I was happy to accept. I start on Monday and I couldn't be more excited to work with the team there! However, this did mean though that my priorities shifted quite instantaneously. I went from working full-time on "RPG_Game" to preparing for this new job. This mainly meant getting up to speed on networking as that is the one area of Unreal Engine I feel I have a lack of knowledge in (I'm already proficient in UI, AI, gameplay, materials, and general backend work), and since 369's specialty is networking I figured I would come prepared. I did do a little work on "RPG_Game" but it was minimal just to tie up some loose ends. Unreal's Multiplayer Framework      As explained by the Unreal Engine documentation, "multiplayer programming [is] inherently more complex than programmin...
Read more