Batch render don't stops, help!

[belafonte]

Hi there,
Somebody can help me to stop batch render?,
I have maya 2009 and batch render don't stops to render when has finished, it continues ever and ever, I select 'cancel batch render' button´s from shelf menu, but isn't working, and it continues until I have to restart the computer to stop it.
If someone know how to stop it or has any script on mel, or any way to do this batch render, please let me know, it´s exhausting restart ever and ever to finish the work.

Thanks

[belafonte]

Ok, in the meantime I found a rustic solution but it works, going to the task manager you can kill the 'mayabatch.exe' process's, and that's it.
If somebody knows another solution please let me know.
I'm looking for a script in MEL to fix this batch render Maya 2009 issue's.
Thanks

[joojaa]

Do you use render layers?

[belafonte]

Joojaa:Do you use render layers?

No, I just using the default Master Layer.
Do you think layers have something about this issue?
Because Im using just the master layer in normal mode.
What other thing could be...Now I think it's a Maya 2009 bug.
What else could it be...

[joojaa]

Well render layers used to have a bug in the mel scripts, where a scene with render layers would render over and over and over again. Its quite easy to fix tough.

Now I think it's a Maya 2009 bug.

Well thing is the renderer is compiler of sorts. And since its a open ended system theres nothing one can do from letting the user do this. After all its meant to do exactly what the user tells you to do. That in itself is not a bug. Also one can not blame things as a bug you need to be MUCH MUCH MUCH more specific than this befiore you can draw any such conclusions. Besicdes saying its a bug and leaving things at that dioes not help you anything. It never does.

This unfortunately has a tendency to back fire with novice users because they cant help themeselves once they drop themselves into a situation like this. So theres no way of telling a system thas been designed to do exactly what told to not do what its told to do. Except offcourse being carefull for what one wishes for.

So no it definitely does not do this by default and it never seems to do this for me. But thats expected I would instantly recognize the problem before it would arise. Its a bit hard to debug this as you have no clue on what it is you might be doing and im left guessing as to what the problem might be.

Is it possible the renderer is blocked by a firewall and is left searching for the licensing server?

Easiesets is offcourse if you start from scratch but tahts a bit time prohibitive.

[belafonte]

joojaa:"After all its meant to do exactly what the user tells you to do. That in itself is not a bug."

Definitely it´s a Maya 2009´s bug, first because the render don't stops when you tell it to stops, second because I have too the Maya 2008 version and the batch render works perfectly, it only happens in Maya 2009, and there is not only me with this issue, I know a bunch of people with this same thing, I think you must have to check out on the net before criticize when somebody search for help.

joojaa:"This unfortunately has a tendency to back fire with novice users because they cant help themeselves"

Looking for help it´s precisely a way to don´t give up, ask for help is a way to help oneself, to help another ones. So if you have good will to help somebody, you can´t criticize in exchange for your help, better don´t help to nobody, don't forget that no one knows eveything about everything, everyone it´s a teacher and a student at same time, be humble when teaching and be humble when learning and maybe you will reach a little of truly wisdom.

[joojaa]

Nono thats not what im saying.

When you say "BUG" you are opting out the problem. You stipulating you didnt have anything to do with the problem. Wich may or may not be the case. Even IF 2,000,000 people would experience this problem does NOT mean it is a bug (its a indication of unsuccessful planning but it may be on purpose, thus not a bug). It might be a new feature you are not aware of.

The simple fact is that until you know for SURE whats causing this then you can not say its a bug. Period thats simply how it works.

you can´t criticize in exchange for your help,

I am not criticizing. Im trying to explain why you can not at this time be helpped. You just need to have a more open mind than this. Saying its a bug is a mental dead end. You are there. At the mental dead end.

But by the way: Yes I can do what the hell it is i want as long as its not illegal and theres nothing you can do about that If you want to see it as criticism than thats up tp you unfortunately, nothing i can do. But yes the only ay to avoid looking at own flaws is not to do anything ever. So by posting you are up to critique unfortunately, if you choose to see things that way.

the Maya 2008 version and the batch render works perfectly, it only happens in Maya 2009.

Still does not necceserily indicate a bug on autodesks part! It might, but IF you are certain its a bug on autodesks side the why are you not going to:

adn.autodesk.com

for your solution? Or atleast contact your reseller. See if it really is a autodesk bug then there's nothing anybody out here can do. A quick scan of the bug database says that theres either no solution or nobody has reported it.

Now then so let us step back form the blame and look at the problem.  Wether or not its a bug or not des not really help you. You mus habve some constructive way of attacking the problem:

is it just this scene?

make a empty scene and put cube into it, no animation no nothing. does that terminate after you render? If you render several frames does it terminate?

IF it terminated then you nee dto pen your scene. delete half of it and redner, does it terminate if not you know the problem is in this half, delete half again repeat. Untill you know whats causing it.

Now if this was unsuccesfull:

What if your environment is screwed, 2009 did introduce a new licencing system:

First, disconnect your computer form the outer world, so you just leave your licencing server and you intact in your network. This is meant to attack a licencing reachability problem.

kill all firewalls on the way, open up your systems protected ports.

Second disconnect all the slaves, just do it on one mechine. Thsi attacks the problem of a slave connection dying the computer is waiting for it.

If this fails, trace the execution, put a script thet prints frame currentkly being used in the post rendre script. Thsi mey help track the problem. Does it turn up on itself?

be humble when teaching and be humble when learning and maybe you will reach a little of truly wisdom.

I am humble, its just you choose not see it that way. If i wasn't humble i wouldnt be writing all theese posts i do. I would just screw all of you I just dont have time for mothering you guys. I say it as i see it, you deserve that. Writing im sorry for your troubles don't ultimately help you anything.

Im not infallable, in fact i LOVE persons who can show me wrong. Because one wrong is way better than untold rights. So im actually setting myself up for being shown wrong. Not just tiny but wrong but terribly wrpng. But i dont see any takers.

PS: When i say i dont have time to be diplomatic its because i dont get paid to do so. At work i have a personal diplomacy filter to re-wirte write my answers to the clients in a diplomatic manner. Because then I can afford to do so. But the way i see it having filtered this way does make all communication about diplomacy and it slows thinsg down considerably.

I dont care whether or not its anybodys fault, if it needs fixing then it can only be fixed by partoes willing to work for a fix. And yes its always your problem no matter if you can do anything about it or not (also means its my problem by proxy, theres no other peoples problems just problems we all share). Sorry just my experience of life. But hey you can look at all problems and say well a tleast this works.

[belafonte]

Wow! Great!, that was a big one
You are a smart guy

thanks for be honest, I appreciated. A sincere word worth more than a thousand ones.

The thing about this issue is when I ask for help is because I already have tried to much to fix the thing.
When I called this one a "Bug" I meant an "unsolved" issue. Not a irreparable one, not a dead end.

In fact I think a software "bug" has a solution, I know this kind of things could be solved with a MEL script, that's the only thing haven't tried because I'm not to good on this to write it, I mean, I know some things, but a complete script to fix a "batch render" issue is away from me.

That's why from the beggining I ask for some script to solve this, because I exhausted all the other ones (like doing new scenes to test it out, with render layers, without render layers, with a single and simple mesh, with many meshes, with maya software, with mental ray etc. setting this, setting that and back an forth) To me is a pleasure to explore different ways to solve a thing, I love to experiment, and this case is not an exception, and the only way I found out was to kill the process from the "task manager" and it works, I told this from almost the beggining in my second reply in case this help to somebody .

So Joojaa right now I 'm looking for a Mel script to to batch render from script editor I think it's a good idea to have a second shelf button just in case the Maya native one fails (as happens in my case and to another ones). Maybe there is a lot of things I forgot to mention but I hope the big picture of this has been understood.

So that's it, is just a tiny software issue, and maybe the stars are laughing at us.

Thanks for your help and for your commitment

[joojaa]

I have a working hypothesis that i havent gotten around to test.

They added backburner into maya 2010, which i am not planning to use, and not using because i have my own dispatch. But it would make sense to not restart maya after each render. So maybe its waiting for backburner to terminate it/ or motre jobs.