Pause Menu, Shield, and Settings

 Author: Cameron Taylor

The old pause menu was hardcoded locations for the buttons and all it had was resume and exit. The exit button brought the player back to the main menu and didn't actually close the game. The first issue I needed to overcome was adding 2 new buttons and have the buttons the side of the image. I also needed to add a bunch of new states to the pipeline to know which window I was on. This is important because the state of the game determines what we display on the screen. For the shield I ended up copying the health bar and decrement it the same way the health is done. This is an issue though because the code was never fully tested so the bar never went down all the way and displayed the incorrect amount of health and shield. I also had trouble keeping the slidebar inside the bounds since I needed to constantly update the mouse position and compare to make sure it's inside.

I ended up splitting more of the pipeline into different parts so that only certain buttons were clickable during certain states of the game. To fix the shield (and also the health bar) I had to completely rewrite the code to scale the health between (current health / max health) 0 and 1. This was really difficult to then transfer into a -1 and 1 value for NDC coordinates. And for fixing the slidebar I needed to constantly compare the position of the mouse with the outer bounds of the bar using the middle position and extents and then stopping the slide if they go outside the bounds.


Comments

Post a Comment

Popular posts from this blog

Adding assets to every enemy -- Owen Meyers

Image
      As with every game, it is very important to have assets to denote which enemy is which. Being able to tell at a glance what enemy you are encountering before receiving a face full of buckshot is incredibly important. The issue for Project [REDACTED] is that we didn't have any artists working full time to deliver assets for the enemies. Thus, it fell upon me, the designer of the asset pipeline, to acquire assets for every enemy. This led to having to fix models and integrate animations, with each problem being subtly different.     Take, for example, the shotgunner model. His original model was designed for an OpenGL renderer, and was flipped 180 degrees for that very reason. In addition to this, he was also placed halfway in the ground, likely due to something required for that game's collision to function. Fixing this model to function for our renderer required that it be re-rigged and most of the animations acquired from Mixamo. With the help of Kris, and several hours
Read more

Sphere to AABB collision

       I had a problem today when trying to detect sphere to AABB collision. For some reason the collision check that I made was never turning true even though I could clearly see the sphere hitting the AABB. This was a big problem as we needed this collision to detect whether any entities are hitting walls.     I discovered that the problem with this bug was that I was improperly getting the closest point in the AABB to the sphere. The way I fixed this problem this problem was by getting the max vertex that the circle center could be and using that to get the closest point on the AABB to then determine the minimum vertex between the sphere's max vertex and the max of the AABB.  Once I found this point, I could properly compare the distance of that point to the center of the sphere. This solution will allow detection between walls and any sphere collider such as the player collider, and enemy collider. This is very important to make sure they both stay within the level bounds.
Read more