MENOZ

Hey, what tutorials have you seen? could you give more info on this please?

because houdini writes the value on the geometry after the code is executed, so while you are in the code, you cant' read @pointatr because its value has not been written to the geometry yet.

hello, I've made a hip file showcasing some tests i've made, regarding both sourcing (in the new pyrosolver sop) and solving collisions properly By "solving collisions properly" I mean without density loss due to collision, for that I disabled "correct collision" parameter in order to see what's going inside the collision object. I tried different combinations of settings, the grid is 2d and quite low res, in order to have a decent interaction on my old laptop. I tried on a modern workstation with higher resolution, the problem is generally less apparent but definetly still there. The hip file is commented as best as i can with notes. It took me quite some effort to test meaningful settings and put together the example file. I'm confused by the fact that the more "accurate" solvers and higher supsteps produce a worste collision behaviour. If anyone wants to try it out and see if he can make the collision to solve correctly and avoid density going inside the collision objects i've attacehd the hipfile. beware! even if it seems that on "first interaction" with the smoke the collision works fine ( this is probably the case setting higher grid resolution), let the object oscillate back an forward. cheers! collDebug.hipnc

In the case I have an HDA that does a series of things, for example bend, and draw curves. Inside I have those nodes that performs those operations and have their own view states. Would it be possible to access/merge those to the view state of my asset? I'd like to be able to choose if i want to enter the bend view state, or the stroke view state, from my hda.

you could speed it up a lot separating the capture step from the deforming step. You capture once, which takes lot of time and it would be always the same, and just deform on every frame. I'm referring to point deform's capture and deform parameters.

I'd say it's because it's a function that is only available in shading context. I'm not sure exactly how is this structured, but I know some functions only works for shading, I'd be interesting to know why. https://www.sidefx.com/docs/houdini/vex/functions/index.html

create various smoke caches and place them by hand

I tried using nested dielectrics and absorption. if you force specular of air bubbles you would get those sharp highlights as well. You should increase a bit the render quality maybe, I'm on a laptop. nested.hipnc

you could object merge different stages of your network in other geometries and link those to different viewports. but you can't set 2 distinct display flag in the same network.

-something to simulate feathers, leaves, scales, fast and efficently. Vellum is helping a bit but is struggling a lot with rigid pieces and collisions. needs too many iterations to converge.

you have normalize(@ptnum - p0) @ptnum is the integer id of the point, not its position.

http://www.sidefx.com/docs/houdini/dyno/plasticity.html Note It is difficult to make very stiff material in Vellum, such as sheet metal. For very hard materials, use Bullet Soft Constraints.

from time to time i have that problem, I've been burned once and now I don't really trust the spreadsheet's order I always order by another column to force a refresh and have it working correctly again. if you managed to make it reproducible maybe is a good idea to send it to sidefx so they can take a look.

i tried to put the parting lines in the guide groom, (and create a rest sop or it will complain later) and it seems that the hair gen picks it up and part it correctly.

because what applies to you doesn't necessarily apply to everyone else. If cops is enough for your work that's great, someone else might have different needs. (Rotoscoping, tracking, speed.. )