Announcement

Collapse
No announcement yet.

Question about stop time with Vray GPU using "Render with Vray Standalone"

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

  • Question about stop time with Vray GPU using "Render with Vray Standalone"

    Hello,

    I've a question about this topic.

    I'm using the "Render with Vray Standalone" with the GPU render. I've set the stop time at "Noise Level" 0.005. But looking at the log file stamp in the Terminal, I notice that even if Vray GPU reached that 0.005 noise level, the render goes on for other minutes, mostly the double then he was supposed to stop. The image visual seams to not change so much in noise quality in this extra time... Is there some sort of bug or there's some extra calculation behind the scene to be done?

    I attach some screenshots.


  • #2
    Hey, axelts,

    Thank you for the feedback. Is there a chance to get statistic at the end of the log with Render time, passes etc.

    Cheers,
    Boyan Nalchadjiiski | QA Engineer @ Chaos |
    E-mail: boyan.nalchadjiiski@chaos.com

    Comment


    • #3
      Originally posted by boyan View Post
      Hey, axelts,

      Thank you for the feedback. Is there a chance to get statistic at the end of the log with Render time, passes etc.

      Cheers,
      Let me know if there's a way to save it. When i render with the "Render with Vray Standalone" I just got a Console window open but when the process end there's no a way to direct save it, at least I can do a copy - paste in a .txt file and send to you...

      Comment


      • #4
        Howdy,

        Actually, no need to send me the log file or screenshot of it. Currently, there is an issue with this message and to be clear if you reach the value it doesn't mean that the render should stop. It's meaning that you've been reached the threshold value but there are many active pixels to be rendered. This is confusing and in a feature, will be changed. The fix will be added in V-Ray Next release.

        Cheers,
        Boyan Nalchadjiiski | QA Engineer @ Chaos |
        E-mail: boyan.nalchadjiiski@chaos.com

        Comment


        • #5
          Originally posted by boyan View Post
          Howdy,

          Actually, no need to send me the log file or screenshot of it. Currently, there is an issue with this message and to be clear if you reach the value it doesn't mean that the render should stop. It's meaning that you've been reached the threshold value but there are many active pixels to be rendered. This is confusing and in a feature, will be changed. The fix will be added in V-Ray Next release.

          Cheers,
          Thanks! I was guessing that there was some work for the render engine to still be done after reaching the Max Noise value, but I wasn't sure. Thanks for the confirm and waiting for a Vray Next Nightly!

          Comment


          • #6
            Today I did some test more.

            I want to render a scene with the "Render with Vray Standalone" using the GPU engine. I set as stop time noise threshold to 0.005. I did some tests before with lower resolution (1400px on longer size) and everything was working except the note I've written above.

            Well, testing today the same scene with a higher resolution (5000px on the longer size) I got the renderer to not stop. The terminal log was showing it reached the 99% of the process in 1h 56m. Then it got "stuck" at 99% for more than an extra 35 minutes. At that point, I've killed the process thinking it was something wrong going on. Of course I can save the .vrimg file from the VFB but in this way I can't program a batch using the Modo Render passes.

            The same thing seems to happen if I launch the render inside Modo still using the GPU engine. The process seems to go on forever without stopping.

            I'm using the GPU + Hybrid option.


            Comment


            • #7
              Hey, axelts,

              Thanks for the feedback, in particular, this is the same behavior.

              Cheers,

              btw, You can try these rendering settings. In most cases, you can use this preset.

              Click image for larger version  Name:	modo_2018-09-10_12-23-25.png Views:	1 Size:	43.3 KB ID:	1010502
              Last edited by boyan; 10-09-2018, 02:28 AM.
              Boyan Nalchadjiiski | QA Engineer @ Chaos |
              E-mail: boyan.nalchadjiiski@chaos.com

              Comment


              • #8
                Originally posted by boyan View Post
                Hey, axelts,

                Thanks for the feedback, in particular, this is the same behavior.

                Cheers,

                btw, You can try these rendering settings. In most cases, you can use this preset.

                Click image for larger version Name:	modo_2018-09-10_12-23-25.png Views:	1 Size:	43.3 KB ID:	1010502
                Thanks for the suggestion, although you don't think that 0.001 for the noise threshold is a bit too low value? I think a range between 0.005 and 0.007/0.008 is a good balance between quality and speed (with maybe little kick of the denoise in post).

                So the fields "Max Noise" and "Max Paths per Pixel" are evaluated together? The first that reach the condition stops the render?

                Comment


                • #9
                  I've made a simple suggestion about how to speed up the render but of course, increasing the Max.noise value will decrease the render time.

                  Cheers,
                  Boyan Nalchadjiiski | QA Engineer @ Chaos |
                  E-mail: boyan.nalchadjiiski@chaos.com

                  Comment

                  Working...
                  X