Controls rekeybinding

 Author: Cameron Taylor

How I originally made the system I made every key press hardcoded with a certain outcome. For example, when pressing WASD the player would move in coordinal directions throughout the game. The problem with this is people like to rekeybind and therefore I needed to make a menu for them. The biggest hurdle I needed to overcome is making a map to comprehend an input key with the correct action. I also needed to display what key they had selected/bound so they know for gameplay.

The way I accomplished the rekeybinding is is by making two maps (translators) to tell the system what key was going in, and what that key needs to be interpreted as. This took a lot of work since I initially needed to hardcode every key input to their respective output in our system. Then it was all up to the player to reassign each one through the settings and that would then automatically update in the code since I was using translators instead of hardcoded values.

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