Announcement

Collapse
No announcement yet.

Long Compiling Scene Geometry phase on vrscene from revit

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

  • Long Compiling Scene Geometry phase on vrscene from revit

    Is there any workflow to speed up the "Compiling Scene Geometry" rendering phase in Max? Right now it takes 8 minutes before it finishes compiling. The same scene imported as FBX and rendered out is almost instantaneous. vrscene file is about 300mb, and has approx 70,000 objects.

  • #2
    If some of these objects are identical, using proxies would definitely speed up the process. Optimizing any displacement (with i.e. Edge length and subdivision) and Fur (with i.e. Lvl of detail and Knots) in the scene should help out as well.
    Aleksandar Hadzhiev | chaos.com
    Chaos Support Representative | contact us

    Comment


    • #3
      Its a revit based project so i'm sure there are duplicate "families" not sure if those get converted some how to instanced geometry or not when exporting the vrscene. no displacement or fur.

      Comment


      • #4
        Duplicated families do get exported as instances.

        Send us the Revit file archive, FBX and .vrscene so we can take a look. Do that like so:
        V-Ray > Settings > Paths & Sharing > check Export as Archive
        V-Ray > Render > Export V-Ray Scene
        Aleksandar Hadzhiev | chaos.com
        Chaos Support Representative | contact us

        Comment


        • #5
          Originally posted by cnd7jones View Post
          Its a revit based project so i'm sure there are duplicate "families" not sure if those get converted some how to instanced geometry or not when exporting the vrscene. no displacement or fur.
          It indeed looks like you have something creating a metric ton of *dynamic* geometry (i.e. created ad-hoc for the rendering phase).
          What does the memory usage look like when the process goes on for 8 minutes?
          It's enough to have one stray displacement with bad settings somewhere (it could be a modifier, or a shader.) to force v-ray to subdivide a lot.
          If the resolution is big, and edge length is in pixels, that could lead to enormous preparation times (as now displacement is calculated -by default- before the rendering phase starts. It's quicker that way.).

          In fact, the key part is that FBX (most certainly ignoring shaders and modifiers, along with any instancing) simply deals with plain geo, and duly flies when preparing the scene.

          Feel free to send us the scenes, as Alex suggested, but you may be quicker out of the issue if you can find the stray setting on your side.

          Lele
          Trouble Stirrer in RnD @ Chaos
          ----------------------
          emanuele.lecchi@chaos.com

          Disclaimer:
          The views and opinions expressed here are my own and do not represent those of Chaos Group, unless otherwise stated.

          Comment


          • #6
            Scenes sent as support ticket. I tried applying just a grey shader in revit and still get the issue. system resources don't get hit at all during the compiling phase.

            Comment


            • #7
              Thanks for the provided files. We've managed to reproduce the issue. I've logged it (internal bug-tracker id: VMAX-11540) for developer investigation. The issue seems to occur in 3ds Max only (works fine in Standalone), so it may be something the matter with the importer itself. I'll write back whenever there's more information.
              Aleksandar Hadzhiev | chaos.com
              Chaos Support Representative | contact us

              Comment


              • #8
                Aleksandar, wondering if any progress had been made on this topic? Thanks!

                Comment


                • #9
                  cnd7jones Not quite yet, I'm afraid.
                  Aleksandar Hadzhiev | chaos.com
                  Chaos Support Representative | contact us

                  Comment

                  Working...
                  X