[Sidefx-houdini-list] OTL available only in one file
andras.ikladi at gmail.com
Sat Feb 9 07:10:03 EST 2008
I can't try it right now, but doesn't mantra feature an almost full
blown hscript engine? If you launch mantra with no stream inwards, you
can try it yourself it it can echo your variable (you could try help
-k, if I remember correctly to get more documentation). I would
suspect it can use envvars (but I may be wrong..easy enough to try).
This obviously supposes that mantra is launched from the same or
similar shell environment as Houdini and has the same variables
On the other hand, as IFD's tend to be relatively static (ie. use
once..at least compared to Rib that uses the same format for archive
and main render stream purposes) without parsing, I don't see that
much point either (and if you're doing parsing already, you can just
as easily identify a network path than an envvar).
On Feb 9, 2008 1:01 PM, <symek at poczta.onet.pl> wrote:
> well, there are much more appropriate people here to answer you that question, but let me just point you out that, IFD file is *meant to be used remotely so this shouldn't be any problem for you. Most of (like 99%) the case with IFD is sending it to renderfarm - read: executing remotely.
> The reason why variables are expanded in ifds is that they are read by Mantra but Houdini itself. The whole business with magical $Variable doesn't exist in Mantra I suppose. I'm not really sure if you can process ifd with python and replace absolute paths with variables as most probably they have no meaning form mantra.
> Normally remote hosts have all needed paths mounted in such a way that paths found in ifds are valid on every render node. In Windows both network drives mapping and using NFS paths work. (Besides minor problems like mixing localhosts and remotehosts in mantra -H option but this is yet another story).
> Sidefx-houdini-list mailing list
> Sidefx-houdini-list at sidefx.com
More information about the Sidefx-houdini-list