Jump to content
  • entries
    165
  • comments
    199
  • views
    85,271

Let's Make a Game - Procedual Content Creation (part 01)


Flexman

10,241 views

 Share

blog-0524079001335886426.jpgAbout: This is a short series for the Leadwerks community on the process of creating a simple game using procedural content.

 

A short while ago I was approached to write a book on terrain generation using dedicated tools for a variety of game engines. There's a lot more to game content than just terrains. Josh's recent blogs on CSG got me thinking about one of my favourite games and had me itching to re-visit the genre.

 

 

 

This series is an exploration of topics I don't normally exercise but are fun to do. Leadwerks is a fun engine that's ideal for prototyping ideas. So throw out your terrain system, we're going to make a game all about claustrophobia. We're going DOWN into the tunnels to blow stuff up Leadwerks style using a mix of old-school gaming know how and modern day 3D.

 

Our goal: create a simple six degrees of freedom shooter set in a procedurally generated network of rooms and corridors. You can use this as the basis for a number of different games but as I'm a fan of the old classic shooter "Descent" and it's easy to create a physics controller to fly around in Leadwerks. Also it can be re-worked using Leadwerks3Ds CSG functions when it's available.

 

 

Procedural Map Generation

 

Dungeoneering is back in gaming news with Legend of Grimrock, a take on Dungeon Master grid based geometry. Many games are based on grids, they are easy to work with and often form the basis of AI routines. They are also easy to generate geometry for. There have already been numerous articles and blogs on creating such levels, you'll find links at the bottom of this article.

 

True Story: The Survival horror Amiga game Xenomorph copied the same gridded dungeon mechanics in a blatant rip-off of the Alien universe where stone walls were replaced by ship corridors. Coded by an ex-Microprose employee I visited his house somewhere in Devon many years ago. He revealed that many of the game objects I clung onto for dear life had no function whatsoever. Lesson learned: Don't explain everything, keep the mystery, it's dishonest but more fun for the player.

 

But before we look at some LUA code to create geometry we'll first have a taster of different techniques used in creating random level geometry. After that we'll kick things up by adding more vertical elements for our demo game. I warn you in advance, I'm not a LUA expert and nor am I a big fan but I'm sure you good folks can make it better and LUA brings the examples to the widest possible audience.

 

 

 

Node based grid

 

Our goal is to create a collection of rooms connected by corridors through which we can explore. A simple approach is to seed a random number of nodes (rooms) and connect them up. There are other methods, such as a corridor based approach which adds rooms in a second pass, such a method is used in the classic DOS game HACK (aka NETHACK).

 

For our examples we'll stick to a 40 x 40 grid to keep it simple. Each grid square could equate 100 world units or 10 in Leadwerks, it doesn't matter as long as we use a consistent scale. We'll stick to 100 units (1 unit = 1 meter) per grid square for this example meaning our potential map is 400x400 units.

 

blogentry-52-0-64637600-1335865399_thumb.png

 

Here each node represents a room of random size. We can restrict the size of the room to fit within its parent grid to make it easier to deal with problem of overlapping rooms as illustrated in the figure below. Eventually we'll construct the geometry to build these irregular shaped rooms so they merge as a single entity.

 

You can see that choosing the size of rooms will impact on how much corridor space you're going to end up with per map. This is something you can set in code easily giving control over how open or closed your level will feel.

 

blogentry-52-0-13979700-1335868221_thumb.png

 

If we stick to the grid arrangement connecting them by corridors becomes an easy process. The difficult part is constructing the vertices and triangles to fit together nicely but we'll get to that. By far the easiest way of joining rooms together is by joining them at the cardinal points of the room. While this makes logic easy it also makes for a pretty boring layout. What's more, there's no reason why a corridor has to be of fixed width...or height.

 

A room typically connects to a room in a neighbouring grid using the straightest link possible and we'll dog leg corridors as required. To add some interest we'll create a 'route' through the grid and randomly connect to neighbours.

 

Again there are many ways you can do this and I encourage you to try your own variations. Our rule-set will have a random chance of connecting to a neighbour if that room. That chance will degrade if that room overlaps and on the number of existing corridor links. Hopefully our final 2D layout will approximate the figure below.

 

blogentry-52-0-22002700-1335871116_thumb.png

 

Then each room can add its own flavour by adding columns, point lights, props, whatever fits your game.

 

Once we've got a class to generate the map we can then move on to generating the required geometry (surfaces) so we end up with something looking like...

blogentry-52-0-42470900-1335883889_thumb.png

 

Things get even more exciting when we'll extend these maps into 3D, with vertically offset rooms and corridors. Eventually we'll have a complete base generated by a single random seed you can fly, shoot, leap, run through with a basic controller.

 

Once we make the logic for generating rooms 'furniture' props can be parented to the room mesh to take advantage of culling. I'm not going to add much in the way of occlusion, instead Leadwerks can take the stain and should do a good job with no effort on our part.

 

In part 2 we'll start with some code to generate the above with geometry directly in the Leadwerks editor and we'll be using Vertex and Surface commands to create rooms which look like the screen-shot below.

blogentry-52-0-70559500-1336048063_thumb.png

 

Random room generation in LUA, corridors coming shortly for part 2

blogentry-52-0-66205600-1336077351_thumb.jpg

 

 

Everyone is welcome to contribute.

 

 

External Links

 

Procedural Content Wiki

Generating Random Dungeons
  • Upvote 3
 Share

7 Comments


Recommended Comments

Procedural content generation truly is the future of indie game development. Not having to worry about artists for your props, level or even characters would give developers a huge boost in base assets, and perhaps help unlock funds with the added credibility for future specific assets in their game or software.

 

I have a tree generator side project that I develop when I get time off school and other work. Here's a screenshot for the curious: Procedural.png

  • Upvote 1
Link to comment

One of my favorite free games, Spelunky, is procedurally generated. Binding of Isaac is the same and it was tempting me a lot to create something similar in 3D. Maybe one day...

Link to comment

It would be going up this weekend, got some booky stuff to get out of the way before tomorrow.

 

I'm having some code issues with getting the corridor geometry joining with room walls. There's an interesting TSurface.Slice(...) command that's not exposed in LUA which I'm guessing is a helper function in 3D World Studio. That might have been interesting to play with.

 

Put some AI robots in the rooms to shoot at you, add some laser guns and power ups then you're good to go.

Link to comment
Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...