Andi Farhall

Thanks mrCatfish,

that works perfectly, vops rather than vex and wrangles is much more familiar given my softimage history but somethings tells me i'll need to grasp vex properly at some point as i've zero coding experience whatsoever. Am I right in thinking that groups are actually just attributes under the hood?

Solver sop seems like a handy node if I just just figure out how to incorporate it properly. Here's my scenario:

I've a a long strip of points travelling along in X (like rocks on a conveyor) and each rock has a float attribute that's a random value between 0 and 1. When each point hits a certain position in X the random value gets added to every frame which is where I though the solver sop would come in. Then at a further position in X the counting stops, and a delete node gets rid of all the points who's random value is above a threshold.

I was using a group by bounding volume to determine where the counting should occur but I can't combine the counting bit inside the solver sop with the grouping bit that comes before.

How do I get the adding wrangle in the solver sop to use the group that's changing frame to frame.

Alternatively what other techniques would people use to achieve the same result?

cheers,

A>

I though it was me and I was just breaking something but I get the same behaviour with a simple test scene. I'm viewing the values in my pyro voxels using a volume slice on the import_pyrofileds node and getting some wild density or heat values. There's the normal range I would expect 0 to 1 or suchlike, and then I'm getting values like 4.10663e-26 or -3.07336e-0 which is confusing.

Are these numbers anything to worry about? Is Houdini, and for that matter redshift ignoring them?



cheers,

Andi.