Can you protect $VARNAME with \$VARNAME... you could make a python
script to put the backslash there on the preRenderScript field of the ROP.
Darran Edmundson wrote:
> 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
> I'd be very interested in hearing how others deal with path issues ...
> 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.
Sidefx-houdini-list mailing list