Enemy Collision

     When testing out multiple enemies at the same time I discovered their colliders would overlap and they would get stuck inside of each other when moving. Clearly this was a big problem because the enemies could not properly navigate and oppose the player. This would be a massive issue for an end user as seeing enemies overlap each other and getting stuck on each other would completely shatter the immersive Ness as because that's not supposed to happen.

    The way I went about fixing this was by implementing separation, which is a flocking algorithm I learned about in our AI class, between the enemies. Essentially separation occurs on impact with any other enemy entity and the way it works is by creating a sphere around each entity its checking with, determining if the distance between the entities is less than the safe distance which is determined by both adding the sphere's radius, and handling collision if any by applied a scaled vector to their position determined by distance. This will allow for the enemy to move around each other and to the player they will just see the enemies avoiding each other and staying spread out.

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