Skip to content
OMNI/KIT
Independent procedural assets for BlenderReview build · TEST payments only
Utilities collection
Topology Regions Pro — source library preview; illustrative, not verified output
Source preview · illustrative. Illustrative previews may differ from the source asset.

Utilities / Geometry Nodes

Topology Regions Pro

Explore Topology Regions Pro: Geometry Nodes asset, source notes, editable controls and preview imagery. OmniKit review library.

7 exposed controlsGeometry Nodes
Review preview · not available for purchase

Source files are private. Compatibility, asset quality and component licences are being reviewed.

View planned membership

Functional review pending. This is not a complete compatibility certification.

Asset overview

Understand the setup.
Then make it your own.

Topology Regions Pro is a Blender Geometry Nodes asset in OmniKit’s utilities collection.

MESH INPUT. Groups connected faces separated by edges above the dihedral-angle threshold or Extra Boundaries field. Writes face omni_region_id, edge omni_region_boundary and display colors. Optional split edges and keep one region. IDs depend on input topology and can change after edits; not semantic/AI segmentation. A boundary must enclose a region to separate it. No face generation. Geometry first output; disable colors to preserve materials. See Utility Analysis Examples scene. AI preview is illustrative.

Its exposed inputs include Bypass, Angle Degrees, Extra Boundaries, Split Region Edges, Keep One Region, Region ID, Show Colors. Review the control reference below to plan a suitable setup.

Source and setup notes

Source node name: OMNI - Topology Regions Pro

Collection: 07 Utilities/Analysis Tools

Structural inspection used Blender 5.2.0 LTS. Other releases and render engines require separate checks.

How to approach this asset

  1. Check the source notes for the expected mesh, curve, field, shader or World context.
  2. Start with a disposable scene and a suitable input. Inspect required object, material or collection inputs.
  3. Adjust one documented control at a time. Evaluate the result before using it in a production project.

Keep exploring

More in this category

View collection ↗