Matt Estela
mestela
About Me
Expertise
Not Specified
Location
Not Specified
Website
Matt Estela is a Senior Houdini Artist at RYOT. Previously he was VFX Lead in Residence at the UTS Animal Logic. Academy, and before that at Animal Logic he's been a VR Supervisor, Lighting Lead, Fx Lead, CG Supervisor, and is one of those annoying Houdini evangelists you don't want to sit next to on the bus.
Connect
My Talks
My Tutorials
Recent Forum Posts
Solaris and USD advantages for one-person teams? Dec. 2, 2021, 7:25 p.m.
It's worth looking at Omniverse while its still in free open beta, as it helps solidify the pros and cons of Lops. It's USD based, has its own fast renderer, but goes a more traditional linear approach vs Lops procedural approach.
Generally it conforms to the pros/cons of a Houdini workflow. If all you need to do is load an object, light, camera, render, Omniverse is likely a better fit for you. If you need to do more complex setups, change lots of things at the last minute, make reactive adaptable setups, deal with all the usual hassles of real world production, Lops handles that stuff better.
Generally it conforms to the pros/cons of a Houdini workflow. If all you need to do is load an object, light, camera, render, Omniverse is likely a better fit for you. If you need to do more complex setups, change lots of things at the last minute, make reactive adaptable setups, deal with all the usual hassles of real world production, Lops handles that stuff better.
how to force karma (cpu) to update textures? Nov. 30, 2021, 4:07 a.m.
Semi-related, Karma seems super aggressive in holding locks on textures on disk, so other processes can't update or delete them.
In this case I'm using tops to pull in a variety of images in various formats, ffmpeg/imagemagick to conform them to png's that are 512x512, then tops/lops to create materials that use those images.
Several times now once Karma has generated a render, the images are locked. Swapping to HoudiniGL, restart the render, move to a node before the materials are created etc.. all the usual drills, windows can't delete the textures, tops can't update or delete the textures.
Now and then I'll have luck making another lopnet, display that context, now the textures are unlocked, but again, this isn't a viable solution in the long term.
In this case I'm using tops to pull in a variety of images in various formats, ffmpeg/imagemagick to conform them to png's that are 512x512, then tops/lops to create materials that use those images.
Several times now once Karma has generated a render, the images are locked. Swapping to HoudiniGL, restart the render, move to a node before the materials are created etc.. all the usual drills, windows can't delete the textures, tops can't update or delete the textures.
Now and then I'll have luck making another lopnet, display that context, now the textures are unlocked, but again, this isn't a viable solution in the long term.