Pattern Feature vs. Instance Geometry in NX: Practitioner Guidance and Performance Notes

A recurring question for anyone building feature-tree-friendly parametric models with repeated geometry: when to pattern the feature versus patterning the geometry (face/body).

The core distinction

• Instance Geometry copies geometric objects — curves, bodies, faces, edges. If created associatively, editing the master object updates all copies, but the copies themselves are "dumb": they are not independent features you can edit one-by-one.
• Pattern Feature creates a true pattern feature where each instance is itself a real feature (hole, pocket, body, curve feature) that can be individually edited — you can suppress, resize, or delete a single instance without touching the others.

Note for version awareness: "Instance Geometry" as a distinct legacy command was effectively superseded in NX 9.0 by the modern Pattern-family functions (Pattern Face, Pattern Geometry, etc.), so some of this terminology is legacy but the underlying feature-vs-geometry distinction still applies to the modern commands.

Performance guidance

• Feature-based patterns (Pattern Feature) are the most processor-intensive way to multiply holes or other features, especially at large instance counts — they're heavier on memory than patterned faces because NX is tracking each instance as a distinct feature with its own dependencies.
• As geometry complexity grows, it's generally more appropriate to use Pattern Face where the per-instance editability isn't actually needed.
• Use Instance/Pattern Geometry when you need to create separate features in space, or need to work across more geometry types than Pattern Feature directly supports.

Practical rule of thumb for feature-tree-friendly models

Default to Pattern Face/Geometry for large-count, uniform repeated features (bolt circles with 20+ holes, perforation patterns) where you'll never need to edit a single instance independently. Reserve Pattern Feature for smaller counts where per-instance editability (suppressing one hole, resizing one instance) is a real requirement — the performance cost is worth it there because you need the flexibility.

Sources: Instance Feature vs Instance Geometry vs Pattern Face? — Eng-Tips, pattern vs instance — Eng-Tips, Pattern Features VS Pattern Geometry — Siemens Community, NX instance vs pattern? — GrabCAD Questions