Hello,
With Patreon In-Depth Knowledge. Will the hip file be possible to download?
I just not only want to learn the knowledge but also how to render a scene’s look like this
Thank you
Hey there’s now a really handy sop in H18 called DistanceAlongGeometry that will create a distance attribute from point A to point B along the surface of a geometry, and thereafter output that as an attribute that can be used to drive simulations, like this thing, pyro spreading and more…
Hello,
I think there is an error in the falloff config.
When I try it on my scene, all the primitives are triggered at the same time (I think the same happens in your video).
In order to make it work I had to remove the attrib promote and in the vex do this:
int pt = primpoints(0, @primnum)[0];
float falloff = point(2,”mops_falloff”, pt);
Can you clarify why this happens? I think the error is in @primnum but cannot say why.
Hello,
With Patreon In-Depth Knowledge. Will the hip file be possible to download?
I just not only want to learn the knowledge but also how to render a scene’s look like this
Thank you
Hey there’s now a really handy sop in H18 called DistanceAlongGeometry that will create a distance attribute from point A to point B along the surface of a geometry, and thereafter output that as an attribute that can be used to drive simulations, like this thing, pyro spreading and more…
Hello,
I think there is an error in the falloff config.
When I try it on my scene, all the primitives are triggered at the same time (I think the same happens in your video).
In order to make it work I had to remove the attrib promote and in the vex do this:
int pt = primpoints(0, @primnum)[0];
float falloff = point(2,”mops_falloff”, pt);
Can you clarify why this happens? I think the error is in @primnum but cannot say why.
Hey I noticed this as well, the fix is in the primwrangle before the solver add the line
i@id = @primnum;
then in the geo wrangle inside the solver do
prim(2, “mops_falloff”, @id);
Mortiz mentions this in an earlier video (1st or 3rd video), something to do with prim numbers getting changed in the solver.
This has driven me nuts for days!