Author Topic: "Stuck" subjobs ?  (Read 2496 times)

p-a-rak

  • Jr. Member
  • **
  • Posts: 6
"Stuck" subjobs ?
« on: February 17, 2009, 01:27:39 PM »
When I submit a 3dsmax render (Not Batch render), via the 3dsmax plugin (64-bit), max fires up on whatever number of worker machines I specified.
However, when subjobs don't actually get frames assigned to them, the subjobs just sit there, marked as "running".
Setting them to "complete" doesn't seem to shift them.

Now, I remember Troy mentioned this last week (QCA class, London), but I cannot remember the solution. (perhaps this was in my "lost" day2 notes.. Grr..)

How do I get the unused subjobs to go away when the job has finished the agenda items?




siyuan.pipelinefx

  • Sr. Member
  • ****
  • Posts: 32
Re: "Stuck" subjobs ?
« Reply #1 on: February 19, 2009, 04:47:34 AM »
I think the solution is just to use the batch rendering in qube.  This is a known issue with the 3dsmax plugin as the 3dsmax won't return any thing back to qube to signify that it finishes running, so it's best if you just use batch render because it provides a more expected solution.  Hope this helps.

p-a-rak

  • Jr. Member
  • **
  • Posts: 6
Re: "Stuck" subjobs ?
« Reply #2 on: February 19, 2009, 12:28:34 PM »
Ok. That's pretty much what I thought.
I'll stick with the batch submission.