Announcement

Collapse
No announcement yet.

Max. noise??

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

  • Max. noise??

    I have a scene were I'm using RT as the production render and setting the Max. noise doesn't seem to stop the render when the Max. noise threshold is reached.
    The render message windows says "Final noise threshold is set: 0.005000 and it just keeps running until I stop it. The VraySampleRate even turns completely blue.

    I'm using SP3.3 with BF/LC Cuda.
    "I have not failed. I've just found 10,000 ways that won't work."
    Thomas A. Edison

  • #2
    "final noise threshold set" doesnt mean its arrived at the final quality, it means its stopped reducing the noise threshold each pass, and is now working with the final noise threshold.


    im not sure, maybe you just didnt wait long enough? was the samplerate *completely* dark blue? ive not noticed this issue myself.

    Comment


    • #3
      Originally posted by super gnu View Post
      "final noise threshold set" doesnt mean its arrived at the final quality, it means its stopped reducing the noise threshold each pass, and is now working with the final noise threshold.


      im not sure, maybe you just didnt wait long enough? was the samplerate *completely* dark blue? ive not noticed this issue myself.
      I waited about half an hour after the "final noise threshold set" almost completely dark blue, I'm going to give it another try.

      Click image for larger version

Name:	Final noise threshold.jpg
Views:	1
Size:	481.4 KB
ID:	859419
      "I have not failed. I've just found 10,000 ways that won't work."
      Thomas A. Edison

      Comment


      • #4
        I'm re-rendering the scene...
        so far it's reached the Final noise threshold of 0.005. in 50 minutes, however, it's been 1 hour 30 min and it's still running.
        I also noticed that the GPU's are running only at about 30 percent power, their running cool between 50c and 55c so I'm not sure why.
        "I have not failed. I've just found 10,000 ways that won't work."
        Thomas A. Edison

        Comment


        • #5
          i believe when the quantity of pixels being worked on (i.e. when most of the image is resolved) drops below a certain level, it becomes harder to distribute it over the whole gpu, meaning lower utilisation at the end of the render. its been improved in the latest 3.3 versions, but still a factor. you can see the same result if you try to do a small region render.. your gpu/cpu will not be fully loaded.

          sounds like you have a few hard to shift areas in your scene!

          Comment


          • #6
            Originally posted by super gnu View Post
            i believe when the quantity of pixels being worked on (i.e. when most of the image is resolved) drops below a certain level, it becomes harder to distribute it over the whole gpu, meaning lower utilisation at the end of the render. its been improved in the latest 3.3 versions, but still a factor. you can see the same result if you try to do a small region render.. your gpu/cpu will not be fully loaded.

            sounds like you have a few hard to shift areas in your scene!
            I see..it's like the last bucket syndrome on GPU!.. My scene finally completed after 1 hour and 50 minutes, that 1 hour after the Final noise threshold set was reached.

            I'm going BF/LC the scene on CPU and see what happens.

            Thanks!
            "I have not failed. I've just found 10,000 ways that won't work."
            Thomas A. Edison

            Comment


            • #7
              Yes, this is something I'm experiencing since SP1 (over a year ago)

              For example, set all your settings to 0. Crop render on the noisiest part of you image, check see stats. You'll find out that fir some pixels, it renders with over than 250.000 point per pixel (PPP) and it takes ages, but it would be exactly the same as if you let it render to 5-10k PPP for only few minutes of render.

              That's why when I render, I always use a max PPP at something like 20k AND a noise threshold.
              This will avoid having your exact situation as it will render to sample your noise but crop at X PPP for those few pixels that "would" need more, but who really don't need to be refined like you had.

              Hope this make sense

              Stan
              Last edited by 3LP; 02-01-2016, 02:18 PM.
              3LP Team

              Comment


              • #8
                Originally posted by 3LP View Post
                Yes, this is something I'm experiencing since SP1 (over a year ago)

                For example, set all your settings to 0. Crop render on the noisiest part of you image, check see stats. You'll find out that fir some pixels, it renders with over than 250.000 point per pixel (PPP) and it takes ages, but it would be exactly the same as if you let it render to 5-10k PPP for only few minutes of render.

                That's why when I render, I always use a max PPP at something like 20k AND a noise threshold.
                This will avoid having your exact situation as it will render to sample your noise but crop at X PPP for those few pixels that "would" need more, but who really don't need to be refined like you had.

                Hope this make sense

                Stan
                Thanks! good tip on setting the max PPP as well. It's probably why my GPU renders take so long I've been comparing noise thresholds with Adv CPU.
                The render I stopped looks just about identical to the one I let finish an hour later.
                "I have not failed. I've just found 10,000 ways that won't work."
                Thomas A. Edison

                Comment


                • #9
                  Glad it worked out for you

                  Stan
                  3LP Team

                  Comment

                  Working...
                  X