Skill Tree tabs and Weapon HUD

 Author: Cameron Taylor

Although a single tab in the skill tree worked, I needed to make every tab work. An issue I ran into right away was that every asset was layered on top of each other. I also had to split up the buttons into their own chunks of code so that overlapping buttons that were in the same space wouldn't be clicked unless they were enabled through code. I also had an issue with displaying the correct currently displayed weapon and ammo count since the current pipeline would display any text given at it.



To fix the layering assets I needed to attach and ID to each asset so that the render pipeline would only display them if I told that renderer that we want to display that ID. I then added switch and if checks into the update code that runs every frame so that only specific text will be added to the pipeline if a certain weapon was equipped. This is a sneaky way to fix it instead of keeping all code on the GPU at all times, but it works fine and runs very fast still.








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