Linker Errors and Merging

 Cameron Taylor

When I was trying to integrate new code for the project I needed to include different OOP classes so that all the information can be shared correctly. The first issue is that three of us were putting the includes in the header file when we needed those files and this worked fine for the time. The second issue is that we weren't completely communicating with what was being included. This combined together was a mess I needed to solve by moving tons of includes into the cpp files and moving some functions around so that everything could work smoothly (although build time is still slow). This issue mainly came to light when I needed to merge with other branches too.

Like I said above the way to solve these issues was to move the includes into the cpp file. I also made sure that nothing was including intermediary that intermediary was also including since this was instantly making so many things crash. Then when merging I just brute force fingered through the code and figured out what was needed and what wasn't. This obviously took more time than I would have liked, but in the end got everything merged and then had the person I merged from pull back from me without any issues.

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