Category: wip

if you’re too lazy to search 😛

this is that shit but on surfaces. I cant release the code for this unfortunately but it works on most if not all non degenerate triangle meshes 😮 the tracing methods are based off that keenan paper i posted in cgi-math about intrinsic triangulations 😮

will pump out some longer versions laterrr

gotta actually do work at some point today 😦

but if u dont want to do crazy surface tracing, you can just fake it with xyz dist and primuv, though itll be pretty slow for big meshes like this (100k points)

Attachments in this post:
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20190510/22/19/jr_physarum_revisited_reupload.hipnc
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20190510/22/19/jr_surface_physarum_v001.mp4

the uv transfer file i have is a lifesaver

gimi a min to drag it up

not even close to the tutorial now…

Attachments in this post:
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20190710/05/19/UV_TransferSmaple.hiplc
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20190710/05/19/stickToAnimation_0001.jpg

If you are all going to have a crack at some procedural walking/dragging things, I just dumped all the files for my last movie on my website. Its a total mess, but might be of use to someone. I was planning a proper tut soon, but haven’t got round to it yet. Heres the files – www.richlord.com/tools/hesperius-draco

for anyone interested in the ASCII tool, have fun

supported generously by @xcaseyx

Attachments in this post:
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20193109/09/19/kw_ascii.hdalc
http://fx-td.com/houdiniandchill/wp-content/uploads/discord/20193109/09/19/kw_ascii.hiplc

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“`

cl.ly/7fb607fa6e70

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; iv@magfield = mf;“`

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