Jump to content

when to use Pack Geometry in CopySOP

jim c

Recommended Posts

If I have geometry that I'm passing into a CopySop that is changing over time (specifically a basic leaf shape that may have it's shape changed based on stamped values from the copy sop that in turn pull this from attributes on the template points) does it make sense to even use the Packed Geometry option in the CopySOP? IN the sidefx docs I came across this:

" This is important to remember when copy-stamping packed geometry. If every instance of your packed geometry is unique, you get no memory or performance benefits. In fact this will use more memory than "real" geometry would, because each packed primitive has its own overhead. " (https://www.sidefx.com/docs/houdini/model/packed#how-to)

Since the leaves are different for each template pt, am I sort of defeating the purpose packing them? Or would I use some other workflow? Total number of template points (when the tree is fully grown) is around 110K-150K pts.

Link to comment
Share on other sites

when talking about geometry where each copy is stamped to, there is no benefit of packing. you may, however, want to pack the geo after the copy SOP and then bring it back as a packed disk primitive (depends on what are you doing).

Edited by davpe
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...