alexx

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Back to forum
    Posted in: Current progress and more – 9.5 status
  • alexx
    20th January 2009 at 9:27 am #14897

    hi alec,

    leo, this is exactely the problem i am haveing as well with my renderfarm as i already wrote you in a short mail.

    alec:
    what muster version are you useing?

    anyway: i am not so 100% sure if this is a maya problem. the problem is that autodesk says that this is a muster problem and that muster says it is an austodesk problem.

    and yes; it is more than annoying since it gets terrible hard to judge if a rendering really has a problem or just outputs this error message.

    cheers

    alex

    alexx
    23rd November 2007 at 9:26 am #14758

    yes,

    on a per job basis or with the global setting in the render client is already possible but not the intended behaviour.

    the way described above (and i think you got that one right leo) is wanted: a dynamic possibility to change that behaviour.

    even one more: being able in muster explorer to assign the amount of CPUs used by right clicking on the client would be desireable and great.

    cheers

    alex

    alexx
    20th November 2007 at 1:00 pm #14750

    since the command line features of maya have not been changed from 8.5 to 2008, all works the same as before

    cheers

    alex

    alexx
    20th November 2007 at 12:59 pm #14749

    any comments from the developers?

    cheers

    alex

    alexx
    11th October 2007 at 2:59 pm #14741

    since i am currently working on the same problem:

    the problem is the following:
    if you create these layer overrides in maya and batch render it. mayas renderer checks what is written in the render globals and which overrides are set..
    this works like expected:
    render myscene.mb

    but as soon as you would try to do the following:
    render -s 1 -e 10 myscene.mb
    all your render layers will render from frame 1 to 10 because you override (!) the values set in the render globals – no matter in which layer or if they already had layer overrides on them.

    the problem: muster has to do exactly that external override to be able to render the images on a renderfam.

    since i noticed that problem quite some time ago, i am currently writing some MEL to be able to submit a single scene several times to muster, and have it only render the desired frame ranges.

    to be honest: i am not using the muster connector tool at all. so i have no idea what it is capable of. i am using a self written MEL code to submit all our jobs to muster.
    maybe if you ask nicely leo can implement that functionality some day :)

    but for you as a workaround:
    save your scene once with all correct settings in it. only make the layers renderable, that have the full frame range. submit that one to muster.

    for the missing render layers that have different frame ranges you can now add another submission to muster which has additional parameters:
    -rl renderLayer1,renderLayer2,…,renderLayern
    like that you make sure only these render layers are rendered abd you can enter their respective frame range in muster.. all from one single scene file.

    cheers

    alexx

Viewing 5 posts - 1 through 5 (of 5 total)