Skip to main content

Side Projects V2.0

I've been working on a number of side projects recently, so no actual work on Treasures of the Deep Dwellers.

However all but one of those side projects have been aimed at testing some ideas with a view to restructuring the project or developing key components which were missing.

When I finished working on the most recent version, it felt like I was nearly ready to put out a demo... but after trying it out for a while I wasn't satisfied. Movement calculation was too slow, the characters and AI were too complicated and not well designed. Adding to them was becoming too much of a chore. And there was something wrong with the pathfinding...

I took part in a game jam and had the opportunity to work on an FSM (Finite State Machine) for character management. The version I designed for the competition was a little limited because I didn't use classes, I had to define all properties for all states at initialization of the game. The result was pretty messy, but it worked much better than the simple Boolean if/else models I'd been using up til now.

I took that idea and used it with a platformer demo which later morphed in to a point and click adventure game... This time I took the time to investigate using classes as part of an FSM.

After some experimentation and some tips from a fellow programmer I had something that really worked. The result was much tidier, much more comfortable to use and expand, used less code much more efficiently... all round it made my previous character code look like junk.

So it seemed it was time to start over.

But before returning to TOTDD I also took some time to develop a multiple choice dialog system, for handling NPC conversations. It includes an editor which allows me to build conversations using a nice object based interface.

There's also support there for semi-random and procedurally generated dialogs...

Back on the project I started by taking some old code and updating it. I was surprised to find a huge error in my A-star pah-finding code, namely that I had left out the "f" value completely because of a typo. I was using only "h" to plot the best course. Sometimes taking a break from a project allows you to go back and fix things you didn't even know were broken. In this case the algorithm was still finding a route, but it certainly wasn't the fastest one. My path smoothing code was covering that up however, so I didn't notice.

I did some work on blocking objects too, reducing the drain previously caused by checking for a blocked route from every node to its neighbor. I found a quick way to check for blocking by only comparing each node to a bounding box of the blocking object.

As well as all that I started using objects (classes) to represent the walk mesh nodes and neighbor links, this allowed me to write an update() function which quickly resets all the g and f values in the graph each time the graph is reused.

The resulting code is much cleaner, faster, and calculates a better path.

The remaining side project is sadly likely to further reduce the time spent on this project, little Henry, my second son was born just three weeks ago.

Right now things are crazy busy at home and I get maybe an hour a night for coding and other things after everyone has gone to bed. That doesn't mean I'm going to stop working on the project, without some kind of creative outlet I'm sure I'd go crazy! But family comes first so expect slower but more focused development of the project for the future.


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 …


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 …