Random Level Generation

 Author: Cameron Taylor
Posted on 2/17/2022

I started working on the random level generation and my biggest issue that the time was that I wasn't able to tell if the generation was correct or not. In order to fix this I opened up my END lab and transferred over my files to start drawing the levels out onto the screen. I then had an issue where none of the rooms were connected and I had no way of detecting if two rooms were next to each other to connect in the first place. This is a big issue because if not all the rooms are connected correctly or in a manner that is solvable; then the player can't finish a floor.

The main issue that was holding me back is that I had no way to know where one room was relative to another. To fix this I used a map to store the location of a room and the output was the index inside the vector of rooms. Once I was able to store that I could generate a whole bunch of rooms all stretching out like a snake and showing proper connection points. I had a small issue with it sometimes wrapping back around on the origin point, but I fixed that. This will improve the user experience because the rooms will be completely random and crazy unique every time. I also have the ability to put in a seed that will generate the same floor layout every time (tested).

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