Skip to main content

Navigation Arrays and Navmeshes.

Today I worked on the prototype navmesh for the game.
Most 3d games use a navigation mesh, it's easier to store data about where you can walk in a mesh than in text arrays, the mesh can also be edited easier than rewriting an array.

Unfortunately with a random dungeon the different sections have separate navigation meshes, and in Blender you can't merge the meshes. So in this project I'm using the meshes to generate the list of walkable tiles and then they will be deleted and the data will be kept as an array. I'll be using simple neighbor checking to create a graph that can then be used with A* pathfinding.

It's all very old fashioned, but for me it's interesting to use these methods because it allows me to understand what's going on at a very basic level. I don't really expect to improve on modern AI but I can find what's good for my project and leave what I don't need.

Here's the walkmesh:

You can see the red areas are walkable, the green areas are a negative mask, I'll be using green walkmeshes to show where you can't walk. They'll be added to props to override the existing walkmesh when the prop is added.

Actually thinking about it, green for don't walk and red for walk is kind of counter intuitive. :)
Have to change that in the next update.

Here's a closer look:

The result is a a set of dictionaries, one for each tile. I'll be accessing the dictionaries separately when building the graph for A* so I don't have to access the whole set of data, hopefully speeding up performance a bit. Tiles which are out of range of the character's movement range will not be added to the graph. Characters will pathfind to a selected square inside their move radius, but it's up to the player to do long distance pathfinding each turn.

The AI will at first try to generate a path to the player using a cropped rectangle around the position of the player and the monster. If it can't reach it will expand the search area. This means that in some cases the A* routine may need to be run twice, however, in most cases it will work the first time, using much less resources than a full level graph.

I'm also thinking of doing a simple flood fill at the beginning of the AI's movement phase to find which players are accessible, or which are on islands (in a locked room for example).

Here's a quick video that shows the unfinished result:

Comments

Popular posts from this blog

Make your game models POP with fake rim lighting.

I was watching one of my son's cartoons today and I noticed they models were using serious amounts of simulated rim lighting. Even though it wasn't a dark scene where you'd usually see such an effect, the result was actually quite effective.



The white edge highlighting and ambient occluded creases give a kind of high contrast that is similar to, but different from traditional comic book ink work.


I'll be honest, I don't know if there's a specific term for this effect in 3d design, since my major at university was in traditional art. I learned it as part of photography.


You can find plenty of tutorials on "what is rim lighting" for photography. It basically means putting your main sources of light behind your subject so that they are lit around the edges. It can produce very arresting photographs, either with an obvious effect when used on a dark subject...


..,or as part of a fully lit scene to add some subtle highlights. See how alive the subject look…

How to... build a strong art concept.

So you want to make some art assets for your game. The first on the list is a Steampunk Revolver for your main character to shoot up Cthulhu with. Quickly opening your internet browser you start with a Google image search. Ah, there is is!

It might be a good idea to find a few influences so you don't accidentally end up copying a famous design.


Just mash them up and you're ready to go! Off to your favorite modeling program.
But wait! isn't there more to building a strong design concept than that?

Of course there is.
One of the diseases of modern design is that of recursion. Everything is a copy of a copy of a copy. This is especially a problem with "historical" concepts. Over the course of that recursive process the concept becomes infected with modern design elements, and ends up looking very similar to everything else that anyone else has ever made.
If you want to come up with a really fresh idea, you have to get beyond secondary references and go look at real …

Skynet

Ok, so it's not exactly skynet, but I have got my first AI state working, kind of.


The first state is "HOLD" in which case the agent stays in place where they are and shoots at any unit that comes in range. When I started writing this module, I found that the existing method of triggering actions wasn't good enough to allow the AI to choose the best weapon or target. It worked by simply sending a command to the unit to trigger the currently selected action.

If the action is valid, it triggered, if not it didn't.
That's fine for play controlled units, as that's all they need to do. But AI needs to know in advance if the action is valid. The player can get that info from UI feedback, but that wasn't available to the AI player.

There were three problems:

1. The UI feedback duplicated code in the action trigger function. These  two sets of code could get out of phase so that UI feedback was wrong.

2. The action trigger didn't give enough feedback for …