Announcement

Collapse
No announcement yet.

Changing the BF GI bounces crash V-Ray

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

  • Changing the BF GI bounces crash V-Ray

    I'm rendering using Interactive Rendering RTX (2 NVidia RTX 6000 48 GB each one) and changing the BF GI bounces from 3 to 16 using the slider, crashing V-Ray. I have to force close Rhino.
    V-Ray 5.2

    Click image for larger version

Name:	2021-11-07 21_27_54-Window.png
Views:	171
Size:	752.7 KB
ID:	1129667

  • #2
    Hi javierrentas ,

    I'm not able to reproduce the issue you've described.
    Can you share your test scene so that I can give it a go?

    Thanks in advance,
    Konstantin

    Comment


    • #3
      How can I share the scene? Where I should send it?

      Comment


      • #4
        Any free file sharing service works.
        Just send me the link in a direct message.

        Comment


        • #5
          Here is a simple scene. I guess the issue is related to SSS
          https://drive.google.com/file/d/1Uox...ew?usp=sharing
          Steps
          1. start IR
          2. Using the slider change the BF GI bounces to 16 or so.

          In my case, I got some errors.

          Comment


          • #6
            Thanks for the scene.
            I requested access.

            Comment


            • #7
              Hi javierrentas,

              The issue is 100% reproducible.
              I just logged it and the GPU team will have a look.

              Thank you once again for reporting it.
              Konstantin

              Comment


              • #8
                Awesome! Thank you for your great support!

                Comment


                • #9
                  Hi javierrentas,

                  The issue seems to be caused by the On-demand mipmapping option.
                  As a temporary workaround you can go back to Full-size textures:
                  Click image for larger version

Name:	GpuTexturesResize.png
Views:	95
Size:	106.8 KB
ID:	1130313

                  We'll do our best to resolve this quickly.

                  Regards,
                  Konstantin

                  Comment


                  • #10
                    Thank you for the workaround!

                    Comment

                    Working...
                    X