Natsura 0.7.4
Growth engine fixes and speed-ups ported back from 0.8, faster scene loads and regrows, and better upgrades for 0.5 and 0.6 scenes.
- Version
- v0.7.4.0
- Released
- Type
- Minor

0.7.4 is a minor release ahead of 0.8. It ports growth engine fixes and speed-ups back from 0.8, cuts load and regrow times, and improves how 0.5 and 0.6 scenes upgrade. Growth output is the same as 0.7.3.
Performance
All timings use the Simple Tree example (about 19 million points), saved in the version being measured, on one workstation: AMD Ryzen 9 7950X (16 cores), 64 GB RAM, NVIDIA GeForce RTX 4090, Windows 11, Houdini 20.5.779. The 0.8 numbers are from our current development build and will change before release.
Opening the scene until it is cooked:
Regrowing after a parameter change:
Where the time goes in one edit (changing the Grow's pitch):
How 0.7.4 got faster
This part is for the Houdini TAs and TDs among you; you do not need any of it to use the tools.
APEX (All-Purpose EXecution) is the graph framework SideFX added in Houdini 20 for character rigs. We use it in a way it was probably not designed for, and I wouldn't be surprised if someone at SideFX would like to give us a slap on the wrist for it. Each tree is grown by a graph we generate from your Grows, maps and effectors: around 9,000 nodes on Simple Tree, with your map and effector code running as VEX inside it.
Houdini's profiling tools for SOPs are very good; for APEX there is much less, so a lot of this release was building our own measurements and following them. What we found:
- Compiling the graph is cheap, about 9 microseconds per node. A structural edit spends its time building the graph, passing it between nodes and compiling the VEX inside it. A slider drag rebuilds nothing: APEX keeps the compiled program and runs it again.
- Precompiled pieces trade off against one big program. We invoke small precompiled pieces that do not change and assemble a simpler program around them, so an edit recompiles only that part. Each invoke has a small cost of its own, so where to split is a balance.
- A Switch does not stop work. Both branches run on every point; the switch only selects the result. To save the work, it has to leave the graph.
- The run got cheaper by doing less. Points that have finished growing now leave the loop instead of travelling through every remaining step (about 93% of them on Simple Tree), and pruning runs in one pass.
Two findings outside APEX apply to any large Houdini toolkit built from assets inside assets:
- Split cook triggers finely. Each operator reads its settings through its own Object Merge, so an edit recooks only its own part of the tree. Merging them looks tidier, but every edit then recooks far more.
- Nested assets pay a sync cost. Any digital asset that contains another asset-type node, even an Attribute Wrangle, writes a hidden definitions file to disk and reads it back on every sync of every instance: about 4.5 ms each time, in Houdini 20.5, 21 and 22. Stripping those sections from a build cut Simple Tree's open time by 29% in our tests.
Beyond 0.8
0.8 brings the bigger gains shown in grey above. Beyond it we expect big improvements from several areas at once: how the growth graph is built and compiled, how much of it runs again after an edit, and how decorations mesh the tree.
Older Scenes
What is new in 0.7.4
- Old Grows carry their split starts and yaw maps over to the current Grow.
- Random 1 (legacy) uses the 0.5 random formula from the first growth cycle.
- Generation that followed the frame becomes a number (50).
We tested the upgrade on 13 production scenes from 0.5: all of them open, upgrade and cook without errors, and 40 of their 50 Simulates grow the same as or close to 0.5.11.2. Leaves and trunks are meshed by the current decorations, so they can look different from the original.
If one of your older scenes does not come through as expected, send it to support@natsura.com. We use these scenes to improve the upgrade.
How upgrading works
Upgrading is built on Houdini's own asset versioning. Every Natsura node is a digital asset with a version number in its definition, and Houdini stores that number with each node in the scene. When you open a scene, Houdini notices any node saved with an older version and calls the asset's sync hook; our hook notes the node, and once the scene has loaded it runs, in order, every upgrade step between the saved version and the installed one. A step can:
- translate a saved setting into what it means now, for example a retired option into its replacement;
- move a retired node onto its successor with Houdini's change-node-type, such as Grow 1.0 to 1.2 onto the current Grow, carrying its settings over;
- turn on a Legacy option on the Simulate when a scene was saved before a change in growth behaviour, so the tree grows as it did (for example Random 1, Split Refreshes Internode Count, Rig On Grown Points).
Each step runs once. The console lists every change, node by node, and names anything it could not change, such as nodes inside a locked asset. Saving the scene stores the new versions, so upgrades only go forward. Scenes now also record the Natsura version and build they were saved with, so later upgrades know exactly where a scene comes from.
Workflow and Stability
- Simulate's Generation is a plain number, 50 by default; the Generation slider grows the tree to the step you pick
- Posing in Generation Slider mode keeps the pose when the slider moves
- A Grow placed from the Tab menu sets itself up again
- A bad line in natsura.pref, or a damaged collections or projects file, no longer stops Natsura from starting
- The hotkey editor opens without errors
- Panels let go of the scene when you close them, so reopening them no longer stacks errors
- Toolbars and panels no longer hold the panes beside them at a fixed width
- Decoration slots stay live after an empty one, and new decorations show straight away
The full list of changes is below. As always, please keep the feedback coming.
George
Full Changelog
Scenes from older versions upgrade when they open, and the console lists what changed.
Growth And Simulation
- Growth speed-ups from 0.8: pruning in one pass, faster splits and gates, and maps and effectors reading less per step
- Generation is a plain number (50) instead of the frame
- Posing in the loop is kept when the Generation slider moves
- Simulate is at version 6
Scene Upgrades
- 0.5 and 0.6 Grows move onto the current Grow with their settings carried over
- Random 1 (legacy) uses the 0.5 formula from the first growth cycle
- Split start, undecorated Grows and yaw maps carry over from 0.5 Grows; a bare 0.5 Grow keeps its first step unturned
- Old scenes no longer cook the whole tree while they open (Simple Tree went past 29 GB)
- Scenes on Generation following the frame open at 50
- Scenes record the Natsura version and build they were saved with
Decorations And Assemblies
- A decoration with no strands this cook is skipped instead of failing the Simulate
- Prune Wizard keeps the root and first bones, and parent ids are rebuilt after pruning
- Rig Rebind, Rig Rename and Visualize Assemblies skip meshes without a capture
Interface
- A Grow from the Tab menu runs its setup again
- Decoration slots stay live up to the last valid one
- Effector helpers work on effector stacks with a prefix
- One picker per click when several Grows are selected
- The hotkey editor opens without errors
- Panels drop their links to the scene when closed
- The display toolbar, the main toolbar and every Natsura panel can be narrowed, so the panes beside them resize freely
- Input labels on Core Map Wrangle and Scan Material, and Tab keywords on Map Remap
- A splash screen per edition
Installing
- Setup shows the Natsura version beside the logo and in its messages, and the package file records it
- Setup offers the Natsura splash screen again
- Launch now: Enter starts Houdini, Esc skips
- Houdini versions are labelled: 20.5 most tested, 21.0 tested, 22.0 relatively tested
Stability
- A bad natsura.pref line, or a damaged collections or projects file, no longer breaks startup
- Scan Rig renumbers parents when a point is removed
- Drag Props and Originize Pivots report a failure once, not on every move
- File paths from our own machines are cleared from node defaults
- New nodes no longer inherit the userData of whoever last saved the node type
Known Issues
- Leaves and trunks on 0.5 scenes are meshed by today's decorations and can differ from the original; send us the scene
- Some tools still need SideFX Labs installed (Scan to Parts, UV Transfer, Mesh Meld and others)
- Scenes with Generation on the frame open at 50; set it back to the generation you want