Skip to main content

Radial menus

A lot of work this week, but you can't really see any of it.
I've been setting up the interface between the player and all the controls. Now I have a way of entering any kind of command I need in a way which is (IMHO) pretty easy to get to grips with.

Here's the early concept:

[radial menu with two levels]
This was my first concept, that you would use the radial menu to switch to a non-game state and from there you could use direction keys and space to set up various parts of the game.

But I thought it would be better if the radial menu could be expanded with multiple layers to handle things directly in game without entering a non-game state.

So now you can control the camera, perform actions and feats, give orders, switch characters, set default AI behavior and other things right in the game.

[8 level radial menu]

And all layers lead back to the main layer, so hopefully you can't get lost in the menus.

Some interactions though still need to enter a non-game state. For example organizing your inventory or resting and eating.

In that case you'll still be able to use the radial menu to exit back to the game. it will always be there.

The radial menu looks kind of crappy right now because it's just a placeholder. Later it'll have proper graphics and probably have special icons.

[like this]

For now I'm concentrating on getting a game that works, then making it look good later.

[Try to think around the problem]

A few days ago I was stuck with a big task to do and nothing small which I could work on until it was finished. These kind of bottlenecks in development are a real problem for me, since I don't get a lot of time for the project and it sucks to get half an hour but not be able to do anything. That's just not enough time to clear the bottleneck and it only confuses things to leave a task half completed.

Anyway, now the menu structure is in place there are a million ways in which I can move forward, many of them will take less than 30 minutes to do, so I can be more productive and less stressed by the project.


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 …