Plasticity 2026.2 adds reusable component libraries, a Studio-only constraint system and new surface-alignment tools to the direct-modeling workflow. The developer’s release of version 26.2.0 also brings curvature analysis and improvements to existing modeling commands. Together, the changes are aimed at reducing repeated setup and giving surface edits more control—but the new constraints are not saved with the project file.
Reusable parts move into the Outliner
The new Assets system lets users mark, export and share reusable components. An Assets tab in the Outliner provides access to asset folders, and components can be dragged into the viewport for placement. Plasticity’s release notes cite bolts and other mechanical parts as examples of components that may be reused while assembling a model.
For repeated modeling work, this is the update’s most immediately practical change. My position is that a small, clearly named asset library is safer than a large pack: an ambiguously named component can be mistaken for the intended part during placement or a handoff. Before accepting the library workflow for an assembly, check that each inserted component’s name and geometry match the intended part; if either is unclear, reject it for that use.
Constraints help during editing, not handoff
The new Constraint System is available only in Studio. Depending on the command, users can create relationships that remain enforced as geometry is transformed. The release notes list supported operations including Square, Project Align, Surface Align, Edge Align, Vertex Align and several bridge commands, with continuity controls that vary by operation.
The key limitation is that constraints are not yet saved with the file. My position is that they are an in-session editing aid, not a handoff record: as an inference, reopening a file without those relationships could leave a later edit free to change geometry that was meant to remain aligned. Accept the workflow only if the saved-and-reopened geometry remains within the project’s requirements after the next planned edit; otherwise, document or re-establish the relationships separately before handoff.
I would not make the new constraints the sole basis for accepting aligned geometry in a handoff, because Plasticity 2026.2 does not save them with the project file. The practical check is to save and reopen the file, then verify that the geometry itself still meets the required alignment; if it does not, correct the geometry or re-establish the relationship before handoff.
More control over surface alignment and inspection
Project Align aligns control vertices along a target surface edge to a reference surface, using either a vector direction or the surface normal. The release notes describe Constrained and xNURBS solver options; the xNURBS solver requires a reference curve and is available in Studio. Plasticity also expands Edge Align with a Collinear solver and Symmetric and Asymmetric behaviors, plus a Skew boundary option that requires at least G1 continuity.
A new Curvature Analysis shader offers Gaussian, Mean and Max modes for examining surface curvature. The vendor describes these as ways to spot sudden changes, assess smoothness and identify areas that may cause problems when thickening or offsetting. These are inspection aids, not evidence that a surface will meet a particular manufacturing or engineering tolerance. Curvature analysis should inform inspection, not sign-off: the release lists the three modes but gives no acceptance tolerance. Approve a surface only after checking it against the tolerance specified for the project.
Other documented changes include editing PolySpline control vertices in Point Selection Mode, visual feedback when snapping to meshes, customizable edge colors and tintable matcaps. Importing a native .Plasticity file now supports meshes, images and instances, which can help preserve more of a mixed scene when bringing objects into another document.
My view is that the expanded native-file import is a transfer convenience, not by itself proof that a scene is complete in the receiving document. Before relying on it, check that every required mesh, image and instance is present there; if any required item is missing, keep the source document and do not treat the import as a complete handoff.
Studio users get the Constraint System and Project Align. Because constraints are not saved with the file, they should not serve as a handoff record.
Sources
- Plasticity 26.2.0 release — Plasticity on GitHub
- Plasticity 26.2 Release Notes — Plasticity Manual
