jan.b
jan.b
About Me
Connect
LOCATION
Not Specified
ウェブサイト
Houdini Engine
Availability
Not Specified
Recent Forum Posts
USDSkel and instancing 2025年7月27日7:22
So this is how i solved that for now, i don't know if there's a better solution?
Afaik the problem is the agent creation strip out all custom attributes.
So tried to inject the instance indices with a third lop input which is a copytopoints from sop.
After that the layered usd seem to keep those attributes (last one layered set the primvars indexinst)
I think those primvars pass the attributes when i unpack them in sop but i'm not sure.
Afaik the problem is the agent creation strip out all custom attributes.
So tried to inject the instance indices with a third lop input which is a copytopoints from sop.
After that the layered usd seem to keep those attributes (last one layered set the primvars indexinst)
I think those primvars pass the attributes when i unpack them in sop but i'm not sure.
USDSkel and instancing 2025年7月27日3:31
Hello I have the following setup i want to make :
I have a rig that drives a tree hierarchy.
Some bones have more than one point so those parts are deformable.
Other parts are meant to be instanced geometry and driven only by one point with rotations.
I got to the point i'm able to instance on the skeleton that is imported with lop character import.
But the trouble is that i'm unable to bring back attributes from primvars or else in lop import to tell the point instancer which mesh goes where.
I made a setup which is not on the pictures where an index is stored on the geo with dummy boxes.
I can see those primvars in solaris but they don't show up in lop import.
Similar setups are for RDB sims but in that case path and name are more or less the same and can exploited to instance. In my case a few meshes are reused across different points.
Also i would like the setup to not rely on sop, be self contained in a .usd file and be shared that way.
Thank you.
I have a rig that drives a tree hierarchy.
Some bones have more than one point so those parts are deformable.
Other parts are meant to be instanced geometry and driven only by one point with rotations.
I got to the point i'm able to instance on the skeleton that is imported with lop character import.
But the trouble is that i'm unable to bring back attributes from primvars or else in lop import to tell the point instancer which mesh goes where.
I made a setup which is not on the pictures where an index is stored on the geo with dummy boxes.
I can see those primvars in solaris but they don't show up in lop import.
Similar setups are for RDB sims but in that case path and name are more or less the same and can exploited to instance. In my case a few meshes are reused across different points.
Also i would like the setup to not rely on sop, be self contained in a .usd file and be shared that way.
Thank you.
Python states and StrokeState anchor new curves on existing 2024年2月22日8:35
Well so there's a ugly answer to that question but i'm sure there's a better way.
Make a feedback loop to the draw curve itself (in a one iteration loop) and move the curves on the plane they originated from :
Make a feedback loop to the draw curve itself (in a one iteration loop) and move the curves on the plane they originated from :
// Find the prim the current point belongs to, then store the point ID // of the first point in that prim int point_prim = pointprims(0, @ptnum)[0]; int first_point_id = primpoints(0, point_prim)[0]; // Use projection attributes stored on the stroke primitive // to move points vector p0_orig = point(0, "stroke_orig", first_point_id); vector p0_proj = point(0, "P", first_point_id); float dist_to_p0 = length(p0_orig - p0_proj); v@P = v@stroke_orig + ( normalize(v@stroke_dir) * dist_to_p0 );