For those who don’t know the tool: Natsura, the Houdini foliage toolkit lives inside Houdini, can push assets to Unreal Engine workflows, and now leans harder into assemblies, mapping, and export glue.

What shipped in 0.6

Version 0.6.0.0 landed on March 25, 2026, with support for Houdini 20.5 and Houdini 21.0. The release calls out modular effectors, Nanite assemblies, an assembly decorator, a revamped UI, analytics, scan extension, and Houdini 21 support. The update introduces an Assembly workflow aimed at quickly rigging twig and branch libraries and assembling canopies. There is also a set of tools for Unreal Nanite skeletal assembly support, paired with wind authoring tools. Assembly-related nodes are flagged as experimental in the release notes, though. Be careful.

On the shaping side, the release adds a modular effector system like a bolt on simulation modifiers with no VEX required. Effectors are an extendable stack, and the base effector node supports writing VEX to extend the simulation and respond to geometry and inputs.

Assemblies, decorators, and Unreal export

The release adds new nodes for an assembly pipeline, including an assembly resource node for mesh library import and auto rigging, an assembly decoration node for canopy decoration that can pick modules based on traits and transform instance hierarchies with rigid rotations, and a classify node for trait-based module classification.

Export to Unreal related workflows gets multiple mentions. The export node for Unreal Nanite assembly lists updates including material support, skeletal and static assembly, fixed instance naming, and removal of a transform on points that broke instancing. There is also a LOP node for USD workflows that creates a Nanite assembly for SOP based creation.

Wind support is expanded through new nodes for wind initialisation and validation, wind class assignment for Unreal, a wind preview visualisation tool that is functional but not accurate or meant to look good, and a node that exports UE5 DynamicWindSkeletalData as JSON. If your environment team already has a wind data convention, this is the part to validate early, especially around naming, material binding, and what your in-engine tooling expects.

Effectors, guides, and growth controls

Several new effectors are listed: deflection, magnet attraction, gravitropism, gravity, and noise based growth perturbation. The grow node line gets a long set of updates in this release, including a new spiral parameter with absolute and relative modes, integration with the effector stack, and an updated decorator stack format to match the effector stack.

One practical change is the way mapping and prim construction are described. Map prim construction is deferred to grow, which is described as reducing node count and compile time. There is also an instant colour preview mentioned, plus options for skeleton swapping and custom draw modules. Growth workflows appear to be treated as a family of versions, with backwards compatibility restored across multiple grow versions and various mapping and parameter warning cleanups.

Rig simplification and reskinning

Rig simplification tooling shows up both as a new simplify rig node and as updates to a simplify rig reskin path, as well as multi stem tree support, chaining of simplify nodes, and added carve method and max joints count. If your pipeline needs a predictable joint budget for game ready trees, this is where you will want to spend time.

Analytics and privacy details

Analytics is “opt-in” and disabled by default, with no data collected without explicit user consent. If you work in an environment with strict compliance rules, the opt in default and EU cloud note are helpful details, but you still need to run your own review. Make sure your team knows what is allowed, and that tool telemetry decisions match your facility policy.

The notes also state that 0.7 will be a breaking release, and this 0.6 release includes precursor work such as a standardised mapping architecture, groundwork for decorator cook trigger decoupling, and a foundation for mappable decorator parameters. Read that as a warning to keep a rollback plan, and to budget time for update testing before you touch active porudction setups.

Compatibility notes for Houdini artists

Houdini 21 support is obvious, including mention of an APEX graph schema enforcement fix. The release also claims continued full Houdini 20.5 support, plus compatibility work around Qt bindings.

In practice, this release spans a lot of surface area: SOP level nodes, UI panels, export to Unreal, USD workflow hooks, analytics, and a mapping engine refactor. That is a lot of moving parts for a minor release number, even if the changelog is transparent about what is experimental. Treat the upgrade like you would any node library update: keep a copy of old scenes, validate the graphs, and test exports end to end before shipping anything client facing.

https://www.natsura.com/

The post Natsura 0.6 adds effectors and Nanite export for Houdini Foliage first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

One click, fewer vertex pushes

SmartConform Pro is a geometry-based conform and projection tool that wraps meshes onto complex surfaces like terrain, walls, and props directly inside the editor. The goal is to avoid manual rotation, scaling, and tweaking when placing assets on uneven geometry.

The core workflow is simple_ You select a source mesh and a target surface, then run a projection to conform the source onto the target. The tool targets common environment tasks like placing sci-fi panels, vents, and other hard-surface details onto curved geometry, plus placing rocks, debris, and similar assets naturally on terrain. Or, as we now them, ALL DA GREEBLIES!

Wrapping modes, overhangs, and smoothing

SmartConform Pro includes projection modes for surface-based wrapping and vertical projection, with volume preservation called out as a “design intent” – including supposedly smart overhang handling with an optional fallback to world surfaces.

There is a relaxation smoothing feature intended to reduce stretching and improve deformation quality. The interface provides a real-time preview for interactive setting changes before committing the result. One takeaway is that this is meant for fast conform tasks where the input mesh shape and UVs should stay predictable after the confrom step, instead of becoming a hand-tuned placement problem.

Baking, Nanite, and what it depends on

SmartConform Pro can bake the result to a static mesh, with Nanite readiness claimed after baking. Nanite support is described in the context of generating baked meshes suitable for high-detail rendering workflows, which aligns with how Nanite operates on static mesh assets.

Under the hood, the tool lists a C plus plus core powered by Geometry Scripting and an Editor Utility Widget interface. The listing also notes it requires the Unreal Engine Geometry Script and Geometry Processing plugins, referencing Geometry Processing as part of the dependency stack.

As always, new tools and workflow shortcuts should be tested on a copy of your project before they touch production assets, especially when deformation, baking, and downstream lighting or collision are involved.

Pricing and availability

SmartConform Pro is sold on Fab, with a Personal license for 55€, and a Professional License for studios / Entities beyond 100.00€ revenue a year, coming in at 96€.

What to watch for in real projects

The promise here is speed: fast placement for modular detailing and kitbashing, without leaving the editor. The real question for pipelines is how consistent the porjection results are across different mesh densities, collision setups, and target surface complexity, and how clean the baked meshes are for Nanite, LODs, and lightmaps once they leave the preview phase.

If this lands, it is the kind of editor utility that pays for itself by deleting a thousand tiny manual adjustments from every environment pass.

https://www.fab.com/listings/3df02265-3c86-4d3f-a17f-3fea15d418f1

The post Meshes in Unreal: Arvomis Oy ships SmartConform Pro first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

The problem NanoGS tackles

3D Gaussian splatting can look like magic right up until it starts behaving like a tax audit. Big captures mean millions of splats. Millions of splats mean constant sorting work, a lot of memory pressure, and a very real risk that the renderer spends time drawing things the camera never sees. NanoGS targets that exact pain: rendering large-scale Gaussian splatting files in real time, while handling video memory pressure, sorting huge splat counts efficiently, and drawing only what the screen needs.

The approach focuses on a set of optimisation techniques: Nanite-style LOD clusters, screen-space error LOD selection, splat compaction, a global accumulator, and GPU radix sort. The headline promise is straightforward: large-scale Gaussian splatting scenes should render efficiently, with an emphasis on keeping memory usage low. That is a marketing claim.

Supported engine versions and what you actually install

NanoGS lists support for Unreal Engine versions UE5.6 and UE5.7. The workflow stays inside the familiar plugin lane. You download the plugin from the releases page, place it into your project’s Plugins folder, then import a PLY file using the plugin import button. That import creates a Gaussian Splat Asset, which you can drag directly into a level for rendering.

There is also an asset action to enable or disable Nanite if needed. It is an unusual sentence to write about splats, but that is the point: the tool is trying to make splats behave like a native citizen in the realtime world.

The controls that decide whether it feels stable

The plugin exposes settings grouped by intent. They map cleanly to the trade-offs most realtime teams already juggle: quality, performance, and final look. On the quality side, SH Order adjusts spherical harmonics quality. On the performance side, Sort Every Nth Frame changes how often splats get sorted. Enable Frustum Culling turns frustum culling on or off. LOD Error Threshold sets how sensitive LOD cluster switching should be. On the rendering side, Opacity Scale adjusts splat opacity, and Splat Scale adjusts splat size.

These are not vanity sliders. Sorting frequency can be the difference between a stable camera move and a shimmering mess. Culling can be the difference between a scene that fits and a scene that explodes memory. LOD sensitivity can be the difference between crisp detail and visible popping. And opacity and scale are the levers that decide whether the splats read as a coherent surface or as a cloud of regret.

About one third into your first test session, you will probably notice the same thing most teams do: the scene can look fine at rest, then fall apart during motion if sorting gets too infrequent. That is when you stop guessing and start dialing.

Debug commands that make problems obvious

NanoGS includes console commands designed for inspection and stress testing. gs.ShowClusterBounds 1 enables a Nanite cluster preview, and setting it to 0 disables that preview. gs.DebugForceLODLevel can force rendering at a specific LOD cluster level for debugging, with values like 1, 2, 3, 4 and so on.

Then there is the one that will get used the most in anger: gs.MaxRenderBudget. It limits the maximum number of visible splats after culling to save memory. The default is no limit, using 0. You can set a maximum cap such as 3,000,000. When the cap is active, the culling starts from splats far from the camera.

If you are trying to ship anything on fixed hardware budgets, this kind of explicit cap is refreshing. It makes the failure mode predictable. It also makes it easier to have honest conversations with art and production, because the tool draws a hard line instead of pretending everything will fit if you just believe harder.

Best practice: do not feed it one giant splat brick

NanoGS calls out a best practice that will sound familiar to anyone who has ever fought streaming, culling, or draw lists. A single big chunk of gaussian splatting file does not help performance optimization. Splats outside the camera view cannot be culled effectively. And if everything stays in one chunk, all splats stay engaged in sorting all the time.

The recommended format is to slice a large splat file into smaller pieces. Examples given include individual props for cinematic scenes or tiles for geo-spatial data. The repository includes a simple tile slicer written in Python to support that workflow.

Proof of concept, not a miracle

NanoGS is described as a proof of concept, with a clear warning not to expect perfect results. Issues can be reported on the project page. That framing matters for production teams because it sets the correct expectation: you are evaluating a technique and an implementation, not adopting a finished commercial renderer. The good news is that the tool is built to be tested, with the kind of switches and debug views that make evaluation less mystical.

New tools and innovations should always be tested before use in production, especially when they touch core rendering paths and memory budgets.

Release, license, and what it costs

NanoGS is released under the MIT license.

The repository lists v1.0.1 as the latest release, dated March 20, 2026.

The plugin is free.

https://github.com/TimChen1383/NanoGaussianSplatting

The post NanoGaussianSplats for UE5 first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

The new CardCutter add-on for Blender converts texture masks into usable 3D geometry for Nanite-based projects in Unreal Engine 5. Created by developer Philipp Russo, the tool simplifies building game-ready foliage and decals by generating optimised meshes directly from source textures.

CardCutter operates as a geometry generation tool that converts 2D texture data, either alpha-masked colour images or greyscale masks, into fully triangulated 3D meshes suitable for Nanite rendering. The add-on functions within Blender’s Python API and supports Blender 4.0 or higher. According to the developer, the geometry output is designed to conform to Nanite’s mesh constraints, favouring dense, evenly distributed triangles over traditional quad-based topologies.

Each processed mask is interpreted as a binary image, with the alpha threshold defining the polygon contour. The tool applies an internal vectorisation step to trace the boundary of the visible region, followed by a polygon simplification algorithm to remove redundant vertices. It then uses a relaxation solver to re-distribute triangle density uniformly across the surface, creating stable topology for Nanite’s internal micro-polygon clustering.

Automatic atlas splitting

When the user provides a texture atlas (for example, a leaf sheet), CardCutter automatically detects discrete masked regions using connected-component labelling. Each detected region becomes a separate mesh object in Blender’s scene graph. This removes the need for manual cutting or polygon mask painting, which is typically required in foliage production. Each region retains its local UV coordinates, preserving the original texture mapping from the atlas. The output meshes can be exported directly as FBX or glTF, maintaining UV alignment and pivot orientation suitable for Unreal Engine import.

Geometry presets for performance tiers

CardCutter offers several density presets: Low, Medium, and High, which define the target number of triangles per pixel area. The lower settings generate lightweight meshes for background vegetation, while the higher settings produce Nanite-ready geometry that benefits from Unreal’s automatic cluster streaming.

The generated meshes are particularly intended for organic and irregular silhouettes like leaves, vines, ivy, ferns, but the developer also notes suitable use cases in flat debris, stickers, posters, and paper scraps, where alpha planes normally create overdraw problems.

In Nanite rendering, alpha cutouts are computationally expensive since masked fragments are still rasterised. By converting them into actual geometry, CardCutter removes the transparency pass entirely, allowing the GPU to perform visibility culling at the triangle level. This is beneficial for scenes with dense foliage or decal overlays.

Export workflow and integration

Meshes generated by CardCutter can be exported directly from Blender using Unreal’s standard FBX pipeline. The add-on does not alter material data; instead, it preserves UV maps for external shading setups. Unreal users can apply the same texture as an opacity mask or base colour without modification.

CardCutter also supports consistent vertex orientation to avoid flipped normals during export. According to the developer, all geometry is manifold and suitable for Nanite import without further cleanup, though it may require triangulation if the user modifies topology post-generation.

Pricing and licensing

CardCutter is distributed via Gumroad. The Individual/Freelance licence costs €12 and includes full functionality, updates, and one user seat. The Studio/Enterprise licence, priced at €50, allows unlimited installations within one facility and provides priority support for pipeline integration. Both include lifetime updates and are maintained by Philipp Russo under The Triangle Forge label.

Technical limitations and notes

At the time of publication, CardCutter is compatible exclusively with Blender 4.0 or newer. The add-on does not currently support real-time texture-to-mesh previews or batch automation through the command line.

Users should test export consistency when integrating the tool into complex Unreal foliage systems that depend on hierarchical instancing or runtime material overrides. The add-on outputs static geometry only, without procedural modifiers or animation rigs.

The post CardCutter turns texture into Nanite meshes first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Fab is Epic Games marketplace for 3D assets, replacing the Unreal Marketplace. It regularly offers time-limited free asset sets that you can permanently add to your library once claimed. These packs are commercially usable, work in most DCC applications and engines, and are a practical way to expand or start an asset collection without cost.

Two weeks to go before the calendar expires, and if you are looking to bury your good intentions somewhere scenic, Epic Games has the perfect spot. The Cryptic Realms Necropolis pack, normally $99.99, is free on Fab until 27 January 2026.

The pack offers 371 placeable objects to construct a stylised graveyard environment. It includes 80 modular meshes for ruins, tombs and crumbling architecture, plus graves, coffins, and set dressing items to complete the scene of your artistic demise.

Death by detail

Each asset includes 23 materials and textures, up to 4,096 by 4,096 pixels. The models support Nanite and Lumen, Unreal Engine’s systems for high-density geometry and dynamic lighting. There are three preset lighting setups to choose from, along with a modular environmental audio system to ensure your ghosts sound convincing. The pack is built for Unreal Engine 5.1 and later. However, the Fab Standard licence allows use in any engine or tool, including commercial projects, as long as the Fab EULA is followed.

Available now, before it’s dead again

The Necropolis pack can be downloaded free from Fab until 27 January 2026, after which it returns to its regular price. Perfect timing if you plan to give your old projects a decent burial before the new year arrives. As always, test assets thoroughly before using them in production or before the next resurrection of your pipeline.

The post Bury Your Good Intentions in 3D first appeared on DIGITAL PRODUCTION and was written by Bela Beier.