Weapon system refactor

   Author: Daniel Jackson


  The weapon system as it was functioned perfectly well however anytime anything weapon related was needed, a series of functions needed to be called. In the short term (and to get things off the ground) this was fine however doing these function hundreds of times a second adds up and gets expensive quickly. Because of this when the weapons are fired, even the least expensive weapon, there is a significant drop in frame-rate and while at the moment it's not noticeable it could hurt the final project later on.


    To alleviate the strain of the multiple function calls, I've been working on refactoring the weapon so that each weapon is it's own struct containing the appropriate values for the weapon. Removing the need for function calls entirely, now we simply access the struct and grab the values directly saving us at least roughly 40 frames while the weapon is in use. Additionally, using this new system we can add any extra effect to any weapon we choose at any point.


(list of functions needed for our simplest weapon)


(One struct that can be used to access or add features to any weapon)
(colloquially named Jim)




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