thank you mate! 😍😍

Awesome to hear! I hope you find it helpful. If you have any questions, don't hesitate to ask😁

Cheers. That's very kind. I will for sure do that haha @@NineBetween

Hi! They made major changes to Karma and the Material Library in H 20. I'll do a revised video to explain some of the differences 👌

In Houdini 20, the Material Library LOP’s way of creating materials changed fundamentally. In previous versions you could access all shader nodes from the libraries root level. This often lead to confusion, because it was possible to mix incompatible shader nodes. Now, shaders are created inside subnets: Karma Material Builder USD MaterialX Builder VEX Material Builder USD Preview Material Builder

@@NineBetween thank you so much for this. Yes. I have been trying to get the shader working, along with displacement (it never worked 😢)

Thanks for the great comment! Solvers and forces work in an interesting way in Houdini, and the "gravity after solver" thing confuses a lot of people. But, as far as my understanding goes, solvers work in two "timesteps." The first one computes the entire network, as in, everything needed by the solver is evaluated in that timestep. Then, the second time step runs the solver. So it may seem as if everything is happening in order, but really, it has an asynchronous element to it where forces are recognized in the first pass and used in the second pass. I hope that makes some sense, I found it confusing initially, but again, it's about data flow, as you mentioned. In this case, the data is evaluated in a less straightforward manner. Thanks again for the comment, gonna pin this because I think some people will find it useful😁

Also the way popreplicate is processed in this video, try to explain someone that you plug an action that refers to another action, that looks like it should execute independently but it adds behavior to the first action based on first action state 🤯 😅 So again it relates to the behaviour of Houdini to process data from top to bottom and also from left to right. If I remember right there are some backwards flows too, forgot in which cases. I think there is definitely some flaws in Houdini architecture which they try to patch but instead they add more complexity and indirection 🤷‍♂️ I hope someday it will be really straightforward 👍 I like that they're trying to get rid of too many ops and try to integrate more in SOPs.

Hi, create a material in the /mat/ tab, rename it SPARKS, then, on your Material_library node (in the stage tab), on the Material VOP section, select it (mat/SPARKS)

​@@thibosoreil9460 Thank you

Same

solved the problem in mine. By default, "enabled" wasn't selected on the pop group node.

You're welcome! Those are two great questions. The "No save path" warning is specific to USD (universal scene description). When we work with Solaris, we have the option to save our files as .usd format files. It gets quite technical, but USD basically saves things as layers (eg. A geo layer, a lighting layer, a background layer, whatever user defined layers we need). Those layers are saved separately to disk. When we don't specify a layer or a path to save that layer to, Houdini automatically generates one, thus the warning message. A configure layer node would fix it, but it won't negatively affect anything you're currently doing. The @nage attribute is actually a bit of a unique case in Houdini. The attribute is only created when you call it and is defined as @age/@life. In other words, it's the normalized age. I believe it is called a "virtual attribute" and only exists when we call it because it would otherwise waste space if it were saved per point. Those were two good catches by you, and both are very much behind the scenes, technical things that don't really affect us. I hope that answers your question!😁

@@NineBetween It was very nice to receive such a detailed answer so quickly. Thanks for your efforts. Yes, now it became clearer to me. I'm just getting acquainted with USD. And your two-hour lesson seemed to me the most useful that I could find on KZfaq. It would be interesting to learn more about optimization tricks in Solaris. I've heard, for example, that File Cache + Sop Import will be slower than USD cache and Layer Import. I haven’t yet remembered exactly what these nodes are called. I didn't know about the properties of the @nage attribute. This seems logical, since POP Solver already generates too many attributes. Then, suppose if I want to call this attribute in mtlx shaders, I won’t be able to?

Hey! I had the same issue. My particles were looking greyish white and I wasn't sure why until I went back into the material node for the sparks and under the emission tab I realized that point color was unchecked. This solved my issue! I know this comment is 5 months late and I am not sure if you figured it out yet but I hope this helps!

Just use an expression in the impulse activation field rather than a pop wrangle. $F>84 && $F

may be not relevant : have you set collision behavior -> response from None to Die ? because if collision particles not die might results more impules points that slow down your pc to be created

Try to reduce the particles. If that did not help. Disable the solver and see what happens. It is most probably too many particles that could be the reason.

oh i didnt select enable under the pop group node

Are you using color ramp? If yes, try adding more points and change their colour.

Hey! No, either is fine. I mostly do it because it became a habit when I was first learning Houdini, but either is fine.

@@NineBetween cool, thanks. Love your content.