Hi Greg!
Yes, I render the same scene, with the same frame range, but different
render layers.
And it's the way I've rendered a lot of projects.. but.. I don't know why
now the logs are mixing... You said it's the default behavior but... I've
never seen that before..
Anyway it's working now with the little hack.
I think render layers are a good way to save time and bring flexibility
to postpo workflow. In fact the oputput images are in separate folders
taken by what render layer says, so I think I'm safe from overwrite the
same data.
Thanks!!
On Fri, 13 Apr 2012 13:56:32 -0400, Greg Ercolano wrote:
> On 04/13/12 10:29, wattana wrote:
>> Hi Greg!!
>> Thanks for the answer!
>>
>> Yes, it seems that the location of the log file is the key of the
>> problem...
>>
>> But I do not understand why I never had this problem before... I've
>> rendered a lot of projects and never seen this problem...
>
> The issue wouldn't come up unless you rendered the same scene and
same
> frame range with two active jobs at the same time.
>
> Usually people don't ever want to have two jobs running the same
> scene/same frame range, as they'll overwrite each others images
(as
> well as logs), causing corruptions.
>
> The only time I could see doing this for a desirable purpose is
if the
> two jobs were rendering different layers.
>
>> I found a way to workaround it coding (a little bit) the maya_submit.pl
>> file. Here's the change I've made:
>> [..]
>> $in{LogDirectory} = "$in{ScenePath}.$in{JobTitle}.log";
>> [..]
>>
>> I've added "$in{JobTitle}" in the logdir creation. I've tested and
>> worked fine.. Now is the responsability for whoever launches a job to
>> keep different job names, but I always put in the scene name and the
>> layer.
>
> Yes, that should be fine.
>
> But as you say, one would have to customize the job title,
because by
> default the job title will be based on the scene filename, where
you'll
> have the same issue again.
>
> But one question: Are you in fact rendering the same scene/same
frame
> range at the same time?
>
> Normally this is a bad thing, unless there's something to keep
their
> output separate (eg. rendering different layers).
>
> If two jobs are actively rendering the same scene/same frames,
there's
> the chance they'll corrupt each other, or give a mix of old and
new
> renders, as well as wasting cpu.
>
> If you resubmit the same scene/frame range, be sure to dump any
> previous renders of the same scene that might still be running,
> otherwise the two jobs will fight each other for both images and
logs.
> (I guess with your fix the logs won't overwrite, but the data
still
> will)
|