← All ideas
  • Published 17 Nov 2021

Subdivision per polygon not modifier

Not sure if already suggested, but the current implementation of subdivision with a modifier has the problem that ain't work with instances. Meaning that a.) The modifier will not be applied, copied or updated on linked objects. b.) There is no performance gain on instanced objects, as the are basically just references of linked base geometry, but the subdivision is added on top of that per object. c.) Turn off subD modifier in viewport (which will still cause the render to use more memory) d.) There is one work around to b. by either collapse the modifiers or by using an instanced collection. But that would make collections mandatory for subD mesh.

So the solutions in other software is.

  1. Using a second instance type where modifiers are also instanced.
  2. Having the subdivision be an additional feature of the base geometry.
  3. Adding a render tag, so the object will only show SubD during rendering.
  4. Tagging individual polygons to be SubD Mesh or Not (Settings are based in the object properties)

Having worked with different software for many years I can only recommend solution 4. currently found in Modo only. It overs a unique way for users who do model to

  • supporting Instances e.g. huge gain for performance with this modeling technic.
  • mixing subD with hard surface Mesh in the same object. Especially useful on complex models, where parts need to be very smooth and other hard edge.
  • transfer polygons from one object to the next without caring about subD.
  • faster workflow with SubD
  • easier access to properties for multi selection (no modifiers need to be used).
75%

Development Status: Open

Upvote 3 Downvote 1
robert
17 Nov 2021

2 Comments

Lauloque

If we had the container object as requested many times already, that would be easy to do.

1
Shimoon

I think that moving the subD into the data itself was under discussion not some long ago