Announcement

Collapse
No announcement yet.

(Fixed, Open) [HOU-1397,1407] Merged volumes render incorrectly

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

  • (Fixed, Open) [HOU-1397,1407] Merged volumes render incorrectly

    Merged volumes render incorrectly. The last-merged volume renders for all 3 volumes.

    See the attached still, viewport on the right render on the left.

    File:
    bug file

    Windows 10
    Houdini 17.5.425
    VRay 17.5.293_6c36393_5752
    Last edited by Gosho.Genchev; 25-11-2019, 06:30 AM.

  • #2
    Hello blented , unfortunately multiple volumes with same names are still not supported by the VolumeGrid shader. As a workaround you can use vdbcombine with operation set to "Add", this way the output is one volume only. I understand that with more complex simulations this workaround will be hard to manage, but it's the only way I can think of for now. Also in order to reduce vrscene filesize you should cache the output again.
    Attached Files
    Georgy Chakarov | QA
    www.chaosgroup.com
    georgy.chakarov@chaosgroup.com

    Comment


    • #3
      Unfortunately that doesn't work as we need to instance dozens of fires throughout the scene.

      Even loaded in separate geometry nodes VRay still only renders the last-created volume.

      This is a show-stopper for us so we're currently exploring other ways to render the scene :\

      Comment


      • #4
        That should not happen. I'm on my way home and will check asap.
        ​​​​
        gosho.genchev@chaosgroup.com

        Comment


        • #5
          Thanks Gosho I'll keep an eye on the thread and let you know if we find a workaround, exploring sop instancing options etc.

          Comment


          • #6
            Even loaded in separate geometry nodes VRay still only renders the last-created volume.
            This doesn't reproduce for me - I grabbed the individual volumes (Blast SOP with group 0, 1, etc) and brought them to a new Geometry node. Assigned the same volume shader and things worked as expected.

            The problem *might* be related to the Pack SOPs if you've got them in your production scene, too. There is no point packing the volumes - if you have them on disk, we will grab them from there. If not, we need to bake them anyway.

            File here: https://drive.google.com/file/d/1f6A...ew?usp=sharing

            Hope that helps!
            Attached Files
            gosho.genchev@chaosgroup.com

            Comment


            • #7
              Gotcha that seems to be what was causing the issue. We were packing them to instance them but are now trying to use the instance sop instead thanks for the clarification though.

              Comment


              • #8
                Hey, Grant,

                I've mislead you with my last post - turns out it's possible to treat each packed object as if it was a separate Geometry node - this makes it possible to instance the volumes around in a single node.

                However, currently we are baking the volume to the VRScene when a Pack is used which probably won't cut it for you. The devs are working on improving this, too. I'll ping you as soon as this is taken care of.

                Cheers!
                gosho.genchev@chaosgroup.com

                Comment


                • #9
                  Has this been improved btw?

                  Comment

                  Working...
                  X