Announcement

Collapse
No announcement yet.

Scene hangs at Transforming Verticies

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

  • Scene hangs at Transforming Verticies

    I have a retail store model that fails to render when Xref'd. It hangs at the Transforming Verticies stage. If I merge the file it renders okay. I have to deal with multiple options for store layouts in other files and another person is working on the store model, so referencing the files would be ideal. Not sure how to debug this scene. At the Transforming Verticies stage I can see in the Task Monitor that Max is continuing to use up memory. The only thing I can do is kill the Max process.

    Windows 7 Enterprise 64bit
    Dual Xeon X5687
    RAM 24GB
    Max 2012 pu10
    Vray 2.30.01

  • #2
    I managed to find the culprit. I stripped out each layer to a separate Max file and Xref'd each one until I found the problem child. It turned out to be a simple fluorescent light. More precisely it was a VrayLightMtl which had Direct Illumination enabled. If I disable Direct Illumination it will render fine as an Xref.

    There are separate materials for the light strip fixture and light tube, ie. no Multi/Sub Object materials. The light tube and light fixture are separate objects.

    I looked at the Vray help files and didn't find any limitations when using direct illumination in an Xref file.

    http://www.spot3d.com/vray/help/200R..._light_mtl.htm


    Here is the problem light fixture:
    https://www.box.com/s/dfz6aaza0xchsf539fx4

    Comment


    • #3
      This is a pesky bug that has unfortunately been around quite a while and so far not been fixed. Maybe the next update? Anyone from Chaos care to comment?

      http://www.chaosgroup.com/forums/vbu...angs-XrefScene
      Christopher Grant
      Director of Visualization, HMC Architects
      Portfolio, ChristopherGrant.com

      Comment


      • #4
        Originally posted by cgrant3d View Post
        This is a pesky bug that has unfortunately been around quite a while and so far not been fixed. Maybe the next update? Anyone from Chaos care to comment?
        Right now I do not know how to fix it, unfortunately. There appears to be little that we can do, but are still looking for options.

        Best regards,
        Vlado
        I only act like I know everything, Rogers.

        Comment


        • #5
          @cgrant3D - Thanks, I did a search and didn't see that post.

          @vlado - Okay. At least its a consistent behavior I can work around.

          Comment


          • #6
            Well actually one of our programmers found a solution for this; it is implemented in the nightly/stable builds for tomorrow and will go into the next service pack.

            Best regards,
            Vlado
            I only act like I know everything, Rogers.

            Comment


            • #7
              You guys ROCK! Looking forward to the next release.

              Comment


              • #8
                looking forward for the update

                Comment

                Working...
                X