George Hulm

Thanks!

That's the (completely optional) pruning doing what it's supposed to do. Pruning can be done manually or procedurally according to user input or any attribute. In this case, it's just based off of a random chance and a height-based condition.

We're very much over the hump with Apex. Thanks to the kind folks at Sidefx that steered us in the right direction. We're seeing some very exciting results now and the advantages of working Apex are becoming clearer by the day!

The Speed, control and flexibility are all very impressive and in our case there are some exciting benefits that we'll be sharing as we get closer to showing off more of our work.

In the meantime here's an early preview of our apex "solver" in action. It's still missing important features, but the core framework is nearly there.

Some more context thanks to the kind devs at sidefx who helped us learn how to do things correctly:

graph::templates that get invoked only need to be "setup" once and these can get invoked at any point using graph::invoke in apex.