matrix3 mat; vector pos; int success; //Get per axis rotation amount from Controller (red null) float rotX = ch("../Controller/rotation")*ch("../Controller/rotationX"); float rotY = ch("../Controller/rotation")*ch("../Controller/rotationY"); float rotZ = ch("../Controller/rotation")*ch("../Controller/rotationZ"); //Get primitive points int points[]; points = primpoints(0, @primnum); //Rotate each point of the primitive using the transform matrix matr foreach (int pt; points){ mat = ident(); rotate(mat, radians(@primnum * rotX), {1,0,0}); rotate(mat, radians(@primnum * rotY), {0,1,0}); rotate(mat, radians(@primnum * rotZ), {0,0,1}); pos = pointattrib(0, "P", pt, success); if(success) setpointattrib(0, "P", pt, pos*mat , "set"); }

@@jack_drums thanks for the code, it's extremely faster

@@jack_drums SO much faster!!!

great inspiration and application of linear algebra! Thanks!

@@aboldmule Thank you! Glad it helps! ☺️

Hard to say as there could be a number of reasons but did you try using Unpack sop right under alembic import?

@@psychedlicavfx6646 thank you for replying 😄. I did, the thing is it works on the first or well the selected frame but not on the rest of the animation 😶. I tried unpacking and also using time shifting and using that to link the animation to geo node but so far no luck 😣

@@Zerefthedark that's strange. maybe write out the geo as a single frame bgeo after unpacking. then read it back in. this way you can diagnose if houdini is having trouble reading the alembic or there is something off in the alembic itself. bit of a hack but it could work. let me know if it works. am curious :)

@@psychedlicavfx6646 ok I will let you know when I try it 😄 thanks for replying tho

DAVID T VARGHESE maybe place an unpack and then a convert node. After the unpack I think it’s still a poly soup. The convert will make it into polygons. I’m no expert though.

Figured it out. Had iteration spelled incorrectly.

@@undertone_dj Cheers for this, you made me realise I'd made the same mistake 😅

Heyhey, the origin of each individual primitive is at {0,0,0}, so that's why they appear to be "flying" around. If you wanted to have the primitives rotate in place you'd first have to translate them so their center is at {0,0,0}, then rotate them, then translate them back. Cheers, Mo

@@Entagma Thank you so much for your reply, so each primitive's origin is at 0,0,0 but they are positioned based on the points they are connected to, which could be anywhere, sorry coming from a 3ds max background, didn't get this until now

Yes, exactly this. :) Cheers, Mo

In the transform sop's pivot transform type $CEX $CEY $CEZ in the pivot translate's X Y Z channels respectively to transform around the centroid.

Because the foreach loop (as we set it up in this case) is used to execute whatever nodes you put inside the loop body for each primitive separately. If you want to work on the geo as a whole, simply don't use a foreach loop :) Cheers, Mo

@@Entagma First of all, thanks for the answer, and thanks for all the great vids you guys do :) I think what I was trying to say was that the vertices between the polygons get split up, instead of the mesh being kept closed. I feel like it isn't intuitive that the loop would do that: after all, it could just, one after the other, transform each polygon, while NOT separating each polygon from the ones next to it(kind of like a displacement would do it). It seems like you wouldn't be able to do that in the loop, right? Sorry, maybe that's a bit stupid to point out, since I can't think of a good example why one would want to do that either at the moment, just something that I noticed^^

@@Goten1010 There's For-Each Connected Piece which uses the connectivity sop defining an attribute ("class" by default) that is used for the piece attribute in the block end.

Thank you for your valuable feedback. Cheers, Mo

@@Entagma Lovely deadpan passive aggressive reply.