3Delight for Houdini Volume rendering test.
Archives For CGI
Using vel fields to control the flow of FLIP sims is quite the handy trick, and using the new source volume nodes set to “pull” allows you to add in your vel fields without them looking like they are taking over the sim completely. Here’s a hip file too: directable_FLIP.hiplcContinue Reading...
I know most of you aren’t interested in this, but hey, there has to be at least one other dickhead out there that wants to compile the USD Plugins for Windows.
We need to install a couple things, namely Microsoft Visual Studio 2017 Community, and also CMake. Get them below. When installing Visual Studio grab all the C++ add ons.
Okay, so lets get to it. We need to grab the houdini toolkit folder, located in;
“C:\Program Files\Side Effects Software\Houdini 17.0.459\toolkit” for example. Copy and paste the toolkit (and obviously all it’s contents) to somewhere. I have whacked mine in here: W:\dev\toolkit but put it wherever you want. We need to set a couple environment variables in order for everything to work.
Let’s make a new environment variable and append the path variable. Remember this is the “User variables for YourName” section, not the System Variables. Make your new var CMAKE_PREFIX_PATH and fill in the path the cmake directory.
And now, let’s append the user path variable. Edit this bad boy, and hit new to append our path to the bin folder.
Sweet azz. Now let’s keep moving, it’s already making me sleepy. In the root of the usd_houdini_plugins folder, which for me is: W:\dev\toolkit\usd_houdini_plugins\
make a folder called “build.” Now In here is a “CMakeLists.txt” file. The default output is to dump everything into C:\Users\YourName\Documents\houdini17.0\ and this is shit. It will be dumped in with everything else, and be hard to fish out. If you don’t care about this, ignore the below custom output location set up. But for those who want to keep it out of there, see below!
Here’s the Vanilla, let’s delete stuff. Remove all the if >>> down to endif, and set your path to where you want to output the data.
Below is what I’ve cleaned it up to. It’s where all my houdini/pipeline tools live.
And here is the append line to make the DSO go to your custom locale. Just add the INSTDIR pathto\\where you added in above\\dso in the line below, and you’re gold.
Here is my CMakeLists.txt
Okey dokey, with that done, open a command prompt and CD to the build folder we made earlier. Now your prompt is at W:\dev\toolkit\usd_houdini_plugins\build> (obviously your location is different!) let’s do some hacking.
run: cmake -G “Visual Studio 15 2017 Win64” ../ and wait for the magic. Here’s a boring gif of the process for sheer entertainment.
Amazing. I feel like Neo, I’m sure a pill offering is on the near horizon for me. Hop inside the build folder and you can see all our hard work. Double click the following: “usd_houdini_plugins.sln” this will launch Visual Studio, all ready to rock n roll.
All we need to do is select the “install” and go and change from “debug” to “release” then right click “install” and “build”
Once it’s all done, you’ll get some sexy confirmation messages in the output window. If it all went to plan, there will be all the USD Plugins in the location you chose earlier.
Sweeeeeeeeeeeeeeeeeet! Now add this to your houdini.env file: HOUDINI_PATH = “W:/Pipeline/Houdini_USD;&”
We made it Wendell! I hope you managed to stay awake for this. I didn’t. Here’s a zipped up binary built against 17.0.459 for you lazy bastards Houdini USD Plugins