Sepu
-
Content count
542 -
Donations
0.00 CAD -
Joined
-
Last visited
-
Days Won
14
Everything posted by Sepu
-
It does work in RS but you have to do an extra step in RS. When you add objects to the force parameter it will enable the `Matte Params From` what I usually do is create a NULL then add the Obj properties in there and enable the Matte and do whatever you need to do there.
-
Do the same that you are doing with the scatter, randomize the global seed of the orient attrib @Frame*2244 or something like that.
-
it works for me in a prim wrangle as you can see I also use the attrib randomize. I use the 2 values distribution so I just get 1 or 0 but you can do whatever you want.
-
create a prim attrib like `@frizzampscale = rand(@primnum);` before the frizz and then use it where it says `no override` pick the `guide attribute` in the amplitude dropdown. And just reading your question again, you can do this in any of the dropdowns btw.
-
Changing torus radius with attribute from copy to points?
Sepu replied to Gigglebooster's topic in General Houdini Questions
You do not need to do that. Think in pts. f@pscale (uniform scale) is the attribute that you use to affect the torus that way, and delete the point function in the torus. There is a lot of different attributes that you can give to your pts before the copy to points, which reads these attributes. I would recommend going through this. https://www.sidefx.com/docs/houdini/model/attributes.html -
Changing torus radius with attribute from copy to points?
Sepu replied to Gigglebooster's topic in General Houdini Questions
I really do not know what you are trying to do looking at your file. Do you want to do something like this? -
is probably an error probably `&` that guy you have somewhere repeated twice or isn't in the right place, etc, just guessing here. The best thing to do is if you post you .env file here.
-
I wouldn't use copy stamp but if you add attrib randomize you can use distribution `custom discrete` which can give you weight for each pt
-
that is what is happening, look at the spreadsheet and you can also just put a pop color in ramp mode and do `ramp = @age;` and you will see it another representation or outside of the popnet as well, use a visualization node.
-
if I understood correctly what you want - in your wrangle inside the pop network just add if (@active == 0){ @mass=0; @age = 0;` }
-
Try to soften/harden normals or set to face.
-
What do you mean with `at frame`? There's no problem with redimensioning the container, that just focuses on where you want the sim to happens.
-
You can use channel reference or use the bbox() hscript function for the box size and the centroid function for the Box center.
-
You have to convert all jpgs, pngs, etc into ACES CG not matter what you used it for, the same goes with your HDRs, linear EXR, etc. If you want to work in ACES. Also, it depends on your render of choice if fully works in ACES. There is a lot to it. This is the best resource out there, explains everything in detail, it is long but I would highly recommend it. https://chrisbrejon.com/cg-cinematography/chapter-1-5-academy-color-encoding-system-aces/ If you want something shorter, Check this one from Toad. https://www.toadstorm.com/blog/?p=694
-
Check this
-
Houdini 18 rbd material fracture woes - can't keep static
Sepu replied to anthonymcgrath's topic in General Houdini Questions
You can activate in a frame that you wish, the rbdconfigure acts more like a global controller (Do not use the bounds in RBD configure). Then if you want to control which pieces aren't active just make a grp afterward and set it to `i@active = 0` Here is an example. Using a sphere ; ) But yes if you want more control and you are doing more complex setup Dops is the way to go. -
you need to loop on the new pieces, not the initial pieces that you set up at the first voronoi. You need to take care of the name attribute as well. By the way, the material fracture does all this for you as well. VoronoiFractureLoop_FIX.hiplc
-
You got a few things wrong with your setup. First of all the constraint attribute `strength` should be a primitive, not a point, so after the wrangle, I promote to primitive the attribute. Also, your wrangles were set up to some group that it didn't exist, also one of them was connected to the wrong path. One more thing in the `rbdconstraintproperties` you can set up the strength to 1 since is gonna be a multiplier to the wrangle above. I color the nodes in red that I fixed for you. color_to_glue_strength_attempt_FIX.hiplc
- 2 replies
-
- 1
-
-
- glue constraint
- attribute transfer
- (and 2 more)
-
What do you mean exactly? This works as expected if you have those channels they showed up in vray buffer as you can see.
-
You to tell the constraints which pts you want to atta ch to the geo. Create a grp of the pts that you need and add the grp the constraint. Here is a fix. Hair Fallout.hiplc
-
Is your name attrib, all messed up. Either use a wrangle and add this line s@name = sprintf("piece%d", @ptnum); or after the assemble unpack your geo (Transfer the name attrib) > connectadjacentpieces
-
orientation of copied object to match the normal of the destination of copy to points
Sepu replied to anicg's topic in General Houdini Questions
No need for a for each there just use the pts. with an extract centroid sop use and an attrib wrangle to create an id. orientation in copy to point.hiplc -
How to add a different viscosity for each Emitter in latest Houdini version
Sepu replied to balaji j's topic in Effects
Do it in SOPs in a wrangle or attrib create. -
It is working fine here - you aren't seeing the color because you have the grp in the wrangle which isn't updating. You can see the attrib is getting updated, so you do not need the grp there.
-
if you are in 17.5 why don't you use the retime node that comes with Houdini?
