Refactoring Renderer and Central Processing

     The problem I faced when working on refactoring the Renderer and Central processing is a really bad race condition that causes random crashing. This is obviously an issue as it prevents the functionality of the game. The race condition is caused by multiple segments of the engine, likely within Gateware or within the audio library. The random crashing is never within the same part of the engine, although the most common sections are within the Renderer itself, which was recently switched over to a singleton system.

    This problem hasn't been fixed yet, but is currently being experimented with. Possible solutions that have been tested include ensuring that all data related to Gateware is initialized at the same time, sharing pointers, etc. So far, none of it has worked, although there is a chance it could be resolved within a couple of days. I am going to discuss this with professors and other programmers to see if they can see where the problem is, but it isn't obvious where it is.

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