Speed Improvements Again.

I've already gained some speed improvements from how I'm handling dynamic blocking objects, but I wanted to revisit some of my older code and see if I could clean it up a bit.

One of the things I was doing before to make faster calculations was to strip the A star graph down to a bounding box around the start and end + a small border. Actually this turned out to be slowing the code down once I reorganized things. The only time this would speed things up is if the map were really huge, the start and end locations were really far apart and every room on the map was open... So this got dropped for now.

I was doing some esoteric things with getting the nearest node in the graph for a start and end point, which was almost taking longer than the A star search (on short routes)! So that got cleaned up. The route smoothing pass cleans that up anyway.

Here's the end results for comparison:

Almost a 50% reduction in some cases. It may not seem important but once there are multiple units in game starting to pathfind around the map, a 50% reduction in time taken to calculate paths is going to be quite a big deal.

It now looks like the code is ready to move forward again.

Comments

Advice needed on tilesets...

I need some advice on which is the best way to handle building the dungeon. Right now I'm using prefabs for my dungeon, they have a north south east and west section for each "room": The basic tileset. This has several advantages, and also several disadvantages. Firstly I can have curved rooms, I can have tunnels and other interesting shapes. The tilesets can look quite nice with a little work. On the other hand I can't easily get the navigation data before building the map and once the map has been built I can't make changes to the layout, like having active pit traps or believable secret doors. Although the rooms are interesting, they are quite repetitive, and it takes a lot of effort to make even a few different variations. Also rooms are constrained to one size. A newer version of the tileset with a lot of variant parts for making more interesting rooms. To create a tile set is a real headache too. Planning how to lay out the UVs, trying to cra...

Upstairs / Downstairs.

I've decided to make my prefabs multilevel. Later this should allow me to add pit traps and other great stuff. It also makes it easier to line up stairs so that you can exit them on the same co-ordinates where you entered them. The prefab editor is pretty much finished, it just needs some code for loading up prefabs from a saved dictionary, so that they can be checked or edited. The entries will need to be forwards compatible, so I'll be loading each tile and then translating the indexes to a new array, that way if I add extra indexes or extra info (like traps or puzzles) I'll be able to update existing prefabs to work with the new standard. Click for a video.

Video Diary 8

Things are moving along well, there's been a lot of progress on the action manager side of things. Actions have finally moved to the UI, so you can initiate actions by clicking the appropriate button. I've set up some dummy actions to show what happens visually when actions are taken, but the actual dice rolls and such are yet to be integrated. The UI objects are also being added, though some are non functional or empty at the moment. Click on the image to see this week's development video. Every time I add something big I also add about a dozen small things. Like the selection box visualization. Previously this was using render.drawline, and old fashioned Blender function which can be impossible to see at certain resolutions, or at certain frequencies. I replaced it with a function that adds planes of the right size and scale in the right location. I also made all characters a little bigger. I still need to do some work with vectors and final target locations t...

Pickledtezcat Game Devblog

Search This Blog