This one focuses on an Adaptive FACS Pipeline built in Houdini. FACS + 4D cache retargeting across different character shapes, procedural jaw/eye solves and facial corrections.

Hi everyone, sharing my transpiled version of the MixBox pigment mixing algorithm into Houdini's OpenCL.

The code is based on the OSL version from the original repository because it included the lookup table for evaluating the polynomials right into the code instead of using a texture image which is what the other shader implementations used.

MixBox seeks to solve the issue of inaccurate digital colour blending because colours don't mix by simply lerping RGB values.

I have included my OpenCL code as a header file which you can use in your own kernels or copy paste all the functions inline to use them.

Here's the GitHub repository for the code, instructions on how to use, as well as demo files:
https://github.com/yongsoon-vfx/mixbox-houdini-opencl

And my instagram for some of my other work:
https://www.instagram.com/backface.culling

Some background: i have used houdini part time for ad agencies for about 3 years, then stopped mid 2024. Now i have my own side business that needs some archviz type shots, with some effects (like smoke and particles for product visualizations). I really dont feel like learning max or cinema, as im pretty comfy with houdini. I went through some of the sidefx lessons for solaris/karma, seems pretty good for archviz (at least easier than it was before). Im wondering if im missing something here? Karma render quality? Photorealism? is it all there?

Hey all, I was building a COPS Subnetwork with multiple outputs and I noticed something that may be obvious to you: It always cooks all outputs even if I'm only reading from one, leading to the network getting slow.
Is this intended behaviour or am I missing something?
Thanks!

Hey guys,

Problem:

No good recource about shaping your fire in a shader (at least for redshift it seems).

What would be one of the first things you would like to do when shading fire? REMAP and RAMP the values of the TEMPERATURE-Volume as you always do when creating fire simulations in houdini. But it seems to be not possible.

I cant stand why this is not working, it feels super trivial.

I have created this fire sim and wanted to test solaris for this testproject.

Shouldn't this rsrampscalar basically change nothing?

I have also tried feeding in my own color ramp into the emission tint parameter that would be supposed to be driven by the temperature but no luck on that end aswell...

Is there anybody that could help me out here? Would be much appreciated, thanks in advance!!!!

enabling scatter doesnt affect the sim, while enabling fire and smoke does. After finalizing the look I just navigated to obj level and again when I navigated to solaris scatter stopped working. The 3rd pic is off the look I finalized before navigating to the obj level.

What is the issue?

is this some kind of glitch?

Made a looping smoke sim. The style based on 80s vhs horror videos I used to see all the time.

Would you sculpt something like this? Is there a height field workflow that could work? Overall just wondering the best approach to get the putting green and fairway on separate levels so it looks realistic

I’ve been sitting here for an hour trying to figure out how to get rising bubbles using pressure incompressibility in FLIP with the FLIP solver, but I honestly don’t understand it at all. Could someone help me?

Houdini was used for the ground destruction, rain, smoke and all particle sims

i want to emitt a long cloth shape geometry in houdini with with property of cloth that emitt infinitly

Failed to open SHFS file C:/Program Files/Side Effects Software/shfs/houdini/nodes/sop/ml_volumeupres/ml/billowysmoke/billowysmoke_2x_medium_v1.metadata.json.hdownload: Failed to create file C:/Program Files/Side Effects Software/shfs/houdini/nodes/sop/ml_volumeupres/ml/billowysmoke/billowysmoke_2x_medium_v1.metadata.json.hdownload: Access is denied. (Error 5)

I am trying to install Houdini 21/22
Even after using the launcher as administrator i am running across this issue, houdini 20.5 and older versions are working fine i am having issues with the newer versions, what is causing this issue

I want to fracture a USD file object and apply all materials in back LOP. But after fracturing in SOP stage, there is no material path in my object. How can I fracture without losing any material or how to link the material together with the fractured object.

I want to quick isolate view one light in karma

Like we do on arnold and vray

Is there is thing like that in karma

I love the new Houdini UI, but I have 1 issue. The parameter editor at the right almost seems grayed out. Is there a way to make it more clear? My brain has a hard time having an overview because it just seems kinda hard to read.

my second question is the file browser houdini uses. I never understood why software have their own file browers anyway. Why not use the defaut windows one? The only software to get it right is Blender because their UI is actually better than the windows one. Anyway, is there a way to just use the Windows UI instead of Houdinis own UI?

Hey guys, I’m increasingly hearing about some studios working in decimetres, and I had a few questions as someone who’s never worked with this before.

- What departments are actually working in this?

- Is it an actual scene scale thing? or is it essentially just x10-ing the size of all assets?

- What implications does this have for things which use noises like heightfields?

- Obviously we going to continue working in meters in FX, but are we exporting out as decimetres, or is the conversion being done somewhere else? (maybe this is studio dependant)

- I assume this is done to reduce floating point errors, but are there any other reasons?

Is there anything else about decimetres that I should know?

What an opportunity to piggyback on the houdinimd creator’s attempt for such a change.

I use a screenreader through my phone and iPad often to present the doc page. My vision in my right eye is all but coming to an end from a degenerative disease. I got lucky to inherit, alongside my mograph skills, this gift from my Gramps and Father.

The page is unbearably heavy and drains power like nothing else on any device, and screenreaders already hate it. Seeing as I can’t easily focus on another screen or second monitor I’d be very happy to see sidefx make some changes or collaborate with the houdinimd guy.

The reader doesn’t work for the crossed out links. I also drew my feelings on this 🥀

Hi, I have the opportunity to attend the Houdini HIVEalt in London next month, and was wondering if it was worth it going even someone who started the journey of working with Houdini.

I've started learning it at school; through RBD, pyro, HDA and simple particle systems. I've taken some time to build my portfolio and worked with online courses to learn procedural modeling, texturing and lighting and rendering with Solaris.

Houdini is a very challenging software but it is rewarding when you can finally achieve what you wanted.

I'm curious about the announced agenda and would attend every speech, even if those sounds very far from what I can actually do. Also very much looking forward to meet people in this field as I'm actively searching for work. I'm wondering if it is a good place to network as a junior?

Here's my portfolio: https://www.artstation.com/azarn

PS: I'm coming from Paris and on a budget, so I'm really pondering on the logistics of 'is it worth it at my level to make this effort?'.

Thanks in advance for your help, I know VFX has been a tough place to work in lately, and it really is, especially when you start.

I’ve been experimenting with controllable 3d workflows with gen-AI things lately, and here's one test that felt pretty cool.

I did a custom viewport grabber node for cops, used nano banana (through fal) to modify the screenshot of the model, then "re-modeling" it based on the generated concept.

I know this is still pretty much slop, and more like a fun test rather than anything production-proven, but though to share.