Jesper Rahlff

in order to do that you would in another if statement check if they have collided with the ground. Same concept

you are mixing things together. That is not a name attribute on the primitives. That is a path attribute. You name attribute exists on the points. Each individual cube is represented by a point. This is what happens when you pack the geometry. So in order to color some of the cubes for instance you need the sop solver to be attached to the rigid body solver. Not the constraint solver. (unless you are trying to color the constraint primitives.) See below Lastly in order to access the cube geometry (the points) you need to work from the dop_geometry node inside the sop solver and not the Impacts. Once all of that has been setup you can then write your code. Your code should look something like this: Take note of the fact that the wrangle node is running over the points and not primitives. Since your geometry is packed I only have one point or one primitive available per cube. The name attribute exists on the points, so we have to run over points. A simple string condition does the trick to isolate the desired cubes. Inside the if statement I choose to add my color attribute to the primitive instead of the point which I am running over. This is simply just because Houdini is not very good at displaying colors that sits as a point attribute when dealing with packed geometry. So in order for it to show in the viewport I added the color in a primitive attribute instead.

yes you can use the s@name string attribute to identify your pieces with. This is why we setup unique names for our packed geometry. So the solver can keep track of each individual piece.

The ObjId has nothing to do with your packed geoemtry. Your ObjId describes the different dynamic objects. for example your RBDpackedobject1 node has objid == 0 and your groundplane has objid == 1 I am a little confused as what you are trying to add a color to? Is it the cubes or the constraints?

Also the documentation is quite well updated with the difference between the new sparse solver and the old dense solver. https://www.sidefx.com/docs/houdini/pyro/index.html

you could create a piece of geo with uv's apply they texture and instance that only the grain particles?

you can enable a bevel scale as a point attribute on the polybevel. this can give you a nice rounded bevel at the top and a hard square edge at the bottom.

ability to save out flipbook holding all the rows and coloumns as one flipbook.

you can use in a primitive wrangle: nprimitives(input)

I also slowly started to dive into Ocean spectrums. I was able to get something cool quite quickly, but there is still lots to figure out. White water will probably be next. Rendered with Redshift

More Vellum stuff. This is all the same simulation, however this time the focus was really to explore different camera angles, FOV, DOF as well as directional lighting. I had a few other versions with stronger DOF but they made me dizzy looking at them. So I stuck with these. Rendered in Redshift.

I want to start spending an hour everyday to just explore simple stuff in Houdini. This will be areas I probably feel I lack a little understanding, as well as ideas I have had but never really executed. Hopefully some form of render will emerge from every little exercise that I do. Last night I had a quick dive into vellum and played around with some Cloth. Rendered in Redshift.

Since your fire will rise upwards I assume anyway, you could scatter some points on your branch and then instance some curves onto the branch. You could then convert those curves into a source as well with the branch. Benefit is that you can animate your curves to give your source a more interesting look which will help with detail etc in your sim.

Short video catering more towards beginners. Let me know what you think.