Leonardo Bernardini

Forum Replies Created

Viewing 15 posts - 391 through 405 (of 492 total)
  • Posted in:
  • 17th December 2007 at 6:41 pm #14762

    got it ;)

    17th December 2007 at 6:40 pm #14761

    job history / archivation are under redesign for future releases. So you can expect this feature in the near future ;)

    22nd November 2007 at 1:58 am #14755

    error 211 isn’t a Muster error, it’s a not-standard error code reported by Maya. As you already understand, 211 is a file system problem. There’s really little Muster can do about that apart from scheduling an automatic missing frames check.
    Keep in mind that file access problems may raise under heavy network usage, your connection to the shared contents may be lost for a timeout.
    What are you network specs ? and size of the farm ?

    22nd November 2007 at 1:55 am #14754

    As the log says, no comp has been given, or check that your comp name (s17) really exists in the scene..

    22nd November 2007 at 1:54 am #14753

    that’s definitively doable, we already scheduled it as medium priority so you can expect the feature in the near future.

    Cannot understand what thorlyn means with “having controls over how many processors it uses”. That’s already doable in the client preferences, if you want it on a job directly, it’s doable through a custom param in the job template even it discourage me. Having this feature on a job basis really give a lack of control…

    22nd November 2007 at 1:51 am #14752

    Confirmed by VV Staff ;)

    21st October 2007 at 7:03 pm #14745

    Maybe giving the option to limit the number of working instances…..why not..

    21st October 2007 at 7:02 pm #14744

    – templates must be configured by hand. We may provide some gui in the future, but that’s at low priority actually…

    – you can easily made a custom job template, where you accept the executable as an argument to the template..

    – Regarding single thread jobs, you can run the renderclient as multiple instances as suggested in the manual for single-threaded jobs.

    21st October 2007 at 6:58 pm #14743

    If the linux box is the dispatcher, you’ve to configure it in the following way:

    local: /mnt/fileserver
    win path: \fileserver
    linux path: /mnt/fileserver
    mac path: What you like

    6th October 2007 at 9:56 am #14740

    Check that your jobs doesn’t fall in the exclusion lists. If that happens, check the Explorer log pane, it will always report a reason for the failure. Muster doesn’t go on to prevent a rendering loop and/or wasted rendering times…

    6th October 2007 at 9:54 am #14739

    We are working on python integration as well as pure C++ SDK. The improvements are scheduled for version 5 releases (maybe 5.4). This will off-course include pre-frame/post-frame/pre-chunk/post-chunk/pre-job/post-job scripts as well.

    6th October 2007 at 9:53 am #14738

    Timeouts are handled by the heartbeat, double check your config, you shouldn’t get any kind of timeout if hb is disabled…

    6th October 2007 at 9:51 am #14737

    The log sharing path is streamed to Muster explorer to allow you to check the logs on the remote clients. There’re few ways to set it up under Linux, like setting up a local Samba server (then your log became available under \mypcmyshare) or just redirect the logs on a network server..

    20th August 2007 at 11:30 pm #14730

    When you say “The job will stop” what do you mean exactly ? Do you get a red ball under the “j” or “t” column ? Do you get any red line in the Explorer log pane ?

    I need further info to help…

    Regards.

    20th August 2007 at 11:29 pm #14729

    then that’s clearly an account problem. How do you configured the Muster account for the services ? Also, is Muster installed on the server hosting the files ? If no, then the default Muster account is not created , and you should run the MsAddUser.exe utility included in any installation….

Viewing 15 posts - 391 through 405 (of 492 total)