https://twitter.com/axelgneiting/status/1241487918046347264?...
I’ve been wondering if this will become de facto standard for multi-threaded/multi-core systems going forward.
ECS, the observer pattern, and behavior trees are probably the three main things that answered all the "how on earth do they build something this complex" questions for me.
I just ran across this: https://csherratt.github.io/blog/posts/specs-and-legion/
Specs? At least that's what Amethyst uses.
e.g. in say a jrpg you have "new game/continue" menu -> world map -> battles and character menu and back again.
Edit: oh I misunderstood you - you were asking about behaviour trees. I haven't used them for anything other than controlling game unit behaviour (although not necessarily just enemy ai - one other example is using them to combine a bunch of simple actions into one thing that the user can tell a unit to do - so like an attack move in an RTS is actually "loop (is enemy nearby? -> no -> move towards location -> yes -> attack (which is probably it's own behaviour tree))
ECS and being able to safely run "systems" within your game concurrently is becoming a thing rapidly as "lists of objects" do not scale.
I just checked Doom Eternal: it's running 81 threads. (Of course, not all of them are always active or doing things concurrently. It's just a datapoint.)
Intel basically only wins by a non-significant margin at video encoding nowadays thanks to AVX512 which AMD does not implement. AMD wins or is comparable at a lower TDP on everything else.