Week 6-7 A Closer look to the Preset pieces alignment.

Week 6-7 A Closer look to the Preset pieces alignment.

Something I had in mind when first drafting the algorithm for the PGL was the ability to set certain rooms  in certain areas within the labyrinth.
After the completion of the rooms attaching and not overlaping each other, I moved onto the part of including the prep-laced pieces.
It is worth to mention that even the pre-placed rooms are not in a constant location but are instantiated within an area set by the user.

To set the preset pieces you drag the room to the inspector, set the area dimentions and location where you want it to spawn.
I had initially thought to look for open exits close to the open exits of the pre-placed piece and then create a corridor connecting the two exits. But that in its own creates a few new problems:
The corridor connecting the two rooms would need to be curved so it would not collide with the rooms and keep the distance of the corridor equal at all points. Also the creation of a code generated corridor might not be up to the same standard of our custom made rooms.


I initially thought to follow the brilliant video above to create a spline based corridor, but realized it would need a lot more coding and still not look good. Though it is something that I can see been added in a later version of the PLG. So I thought of a simpler solution, when i randomly place the preset room in its area no one really knows were it is set. So I place it randomly and replace again to attach to an existing exit.

The way it works is the following, after we have checked that the new room we attached does not collide with others, and after we have removed exits that are outside the level's dimensions, we check if any of the rooms remaining exits are withing X distance to any of  our preset pieces exits.
if it is then we move the preset piece and remove the 2 exit points. Incredibly simple after you realize that you are allowed to remove the randomly placed preset piece.

Comments

Post a Comment

Popular posts from this blog

Player stats and brightness.

Image
Player stats and brightness. Last week I worked a bit more on the player characteristics, decided on min max values, and did the same for the Enemy stats. I split the visibility factor into 2 values, brightness and motion. Motion will be affected by the movement of the player and the movement in the headpiece and controllers. Brightness is a factor indicating how well lit the player is. So the enemy has skill values for detecting motion sound and smell, it also has a detection generic skill value which is linked with the enemies intelligence. So any light source will have attached a brightness script that triggers and sends a brightness value to the player brightness when the player is in range and increase as the player comes closer to the light source. The player value of Brightness is for now a static value, so multiple light sources can affect it. I still need to cast a ray cast from the light source to the player, if it fails to hit the player then that would indicate that ...
Read more

Testing the PLG

Image
Testing the PLG Before I get into the testing section Progress on the tasks remaining Place restrictions on all controls in the room generator editor. So you can't place the replaced rooms outside the level and the scan lines. DONE Fix some conditions in chance the quarter can not find a theme room or it the two theme rooms are too close. *I have decided to ignore this and come back to it if i have time after the documentation. Place the furniture , loot and enemies into the level.  Scan the area and store the points that were hit. - this is for demonstration purposes to show how many times that area has a tile placed, to demonstrate how different the levels are. DONE  Store the seed number, the number of tiles used, the  distance to reach the exit and the exit room location DONE So tomorrow I start working on placing the enemies and loot into the level. Testing Today I ran the PLG in a sequence of 40. I have also added 3 functions at before the PL...
Read more

More work done on the interface, saving data.

Image
More work done on the interface, saving data. I would have liked to say that I started on the loot and enemy randomization, but that is not the case. What I thought would be an hour work job took me half a day. I have now finished with the way the randomizing feed is stored. When a level is complete (PLG state is -off) two buttons appear in the inspector allowing the user to store the seed in a whitelist of black list. When the time comes to generate the level the user has a larger option of choices:  Generate a completely randomly level.  Generate a  completely randomly level but it will never be one of the levels we blacklisted (if we tick on use black list). Generate a specific level from a ID we enter. Load a random level that is included in the whitelist. In order the randomization between levels within the list to be equally random before storing the lvl ID we load the current values and check if the Id already exists, if it does then there i...
Read more