Dan Wood

VortexVFX

About Me

EXPERTISE
VFX Artist

Connect

LOCATION
Mexico City, Not Specified
WEBSITE

Houdini Skills

Availability

Not Specified

Recent Forum Posts

Karma XPU (H20) vs Redshift Sept. 16, 2024, 7:51 p.m.

I've yet to dabble with Karma, but a while back I got into Octane - it seemed a lot better than Redshift for technical renders like water rendering with internal scattering, volumes in general, etc... and then they brought in the Progressive Photon Mapping kernel, which has been an absolute game-changer for light propagation in water renders.

I'm assuming photon mapping isn't in Karma yet... just wondering if there's anything on the roadmap to add something similar to the Octane PPM kernel into Karma XPU? Octane is great, but I always appreciated the simple customizability of using Mantra, so it'd be good to get back to an integrated setup.

Delete geo inside geo Aug. 28, 2024, 10:05 p.m.

Can't check over it myself at the moment, but I'm wondering if the group-expression version of the intersect command might be the way to go.

int intersect(<geometry>geometry, string group, vector orig, vector dir, vector &p, vector &uvw)

If you have each mesh assigned to a primitive group beforehand, you may be able to use a standard group pattern in that (string group) parameter... along the lines of "* ^thismesh" for intersecting everything excluding the current mesh.

Delete geo inside geo Aug. 27, 2024, 12:28 p.m.

Assuming you want to cull on a per-connected-mesh basis, rather than a per-point/primitive basis... you could perhaps start with the intersect vex command, make a check along the normal from each point in a mesh, store whether it hits anything or not... then use the promote note to aggregate the hits per mesh, convert number of hits into a percentage of total point count, and set a threshold to delete the whole mesh, say if 90% of intersect checks hit something, then delete that mesh.