bobbybob

I am trying to create a solid object, with hair simulation that can collide with other surfaces. Right now I am using the "Organic mass" shelf tool, to create a solid object of a sphere. I am then applying hair (Add fur) and then adding hair simulation (Also via the shelf tool) I have also added a ground plane. When the solid object collides with the ground plane (And the object begins to deform), the hair simulation explodes. Is there another way to create a solid object with hair simulation, that will work, when colliding with other objects?

@vicvvsh thank you! That makes sense

Is it possible to use at point group from sop level, to constraint points in a dop (wire sim) with the "SBD Pin Constraint", instead of manually typing in all the points, that has to be "Constrained Points"?

So often I create some different file cache nodes, from my "dop output". When simulating I often need to see how the sim is acting after 50 frames. But I can't resume the simulation, from frame 50 and to the end. I can imagine that, it's because the simulation, don't know the previous frame and therefore don't know how to calculate the next. Is there a fix/tip to get this working, like giving the solver the prev frame, to continue the calculations?

I am putting a new computer together. I am in doubt of how much memory I am going to use. My current configuration is 2x GTX 1080ti and 64GB of ram. I am rendering all my stuff in Octane, and can therefore benefit of the two 1080ti's. But I don't know if 64GB ram is enough. Are you guys, and girls often experiencing that your simulations is maxing out at least 64GB ram, when simulating stuff? The alternative, would be 128GB ram and only one 1080ti. (64GB ram cost about the same as a 1080ti)

I am about to buy some new hardware for a workstation that primarily are going to be used for working in Houdini. I am thinking of putting a Ryzen Threadripper 1950x in it, for the high amount of cores, and the relative low price in relation to some other Xeon CPU's. All my rendering is done in Octane, and the CPU will primarily be used for simulations. Are the 1950x, the right choice, for Houdini work?. For what I know, does Houdini support multithreading in almost every aspect, but does the high core count make up for a lower core speed. The alternative is a I9-7900X, where the cores are faster, but the number of cores are lower. Are there any other CPU alternatives in the price range (or a bit more expensive) that would give better performance?

Sean-R, thank you so much. Just out of curiosity. Is this a bug, that "i@opinput1_numpt" is not working, or do I use it wrong?

Sorry, I want the numpt of input 2.. I am use to programming where everything starts at 0

As I can understand from the Houdini documentation, the "@opinputn_name" will access attributes from the secondary inputs. I am trying to access the "numpt" by "int numLastPoint = i@opinput1_numpt;" but this does not work. Im I missing something?