Search - User list
Full Version: Named Point Instancer Prototypes mess up assignments
Root » Solaris and Karma » Named Point Instancer Prototypes mess up assignments
tas3d
I use name attribute (or any string attrib) to name Point Instancer Prototypes.
But if I do, then shape assignment is random once point count number starts changing.
Its a simple Packed Geo to LOP worflow.
Am I missing something?

Attached hipnc

Thanks!
goldleaf
In general, I try to be careful with @path and @name when going to/from LOPs; and these are packed prims, where you have name on the inside of the packed geometry, as well as on the outside. There could be a bug here, but it's hard to tell. If I change from using s@name to using s@foobar, the exported PointInstancer is stable again.

Were you seeing it not work if you used a different string attribute? Did you try using an integer attribute on the Copy to Points SOP?
tas3d
I agree with path/name attributes, they are interpreted at default in certain LOPs.

Even if I rename s@name to s@piece and use it as a Path Attribute in Import Configuration, I get unstable result.
Why I do it in the first place? I want Prototypes to have names from s@piece attrib.
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