検索 - User list
Full Version: how to alter alembic file to render as subd rather than poly
Root » Solaris and Karma » how to alter alembic file to render as subd rather than poly
Mark Wallman
Hi

If you use a reference node to bring in an alembic file. How can you tell Solaris that it needs to be rendered as a subdivision surface rather than polys?

I can see an option in the sopcreate node:
SOP Import>GeometryHandling>Treat Polygons as Subdivision Surfaces

The only way I can see with a reference node is to add a sopModify node, and unpack the USD. I am guessing I need to repack it but can see no way of doing this.

I feel sopModify is probably the wrong node to use in this case but not sure which node to use. Or should I always use a SOPimport node to bring in the abc file?

EDIT: OK as is always the way I may have found somthing. I just want to check that this a a good way.

-So under the reference node add a editproperties node and add a subdivisioncheme in.

Thanks in advance. (and I hope everyone is coping OK right now)

Best

Mark
jsmack
Correct me if I'm wrong, but subdivision scheme is NOT a primvar and has no inheritance and therefore needs to be authored on each mesh prim. Which would make it impossible to author on instanceable references.
mtucker
Setting the subdivisionshceme on each mesh is, I'm pretty sure the right way to do it. @jsmack is also right that if you are makring the imported alembic as a instanceable reference, this won't work. But you can author a second layer (published as a sidecar to the alembic?) that can also be referenced onto the same prim referencing the alembic. Then it's the combination of these two files (the Alembic and the enabling of subd overlay) that define the instance master which should work fine. Or the sidecar could be a USD file that sublayers the alembic and authors the subd attribute on top, then you can just reference the sidecar file… As always with USD, lots of options
Mark Wallman
Thanks. I will give that a go.

Best

Mark
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Powered by DjangoBB