Skill Tree Functionality

 Author: Cameron Taylor

I needed to make the skill tree so that the player didn't have the same weapons throughout the entire game. This also functioned as a store for unlocking new weapons. I constantly ran into an issue where resizing the window broke everything. This is because the assets would be drawn with premade values on the screen from -1 (left side) to 1 (right side) of the screen. That means when you resized the screen to make it wider then the width of the texture is now more pixels. There was also an issue where no texture could change color. They were all green and there was no easy way to tell if one was purchased or not.

To fix the resizing issue I needed to constantly check the width and height of the screen and compare it with the previous width and height of the screen just a frame before. Although this happens every frame the comparison doesn't hurt. If they were different values then I knew that the screen size has changed and that triggered remaking all the assets to be done. I would need to grab the new width and height and remake the assets qiad values to still be between -1 and 1, but since the screen is bigger/smaller the numbers need to be different. To make the buttons be greyscale and then change to a green texture I needed to hook into the shaders where rendering is done and manually greyscale the texture if I tell the pipeline that the texture is not unlocked.



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