They are stored in a python file that is loaded when Houdini launches… one sec, I’ll find the support page
www.sidefx.com/docs/houdini/hom/locations.html (In the startup scripts section)
I have a module called fcurves, and in there is a function called overshoot(), which can take some parameters or operate using default values if no parameters are entered.
yeah that’s the grid resolution stuff
it’s definitely going to be dependant on the grid res at the end of the day. but that’s the tradeoff
Attachments in this post:
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20193808/12/19/grid_to_levelset_curves_v02.hip
looking at the random paper or two: www.researchgate.net/publication/220068154_Rendering_Traditional_Mosaics
but the bit i need to solve manually to really get more control is to roll my own offset curves and honestly, i just aint in the mood at the moment.
I remember making a pass that worked okay, but when it comes time to fix overlaps, i lose interest.
“`Spot lights casting caustic photons (millions) Object casting caustic photons (glass material with disperssion) Search radius on caustics set to like 0.1 or 0.03 depending on the shot higher values = more blur, lower values = more tiny dots of light If you want very very detailed caustics crank up spot lights to 9-10 million and search radius down to like .01 add photos until you’re happy“`
there you go whomever wants to play around with the caustic setup I made a scene
Attachments in this post:
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20193307/24/19/ch_caustics_RS.hiplc
p simple actually This is a volume wrangle. First input is your volume for storing the field, second input is your geometry that has a magnetic value (-1 to 1) point attribute “`c vector mf = 0;
for( int i=0; i
trying to convert to openCL but running into dumb problems with how to write to vector volumes
of course, it also doesn’t take into account spatial density of points, so if you double your point count you will get double the magnetic field values
peeps were talking about using FLIP for marbling/ink sims a while back… but i gotta defend the honour of the smoke solver, this uses no particles just a full-res fully-advected “single rest” field, with some noise mapped onto it in COPs. the downside is that no diffusion/blending is possible at all, everything stays sharp no matter how folded and distorted it gets streamable.com/3gtni
Attachments in this post:
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20191805/20/19/1904-oil-v06.hiplc
modified repo will be here, its in examples test.py
github.com/workproduct/face_alignment/
the test batch python file will batch a folder of frames, ill combine the 2 together later to make a sequence of the points
https://vimeo.com/336017942 here’s a link to my LA HUG talk where i poorly explain how to make a vex based polywire sop. unfortunately it’s only a screen recording and my voice, so its probably a little dry…