Maya render log errors always reported = annoying

Viewing 4 posts - 1 through 4 (of 4 total)
  • Back to forum
    Posted in: Muster usage
  • Alec McClymont
    16th January 2009 at 11:28 pm #14303

    I’ve got Maya 2009 rendering successfully through Muster, so this problem is really more of an annoyance. Maya jobs always report errors upon loading. This means that even though a chunk or frame will render just fine, Muster flags it as having an error. When a “real” error is encountered, it really becomes annoying to track down which frame is responsible.

    I’ve discovered a difference between my Maya log files depending on the account under which the Muster service runs. If Muster is running under a “Render” account with standard permissions, the log file appears like this:

    Quote:
    …
    Starting “C:Program FilesAutodeskMaya2009binmayabatch.exe”
    mental ray for Maya 10.0
    mental ray: version 3.7.1.26, Jul 30 2008, revision 26576
    File read in 0 seconds.
    Result: ***scene file***
    mental ray: got 8 satellite CPUs.
    MEM 0.0 info : heap size limit set to 1488 MB
    Info: (mental ray) : number of render thread(s): 4
    Info: (Mayatomr.Nodes) : custom string options found
    Info: (Mayatomr.Nodes) : derive mental ray global approximation settings from Maya
    Info: (Mayatomr.Nodes) : derive mental ray global displacement settings from Maya
    Info: (Mayatomr.Scene) : update lights and related shaders
    Info: (Mayatomr.Scene) : update cameras and related shaders
    Info: (Mayatomr.Scene) : update geometry and materials
    Info: (Mayatomr.Scene) : render camera: persp
    ….etc

    Seems normal. However when the Muster service runs under the “Administrator” account, as it must to have permissions to save Muster config settings, the log file appears as such:

    Quote:
    …
    Starting “C:Program FilesAutodeskMaya2009binmayabatch.exe”
    mental ray for Maya 10.0
    // mental ray for Maya: using startup file C:/Program Files/Autodesk/Maya2009/mentalray/maya.rayrc
    mental ray for Maya: setup
    mental ray for Maya: initialize
    mental ray: version 3.7.1.26, Jul 30 2008, revision 26576
    mental ray for Maya: using 1 license
    mental ray for Maya: register extensions
    // mental ray Node Factory: loaded
    Error: file: C:/Program Files/Autodesk/Maya2009/scripts/others/miImfkeyOverrideScriptJob.mel line 37: No object matches name: renderLayerManager.renderLayerId
    mental ray for Maya: successfully registered
    mental ray for Maya: loading startup file: C:/Program Files/Autodesk/Maya2009/mentalray/maya.rayrc
    // parsing C:/Program Files/Autodesk/Maya2009/mentalray/include/AdskShaderSDKWrappers.mi
    // generating Maya nodes…
    // parsing C:/Program Files/Autodesk/Maya2009/mentalray/include/architectural.mi
    // loading C:/Program Files/Autodesk/Maya2009/mentalray/lib/architectural.dll
    // generating Maya nodes…
    // parsing C:/Program Files/Autodesk/Maya2009/mentalray/include/base.mi
    // loading C:/Program Files/Autodesk/Maya2009/mentalray/lib/base.dll
    // generating Maya nodes…
    // parsing C:/Program Files/Autodesk/Maya2009/mentalray/include/contour.mi
    // loading C:/Program Files/Autodesk/Maya2009/mentalray/lib/contour.dll
    // generating Maya nodes…
    // parsing C:/Program Files/Autodesk/Maya2009/mentalray/include/paint.mi
    // loading C:/Program Files/Autodesk/Maya2009/mentalray/lib/paint.dll
    // generating Maya nodes…
    // parsing C:/Program Files/Autodesk/Maya2009/mentalray/include/physics.mi
    // loading C:/Program Files/Autodesk/Maya2009/mentalray/lib/physics.dll
    // generating Maya nodes…
    // parsing C:/Program Files/Autodesk/Maya2009/mentalray/include/production.mi
    // loading C:/Program Files/Autodesk/Maya2009/mentalray/lib/production.dll
    // generating Maya nodes…
    // parsing C:/Program Files/Autodesk/Maya2009/mentalray/include/subsurface.mi
    // loading C:/Program Files/Autodesk/Maya2009/mentalray/lib/subsurface.dll
    // generating Maya nodes…
    // parsing C:/Program Files/Autodesk/Maya2009/mentalray/include/surfaceSampler.mi
    // loading C:/Program Files/Autodesk/Maya2009/mentalray/lib/surfaceSampler.dll
    // generating Maya nodes…
    File read in 3 seconds.
    Result: ***scene file***
    mental ray: got 8 satellite CPUs.
    MEM 0.0 info : heap size limit set to 1508 MB
    Info: (mental ray) : number of render thread(s): 4
    Info: (Mayatomr.Nodes) : custom string options found
    Info: (Mayatomr.Nodes) : derive mental ray global approximation settings from Maya
    Info: (Mayatomr.Nodes) : derive mental ray global displacement settings from Maya
    Info: (Mayatomr.Scene) : update lights and related shaders
    Info: (Mayatomr.Scene) : update cameras and related shaders
    Info: (Mayatomr.Scene) : update geometry and materials
    Info: (Mayatomr.Scene) : render camera: persp
    …etc

    Same scene file, same job settings, but with the Muster service running under different accounts. Obviously I need the service to run under the “Administrator” account, but the extra log errors are an annoyance when trying to manage jobs in the Muster Explorer. Turning down Maya’s error reporting isn’t really an option, since it would lead to meaningless log files making troubleshooting scenes even harder.

    I should note that the Maya scene renders and outputs properly in both cases.

    I know this may be more of a Maya issue than anything to do with Muster, but I thought someone else may have run into this before. If so, I’d love to hear a solution.

    Thanks!

    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

    Alec McClymont
    21st January 2009 at 9:12 pm #14898

    I’m just in the process of upgrading to Muster 5.5.4. This is my first real use of version 5.x since we’ve been running 4.52 for quite a while, but even then had the same issue with Muster reporting Maya errors all the time.

    Good to know that you’ve asked Autodesk about it. I still haven’t been able to find a solution, however.

    Leonardo Bernardini
    3rd July 2009 at 4:54 pm #14967

    Well, we are going to put log parsing overrides in Muster 6 so this is going to be configurable…about that maya error, you’ve a good techical background , and understand that we’re just spawning a render.exe process in the end….how can this be a Muster problem :)) ?

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

You must be logged in to reply to this topic.