Announcement

Collapse
No announcement yet.

VrayMetaball + VrayDistance map: very slow

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

  • VrayMetaball + VrayDistance map: very slow

    Why VrayMetaball with VrayDistance map as field texture is so slow?
    Below simple rendering which took 20 min.
    When I changed VrayDistance map to noise map rendering took 13 sec.

    Click image for larger version

Name:	VrayDistance.jpg
Views:	1
Size:	95.7 KB
ID:	880924 Click image for larger version

Name:	Noise.jpg
Views:	1
Size:	117.7 KB
ID:	880925

    max 2015 file: VrayMetaball.zip

    __
    sorry for mu English

  • #2
    Interesting setup.
    You are trying to use together a map and a geometry that are being calculated/generated at render time. This will be slower to render and I'm not sure if we can do something to improve it.
    Try to keep the DistanceTex object as simple as possible (low poly) in order to enhance the rendering speed.
    Tashko Zashev | chaos.com
    Chaos Support Representative | contact us

    Comment


    • #3
      It is normal; the distance texture performs quite complex calculations for each of the hundreds of raymarching steps through the metaball volume.

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

      Comment


      • #4
        It's a pity. It would be quite useful in some situations...

        Comment


        • #5
          Have you tried enabling the "Cache" option in the metaball object? It may help to make the tracing faster.

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

          Comment


          • #6
            with cache rendering time took 3 minutes

            Comment


            • #7
              Eh well, still better than 20

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

              Comment


              • #8
                I encountered this problem again.
                The distance texture, even with cache enabled, is veeery slow.
                What about mesh object as input geometry? Is this planned?
                Maybe there is other way to get metaball object clipped to mesh object?

                Comment


                • #9
                  You can distribute particles on the surface of an object, it should work just as well.

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

                  Comment


                  • #10
                    Possibly in the field use a falloff map set to distance blend (object mode), but with some noise?

                    Or see this thread. Might help (might not)

                    http://forums.chaosgroup.com/showthr...ce-not-working
                    Last edited by Joelaff; 25-02-2015, 08:27 PM.

                    Comment

                    Working...
                    X