mestela
-
Content count
723 -
Donations
0.00 CAD -
Joined
-
Last visited
-
Days Won
64
-
That's overcranked disturbance. You could try keyframing it down over the first 30 frames.
-
Cool stuff @WLVL!
-
You're in luck! https://qiita.com/jhorikawa_err/items/24785f6255ccf19296b3
-
Yep, you can see I'm creating an attribute with a wrangle and ramp like the stroika video you linked, but you could use an attribute-from-map to make that attribute from an image sequence.
-
Here's one of no doubt many ways to do that effect. blendshape_from_ramp.hipnc
-
Sounds crazy! I was lucky enough to visit Filmakademie several years ago, maybe I'll come collect those beers in person...
-
Have you tried to light a non trivial shot in /obj context? Myself and a bunch of lighters suffered through this on HF2, it was awful. /obj is fine for a handful of nodes, but these days production lighting setups involve hundreds, thousands of assets. It's the kind of problem USD was built to address. Further, katana showed the way forward with a 'high level node based stream of all the things', the existing object framework was never going to be able to deal with that efficiently.
-
zBrush-style alphas on Heightfields/Terrain
mestela replied to Malak1000's topic in General Houdini Questions
Yep, heightfield from file, mask mode. heightfield_mask_images.hip -
The above answer is wrong? My one? Look closer; the first example uses the iterator 'i' to get a value from the array, the other one accesses the array value directly.
-
A for loop requires you to control the variable you're iterating, do your own comparison, and extract the element of an array yourself. A foreach does all that for you. These are functionally equivalent: int myarray[] = {2345,3456,234,34,6,8,567,34,5,346,45}; for (int i = 0; i < len(myarray); i++) { @P.x += myarray[i]; } // vs... foreach(int element; myarray) { @P.x += element; }
-
Ah, added an alpha fade to the lines: drippy_pixels_v2.hip
-
Or some mild abuse of scatter, attribfrommap, attribnoise: drippy_pixels.hip
-
Getting better, trying a fakey way of setting attachment points. I know the right way is to run this in a proper dopnet rather than the vellum solver, but meh... vellum_worm_guy_v02.hip
-
This is more comedy than horror, but might give you some ideas. Need a better way to stick the worms to the character, right now I'm just doing a lowbrow 'find the closest point and head there, plus up a bit', so the worms throw themselves in a rather madcap way. I'm sure you or someone else can improve on this! vellum_worm_guy.hip
