Kai Stavginski


About Me

Not Specified
Not Specified

Kai Stavginski has been a Senior Technical Director for SideFX Software since 2014. In that time, he's mostly been busy in the areas of shading and fur tools. He started in the industry as a generalist in 2004, spent some time as a rigger for an animated feature and then created VFX for major Hollywood blockbusters for several years. He used Houdini to get the job done and now uses his extensive industry experience in his development work on the software itself.


My Talks

obj-image FMX
Shading in Houdini 16
obj-image FMX
Fur in Houdini 16
obj-image Character FX Talks
Hair and Fur Grooming in H17

My Tutorials

obj-image Masterclass
Fur & Hair Grooming Toolset | H16.5 Masterclass
obj-image Masterclass
New Shading Features | H16 Masterclass
obj-image Masterclass
Custom Shading | H16 Masterclass
obj-image Masterclass
Hair and Fur Masterclass

Recent Forum Posts

What relation about light and texture? March 1, 2021, 9:59 a.m.

Ok the fix will be in tomorrow's 18.5 build.

What relation about light and texture? March 1, 2021, 8:40 a.m.

Hi, we already have a fix for that, it's just not in an 18.5 build yet. I'll try to backport & test it today.

Importing `houdini.env` into the shell Aug. 13, 2020, 7:50 a.m.

You can set variables from a bash script if you just source it. But the houdini.env file doesn't exactly contain shell commands.

In bash you could do something like this:

$(cat houdini.env | grep -v "#" | grep "=" | xargs -L1 echo export)

grep -v “#” just filters out comment lines
grep “=” filters for lines actually containing an assigment

xargs -L1 echo export just prints each line with “export” prepended.

So you get output like


Wrapping the whole command in $() will execute the whole thing as a shell command.

Bash also requires that there's no space around the =. Just make sure of that in your file, I didn't take care of that in the one-liner.