Hey,
We had fun working this out when we moved our logs to a standard
location.
As long as the base dir exists:
"//sledgehammer1/share/rush/farmlogs/$project/renders/"
And then you use the "_%s" after say the jobname, it will create the
log folder.
Thou we are injecting this information to an .in and submitting it via
the command line to rush, so it may handle things differently.
ie:
LogDirectory:
//sledgehammer1/share/rush/farmlogs/project/renders/testrender_%s
Hope this helps.
Cheers
Kym
Gary Jaeger wrote:
[posted
to rush.general]
On Jul 9, 2007, at 12:08 PM, Greg Ercolano wrote:
I think it's documented behavior; the
little '?' help button
next to the Log Directory field says:
you're right, it's documented which I noticed after I sent the mail
"If you specify your own log directory, the directory must already
exist."
I could try to have it post a prompt if the directory doesn't
exist asking the user if they want to create it.
actually, that's not the issue. Let's say I'm going to render
"scene1.ma", "scene2.ma" and "scene3.ma"
If I leave the behavior as default, in the /Scenes directory I get:
"scene1.ma.log"
"scene2.ma.log"
"scene3.ma.log"
with the appropriate logs inside each directory. however, if point
rush to create logs in a /logs directory that I create, rush will just
start filling up that directory with log files. So no sub directories
with scene name prefixes are created. I would like those to be created
automatically just as they are if I leave it at the default.
. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
(Tel# suppressed)
http://corestudio.com
|
|