Procedural Dungeon Generation - Revision history

Talad at 20:39, 11 September 2024

2024-09-11T20:39:53Z

← Older revision		Revision as of 20:39, 11 September 2024
Line 1:		Line 1:

	=== ~~Homemade~~ random generator ===		=== PlaneShift random dungeon generator ===
	'''Core System:'''		'''Core System:'''

Line 45:		Line 45:
	* check for overlaps, if it overlaps try another room, max number of tries, then change connection		* check for overlaps, if it overlaps try another room, max number of tries, then change connection

			=== What happens at runtime ===
			1) We have a sub-level called "DungeonGeneration". In this level there is an objects called "DungeonOwner1". When the level loads we store a reference to the "DungeonOwner1" in a variable for later use.

	~~'''To check~~:~~'''~~		2) A GM creates the dungeon with /dungeon or with the /dungeon window command. In the window case we go through APlaneshiftPlayerControllerBase::RequestCreateDungeon(), which then calls the /dungeon command.

	* Navmesh generation. ~~Spawn~~ one navmesh covering the total area where we generated the rooms~~, and trigger the recalculation~~.		3) This will call AdminManager::DungeonGeneration() , it retrieves the "DungeonOwner1" and use it for location and ownership when spawning a new "DungGenStart_BP".

			4) "DungGenStart_BP" is a blueprint which holds all the possible configurations to use in the generation. This object is instantiated

			=== Open Points '''NavMesh:''' ===
			* Navmesh generation is possible only if the whole world has dynamic navmesh generation. UE doesn't allow at the moment to have a mix of static and dynamic navmeshes.
			*For dynamic generation we could spawn at runtime one navmesh covering the total area where we generated the rooms.

Talad at 15:29, 4 February 2024

2024-02-04T15:29:17Z

← Older revision		Revision as of 15:29, 4 February 2024
Line 14:		Line 14:
	**Add a simple Box Collision object, which is covering the whole room, will be used to activate and deactivate traps when the player enters the room. You HAVE to TAG this actor with "trapsActivation"		**Add a simple Box Collision object, which is covering the whole room, will be used to activate and deactivate traps when the player enters the room. You HAVE to TAG this actor with "trapsActivation"
	**Add NPCs using UDungeonSpawnComponent and set the custom attribute "Spawn Type" == NPC		**Add NPCs using UDungeonSpawnComponent and set the custom attribute "Spawn Type" == NPC

			=== Configuration ===
			Configuration is done on the Dungeon Start object BP.

			[[File:Procedural Dungeon2.png]]

	=== '''Randomization''' ===		=== '''Randomization''' ===

Talad at 15:26, 4 February 2024

2024-02-04T15:26:58Z

@@ Line 1: / Line 1: @@
-* If you want to do it in an actor, you need a Collision Box inside the actor , so the engine can determine the overall actor size.
+=== Homemade random generator ===
-=== Homemade random generator ===
+=== '''Randomization''' ===
-'''Good ideas:'''
+*For each connection we spawn another room and connect it
 '''Placeholders:'''
@@ Line 38: / Line 44: @@
 * Navmesh generation. Spawn one navmesh covering the total area where we generated the rooms, and trigger the recalculation.

Talad at 22:32, 14 January 2024

2024-01-14T22:32:13Z

@@ Line 1: / Line 1: @@
 * You need to position your initial volume with snap to grid 100, otherwise if you are in non step position you will get a different number of points generated.
 * We need to use Transform Points to move the offset of our generated points back to the 0,0,0 position of our volume. In our example we had to use 50,50,50 as both min and max offset.
@@ Line 6: / Line 7: @@
 * If you want to do it in an actor, you need a Collision Box inside the actor , so the engine can determine the overall actor size.

Talad: Talad moved page PCG Procedural Generation to Procedural Dungeon Generation without leaving a redirect

2024-01-14T21:52:55Z

Talad moved page PCG Procedural Generation to Procedural Dungeon Generation without leaving a redirect

← Older revision	Revision as of 21:52, 14 January 2024
(No difference)

Talad: Created page with "* You need to position your initial volume with snap to grid 100, otherwise if you are in non step position you will get a different number of points generated. * We need to use Transform Points to move the offset of our generated points back to the 0,0,0 position of our volume. In our example we had to use 50,50,50 as both min and max offset. * In the chart we use: Get Actor Data -> Volume Sampler -> Transform Points -> Static Mesh Spawner Volume Sampler has 100,1..."

2024-01-11T23:47:51Z

Created page with "* You need to position your initial volume with snap to grid 100, otherwise if you are in non step position you will get a different number of points generated. * We need to use Transform Points to move the offset of our generated points back to the 0,0,0 position of our volume. In our example we had to use 50,50,50 as both min and max offset. * In the chart we use: ** Get Actor Data -> Volume Sampler -> Transform Points -> Static Mesh Spawner ** Volume Sampler has 100,1..."

New page

* You need to position your initial volume with snap to grid 100, otherwise if you are in non step position you will get a different number of points generated.
* We need to use Transform Points to move the offset of our generated points back to the 0,0,0 position of our volume. In our example we had to use 50,50,50 as both min and max offset.
* In the chart we use:
** Get Actor Data -> Volume Sampler -> Transform Points -> Static Mesh Spawner
** Volume Sampler has 100,100,100 for Voxel size

* If you want to do it in an actor, you need a Collision Box inside the actor , so the engine can determine the overall actor size.