Announcement

Collapse
No announcement yet.

backburner how to

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • backburner how to

    got this problem:
    dumb backburner when sees that frames render very fast like in few seconds desides that it should assign batches of frames for each node. IS there a way to turn this off?
    Dmitry Vinnik
    Silhouette Images Inc.
    ShowReel:
    https://www.youtube.com/watch?v=qxSJlvSwAhA
    https://www.linkedin.com/in/dmitry-v...-identity-name

  • #2
    Not that I've found, and it's ruined renders for me.

    Comment


    • #3
      Looks like this is the solution:

      http://usa.autodesk.com/adsk/servlet...linkID=5573345

      Comment


      • #4
        ya ive seen that too. can be a pain in the ass.
        ____________________________________

        "Sometimes life leaves a hundred dollar bill on your dresser, and you don't realize until later that it's because it fu**ed you."

        Comment


        • #5
          anyways, if you go to submit network job, go to advanced and at the bottom uncheck Enable Task Blocking. Thats exectly what it is, thanks Dynedain.
          Dmitry Vinnik
          Silhouette Images Inc.
          ShowReel:
          https://www.youtube.com/watch?v=qxSJlvSwAhA
          https://www.linkedin.com/in/dmitry-v...-identity-name

          Comment


          • #6
            What kind of problems would this batching cause?
            Kind Regards,
            Richard Birket
            ----------------------------------->
            http://www.blinkimage.com

            ----------------------------------->

            Comment


            • #7
              Thx for the hint...saved my day...or my night...or my deadline as you wish

              @tricky :

              we got a sequence here wich we render with "skip existing" turned on...now backburner assigns like 30 tasks to ONE slave....BUT the slave RENDERS the image and THEN checks when writing to skip it because it´s existing already. As we got 60 slaves. In a case when 30 Tasks are left they are ALL assigned to one slave, wich has to render ALL the files before skipping quite a bunch...while the rest of the farm is idle.

              Sorry if this description is confusing, but am on a workaholic hangover

              Thorsten

              Comment

              Working...
              X