Level Randomizer Integration

Author: Cameron Taylor

 My beginning issue with the level randomizer is I needed a way to view it in the world so that I know what is happening instead of just looking at raw code. To achieve this I set up the entire header and cpp in another engine so I can easily render everything I need into the world. The problem came when moving both files over to the project because I had to convert from float4 to gateware vector. This isn't too difficult but gateware needs proxies for things and has way less math operations than normal END typedefs. I then also had to integrate this more with Pedro's collision code to bring collision into my handle/update and figure out when the player collides with the door.

As I said above I spent a good amount of time transferring all the data types over to gateware. I then spent easily 3 hours working with Pedro figuring out how to sent signals back and forth without including each others headers in our own headers. We did this by using the instance of each others headers and when needing to retrieve information we would send a signal to the others instance saying "hey we need info" and then they would send it themselves. Dirty workaround but it works well and no issues at the current moment. (Doubt there will be more issues in the future too). After doing all of this the player can now walk around room to room correctly and pressing 'U' in debug mode randomizes the floor and the player can walk around it and explore freely.



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