Skip to main content

Speed improvements.

Yesterday was headache day, so no development.

Today was coding day. Found a big BUG!

I've been using a dictionary to contain my navigation data, that's to remove the need to recalculate the graph after every run of A*. I just made a deep copy of the original dictionary. I was deep copying the dictionary, then cropping the new dictionary to a bounding box around the start and finish points, by reducing the size of the graph it makes A* run faster.

Unfortunately deep copy, or even dict.copy() are very slow operations.

So while a long distance calculation of A* was taking 0.012 seconds, the deep copy operation was taking 0.12 seconds! 10 times slower than the A* function. A big drain on resources indeed. (nearly half a second for just six enemies!)

So I started by rewriting the cropping function. Now it crops data out of the original dictionary, copying entries and appending them to a new dictionary. Because it only copies entries inside the bounding area this is much faster and the resulting graph is much smaller. This takes just 0.01 seconds, much better and still somewhat faster than rebuilding the graph from scratch every time.

I've also done some work with the AI so it won't try to move if there's no route. It gets this info from the AI tactical map, though this is another area that is a little slow to calculate, but improved 10 fold since last week.

AI maps themselves are coming along rather nicely:

LOS is now calculated for each player character and also a fleeing map, so the enemies can get away to an unseen region. Archers will be able to move to a distant spot where the Player can still be seen and fire from there. If you pull out a bow and start shooting, enemies will take cover if far away, or move to engage quickly if they are close by. The more complex I make this part of the game, the slower the AI turns are going to be, so I have to find a compromise.

Again, cropping the area of calculation to include only the active players and a moderate border should speed things up. While allowing me to make the AI a little smarter. At the moment it only calculates areas which are accessible, i.e. not behind shut doors viewable. That's very fast but it means you can seal an enemy in a room and it won't move or do anything until the door is opened again. You could also avoid enemies by not looking at them. This obviously needs to be changed.

The AI maps are not very useful for the player, but they could be rewritten to use different calculations during the player's turn. LOS is useful for simulating guards, while accessibility maps can be used to make sure an A* pathfinding check isn't run if there's no valid route to that point, thus saving time.

One thing I have to look at is how opening a door during the AI turn immediately requires a re-run of the AI map generator if it makes new areas visible or accessible to the player's characters.

More experiments and refinements tomorrow.

Comments

Popular posts from this blog

Vinland 1936

What have I been up to this month?

Well you can see it in a couple of development blog videos, here, here and here.

Vinland 1936 is a game I've been working on (on and off) for about 3 years. It is somewhat based on the old Nirval interactive game, Blitzkrieg;





I hope you've played it since it is one of the best games ever!!! (IMHO)
Blitzkrieg was a real time tactics game. You didn't build a base, or spawn units. It wasn't about rushing the enemy. You got a small number of troops and vehicles that could be replenished or repaired if you had access to a supply base and the right supply trucks, but couldn't be replaced if lost. Once your vehicles were destroyed and your infantry killed you were finished. You couldn't just churn out some more from your factory and have another go at rushing the enemy guns. This made you invest a lot in each of your units. They really mattered.

It was also procedurally generated. Each mission (except for the historical missions) was…

Reboot / Remake / Restart

Although the roguelike project was going well I had a few issues with some parts of the code, and the sheer size of the project was something I could see stretching away in front of me for years with no guarantee that people would actually want to play it when it's finished.

It's time to try something a little less ambitious.
I'm going full rogueLITE!

Using a lot of the code from the roguelike project, I started making a more limited game.
There will be a single character, combat will be more arcade like, there will still be a chance to upgrade and develop your character's stats, but they represent only a single class and have fixed equipment.

I've got a fun character, an interesting setting and an exciting story lined up. It still utilizes my low poly style, but things are going to be a little more cartoony.

Game play involves mostly chucking bombs at the enemy.

But there's also a lot of platforming, jumping from multiple levels is part of the game. And you ca…

Telling a story; Creating a Compelling Narrative.

Telling a story; Creating a Compelling Narrative. In this blog I will talk about my own recent brush with story telling and go on to talk about how tools from creative wring can help you to better author the narrative in your games, whether they have a traditional linear narrative or a procedurally generated interactive narrative.

Narrative and structure in traditional fiction  last week I started writing a story set in the world I'm developing for my game Vinland: 1936.

I hope the story will help me to flesh out my game world and develop my own expanded universe which will be a good place to set my games in the future.

After about a week of work, on and off I've progressed the story to outline stage. For each character thread I have half a dozen chapters which plot a course through the events of the story. Each thread is told from the perspective of a different character.


Actually I started writing as soon as I had my outline, but I've since gone back and deleted what …