Author Topic: No output listed under agenda/frames tab for cmdrange jobs  (Read 2141 times)

connnor.v

  • Full Member
  • ***
  • Posts: 10
No output listed under agenda/frames tab for cmdrange jobs
« on: January 30, 2013, 08:17:58 PM »
Ok, here's the problem:

I am running jobs on a network render farm. We just set up our mayabatches to submit to the farm with each layer as a separate job for each scenefile. Before, the prototype was "maya", and now it is listed as "cmdrange". When the prototype was "maya", we were able to browse the render directory by right-clicking on the "output" listed for each of the frames listed under the "agenda/frames" tab. However, now that the job protoype has changed to "cmdrange", no output is visible in this "output" section.

Now, while I can still locate the output directory by looking under the "Properties" tab, and scrolling down to the "Package" section, and finding "renderDirectory", I would much prefer the easier method of simply right clicking on the completed frames, and browsing the render directory that way. Is there a way to enable this function for "cmdrange" jobs, or am I out of luck?

jburk

  • Administrator
  • *****
  • Posts: 484
Re: No output listed under agenda/frames tab for cmdrange jobs
« Reply #1 on: January 30, 2013, 08:40:30 PM »
The issue is that the batchrender jobs (usually) don't print out the name to the rendered images, so we can't search the logs for the image path.

Which renderer are you using?  (also, if you have a valid software subscription, you can start a support case for this by sending mail to "support@pipelinefx.com").

BTW: submitting jobs per render layer in the Maya jobtype is something that has come up as a feature request before, but not many people have voted on it, so it gets pushed down the stack.  Would you like to cast your vote for this?

connnor.v

  • Full Member
  • ***
  • Posts: 10
Re: No output listed under agenda/frames tab for cmdrange jobs
« Reply #2 on: January 30, 2013, 08:59:32 PM »
I see, that's what I was afraid of.

We're using Mental Ray as our renderer. If the solution for this issue could be found more easily by sending mail to support@pipelinefx.com, I'll definitely give that a try.

As for voting for a feature that supports submitting jobs per render layer in the Maya jobtype, YES, I would love to see something like that. As far as I know, this is a commonly used way of rendering large jobs over a spread of available CPUs in a more timely manner.

Thank you very much for your speedy reply!