Announcement

Collapse
No announcement yet.

Vray proxy render flicker/errors

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

  • Vray proxy render flicker/errors

    Hello, I have been running into an issue with certain vray proxy objects having issues rendering. They have black/dark areas within the render. These areas flicker a bit through the animation. On some building objects, they disappear after the building starts its breaking animation.

    Click image for larger version

Name:	ProxyError.jpg
Views:	1
Size:	77.8 KB
ID:	882799

    The error seems persistent through AOVs as well

    Click image for larger version

Name:	ProxyError_b.normals.jpg
Views:	1
Size:	55.9 KB
ID:	882800
    normals

    Click image for larger version

Name:	ProxyError_a.multimatte.jpg
Views:	1
Size:	85.4 KB
ID:	882801
    multimatte

    Changing the scale of objects or repositioning the camera simply changes the shape/positioning of the errors.

    Click image for larger version

Name:	ProxyError2.jpg
Views:	1
Size:	27.9 KB
ID:	882802

    The errors are independent of the shader as they still appear with the default material applied and they remain solid in the alpha channel.

    The proxy file itself is fairly large (10GB) as it is a 200frame sequence that contains a couple 100k faces and it was created with the same version of vray that I am rendering with. I have tried pulling the file through both the network and accessing it from a local path. It does not appear affected by GI as it persists when GI is disabled and same goes for DR. Turning on "Show whole mesh" doesn't show any visible mesh issues in viewport, and if I render the full surface with Maya Software, I do not see the errors.

    The geometry itself is a fractured object that has a destruction simulation baked on which was then all exported as a vray proxy for smaller scene sizes and quicker render times (less scene translation time). The errors in the render are reminiscent of view clipping issues that you get when faces are closer together which the fragments may be causing. So perhaps this is the problem? Vray renders the original scene (where every fragment is a maya mesh that is animated) without these errors. Is there something that can be tweaked in the exporting, or within the scene the proxy is imported into?

    VRay 3.10.01 Maya 2015 Ext 1 SP6
    OSX Yosemite 10.10.3

    Thanks!
    Alex
    Last edited by arideout; 16-09-2015, 09:22 AM. Reason: more info

  • #2
    I just found a possible solution. If I scale the scene down to 1/100 the current scale (which is semi-real-world), then it seems like the errors disappear. Perhaps there is an issue with the way proxy object handle world space and rendering at larger scales?

    Comment


    • #3
      Can you try to reproduce the problem with a proxy that has a single frame or just a few frames?
      If you can and it reproduces the same, can you send the proxy to our support for further investigation?

      This looks like a precision bug and it should be fixed.
      V-Ray developer

      Comment


      • #4
        I have sent it over in a PM. Thanks for taking a look!

        Comment


        • #5
          Please send an email to support @ chaosgroup.com
          V-Ray developer

          Comment


          • #6
            Did you find any solution for this? We may be having similar issues.
            Patrick Macdonald
            Lighting TD : http://reformstudios.com Developer of "Mission Control", the spreadsheet editor for 3ds Max http://reformstudios.com/mission-control-for-3ds-max/



            Comment


            • #7
              Originally posted by re:FORM View Post
              Did you find any solution for this? We may be having similar issues.
              Sent the scene and setup off to the devs since it appeared to be a bug. Temporary fix was to scale down the scene by putting everything under a group node and scaling that down. Might work with a post translate script as well, but we went with the scale down method. Not ideal for some situations, but a quick fix if you can get away with it.

              Comment


              • #8
                There is also a work-around to set this env vray - VRAY_USE_QNDTREE to 0.
                V-Ray/PhoenixFD for Maya developer

                Comment


                • #9
                  Originally posted by ivaylo.ivanov View Post
                  There is also a work-around to set this env vray - VRAY_USE_QNDTREE to 0.
                  As Patrick mentioned earlier, we were having a simillar issue. The env variable seems to have solved it.
                  We were having some weird flickering and face becoming black, even when the geometries weren't touching.

                  Thanks,

                  Yannick
                  Portfolio: http://www.cgifocus.co.uk

                  Comment


                  • #10
                    Is this not the same bug mentioned in another thread, where the maya proxy exporter saves multiple copies of a mesh in the vrmesh ?

                    Comment


                    • #11
                      These are dfiferent issues.
                      V-Ray/PhoenixFD for Maya developer

                      Comment

                      Working...
                      X