SUBSCRIBE The SideFX mailing list is a great place to make contact with Houdini users. To subscribe, send us an email with no subject and the word subscribe in the body.
- 1 discussions
non-hardened environment variables in IFDs? 7 years, 1 month
Is it possible for Houdini to *not* expand environment variables when writing to IFD? More generally, what options are there for dealing with relative paths when moving from one's local machine over to a render node? For a given project, I tend to create a directory tree with one or more .hip files in the root folder. Resources are then referenced as $HIP/shaders, $HIP/maps, etc. In the ROP, I'll then prepend my output filenames with $HIP/render/diff, $HIP/render/spec, etc. This works great on the local machine. However, writing to .ifd, the $HIP (or any other environment variable) gets expanded. My hack is to run a post-render script that does a search/replace of the hardened strings, converting them back to envvars. Of course this only works with ascii IFD. I'd be very interested in hearing how others deal with path issues ... Cheers, Darran. P.S. I've got a nagging suspicion that I asked a similar question on the list last year. Can't find a reference to it in the archives though. -- Darran Edmundson [darran at edmstudio.com] http://www.edmstudio.com
- 5 participants
- 8 comments