Overcrowded is nearly ready for release. COVID19 sucks.

What Did I Do In 2019?

In my last retrospective I talked about releasing Fancy Folders, beginning development on Overcrowded and getting into the Starbase community.

Placeholder Software

This year we’ve released 11 updates for Dissonance with a number of improvements:

  • Fixed strange inspector behaviour when editing prefabs (due to a change in how Unity handle prefabs)
  • Fixed the editor crashing when inspecting the AEC filter (due to a Unity bug)
  • Fixed muted players not being unmuted instantly
  • Fixed an issue that could cause voice packets to be dropped or long periods of time!
  • Dropped support for Unity 2017.4
  • Improved VU meters in inspector
  • Removed support for spatializer plugins (due to a change in Unity)
  • Improved precision of audio sync system
  • Improved audio quality in poor network conditions
  • Improved Automatic Gain Control handling of silence
  • Added better support for custom microphone systems
  • Released a free integration with NatDevice
  • Added support for Windows+ARM64 (e.g. Hololens 2)

As you can see there haven’t been any huge changes this year. At this point Dissonance itself is quite stable and most of the changes are small improvements to a specific subsystem or fixes to workaround issues in Unity! I’m overall pretty happy with how Dissonance is at the moment.

We’ve also released 3 updates to Wet Stuff:

  • Fixed a loading loop that could lock up the editor (due to a change in Unity)
  • Fixed an ArgumentOutOfRangeException in the instanced rendering system
  • Removed some (harmless) warnings that were confusing users
  • Added a warning about using 2D mode in scene view (incompatible with Wet Stuff)
  • Dropped support for Unity 2017.4
  • Added support for “Mesh” shaped decals instead of just sphere or box shaped

Again no huge changes here, mostly just small tweaks to improve the overall user experience. Mesh type decals are a pretty major feature from an end user perspective, but actually were quite simple to implement!


Since mid 2019 we’ve been working on this huge new project. Overcrowded is intended as a full toolkit to handle the movement of agents in the scene. It does pathfinding (currently using the Unity pathfinder, but we’d like to replace that in the future) but that’s not really the main focus of the project. The main focus is what comes after pathfinding: how to get agents to move naturally along paths. This is split into two main systems: global planning and local planning.

Global Planning is where you look at the high level goals of the agent (e.g. follow this path) and then come up with a way to achieve them (e.g. walk towards the next waypoint). This is something you’re familiar with if you’ve used anything like steering behaviours. However, basic steering behaviours have serious problems when you try to compose them, for example they can cancel out and cause the agent to move nowhere. You can add hacks on to try and fix this, but they’re really just fundamentally broken. Overcrowded has a much more advanced system of “Context Aware Steering Behaviours” which aggregates all of the steering impulses into a “context” and then picks the best direction to move from that context - it will never get stuck with two impulses cancelling out. The context also naturally supports negative steering behaviours which cause an agent to not steer in a given direction - that’s not the same as actively steering away from it it’s simply discouraging moving in that direction. This actually turns out to be incredibly powerful and as I’ve used the systems I’ve often found myself mostly using negative steering behaviours combined with just one or two positive behaviours.

Local Avoidance is where the agent looks at the immediate area around it and decides where it should walk for the next one or two steps. This might sound pretty simple but is actually quite complex and is incredibly important to natural looking movement - humans moving in a crowded will tweak their movement direction to avoid collisions with other people, taking into account how those other people will also tweak their movement to avoid collisions. Initially when we started working on Overcrowded we thought that we’d simply be able to implement an algorithm directly from some academic papers on the topic, but it turned out that all of these algorithms had bad behaviour in various different edge cases which made them unacceptable to use in a game. On top of that the performance of many of these algorithms left a lot to be desired! Instead we’ve developed an entirely new local avoidance system that is faster, simpler, cleanly handles most bad cases, is easily extensible and is even built with GPU computation in mind!

“That sounds awesome, where can I buy it?”, you’re thinking. Well… you can’t yet. We’re very close to an initial release, so watch this space. If you’re really interested in trying out this system please send me an email ( expressing your interest and I can probably give you an alpha version to try out. We really appreciate the feedback :)


Well, I did better than last year at least with my blog post summarising “The Yard Sale”, a game design technique developed by Zac McClendon which I’m a big fan of. I wrote this blog post to explain the technique to a team I wanted to use it with for…

Bounded Planet

Bounded Planet was a game development project with the people from the Cylon Discord server I spend a lot of time hanging out in. The idea grew out of a discussion about an MMORTS I used to play called Boundless Planet. We came up with a plan to write a similar game together in Rust using the Bevy game engine. We made some decent progress with a basic network system, adapting EGUI to render in Bevy, simple landscape generation and rendering and some camera movement.

Unfortunately we could never agree on a good design and the project is mostly dead. All of our design sessions basically degenerated into arguments about how much the game should be a clone of Supreme Commander. The strength of the Yard Sale technique is that it allows you to define some guiding principles and then iteratively create/discard features until you arrive a set of features that satisfy your overall design principles, often that final feature set may not be at all like what you initially imagined which is a good thing - it means you’ve discovered some new ideas! However, if this isn’t kept in mind by everyone involved it becomes an argumentative process as everyone tries to redefine the core principles to support their pet features. I think the “Yard Sale” technique really works better if you’re all physically present and moving the cards around on a pinboard.


Lockdown sucks and everyone needs a hobby to get through it. I’ve taken up PCB design and soldering of the completed boards (ordered from JLC) to pass the time. This is a really fun combination of browsing datasheets and electronics stores for interesting parts, learning enough about electronics to design the schematics and then routing the traces on the actual board. Here are a few boards I’ve designed this year:

I have a long term goal of designing something good enough to sell on Tindie. I don’t really expect to sell very many, but it’d be cool to have something good enough to manufacture and sell in (very small) runs. Maybe some kind of hat for the Raspberry Pi400, if I can work out what functionality to put in it!

Interesting Stuff

Some other interesting things that I encountered in 2020 i no particular order:

blog comments powered by Disqus