Please or Register to create posts and topics.

Additional Export/Render Locations as Houdini Variables

Hi Richard

Amazing work on Prism, my studio is beginning to shift towards using it and I am working out how to set it up this week. I do not have a whole lot of experience setting up pipelines. I was wondering if there way a way of getting the Additional Export/Rendering Location we set in the 'Prism Project Settings' into Houdini as a variable?

Thanks for your time


Hey Josh,

happy to hear that you are starting to use Prism. It shouldn't be too complicated to set it up in your studio, but just ask in case of any problems.

To create the location variables I would create a new custom Prism plugin in the Prism Settings. In the onProjectChanged function you can use this to get all export locations:


Using the Houdini python API you can create Houdini variables for each of these paths.



Hi Richard

Thanks for the help. I am having some issues getting it working, I think I am messing up some syntax on Linux. If its not to much trouble would you be able to give me a example of how to get it into the Houdini API.



You have to use two hscript commands: setvar and varchange. You can take a look at how Prism sets some variables in Houdini:

Got it working!

Thanks for your patience Richard, this was my first time playing with Python! haha

My probably pretty janky solution if anyone has a similar issue:

ExportPaths = self.core.paths.getExportProductBasePaths()
HCACHE = ExportPaths.items()[1]
HCACHE_String = str(HCACHE_Path)

hou.hscript("setenv HCACHE=" + HCACHE_String)
hou.hscript("varchange HCACHE")