Announcement

Collapse
No announcement yet.

Maya Fluid workflow

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

  • Maya Fluid workflow

    I've been having trouble rendering Maya Fluids using V-Ray and would like share my workflow to see if anyone could shed some light on the problem (no pun intended).

    We use Maya 2016 with V-Ray 3.4
    I simulate my Fluid from frame 1 to 500, everything looks great, and I proceed with creating a fluid cache using the mcx format for each frame with default settings.
    I keep my fluid cache in Maya's project scene folder, not in a network shared location.
    The final fluid resolution is high (500) and each mcx file is about 600mb.

    When I render a test frame anywhere between the 1 to 500 frame with distributed rendering using the V-Ray frame buffer everything looks good.

    When I render any frame sequence, for example 100 to 200, using command line rendering I get the first frame and then blank frames for the rest of the sequence, occasionally a frame with a few rendered buckets in between.

    my command line file reads...
    render -r vray -s 100 -e 200 -cam camera1 -im smoke.cam1 smoke.ma

    The way I fixed this issue is to command line render each frame individually...
    render -r vray -s 100 -e 100 -cam camera1 -im smoke.cam1 smoke.ma
    render -r vray -s 101 -e 101 -cam camera1 -im smoke.cam1 smoke.ma
    render -r vray -s 102 -e 102 -cam camera1 -im smoke.cam1 smoke.ma
    etc,
    (lots of fun setting up a 500 frame sequence that way!)

    I though of putting the cache in a network shared location, but I got the same issue when turning off distributed rendering so I realized that wouldn't solve it.

    What am I missing?

    Should I adopt a different workflow?

  • #2
    have you tried it through backburner? sounds like a bug tho...
    Dmitry Vinnik
    Silhouette Images Inc.
    ShowReel:
    https://www.youtube.com/watch?v=qxSJlvSwAhA
    https://www.linkedin.com/in/dmitry-v...-identity-name

    Comment


    • #3
      We don't use backburner since we render a lot of stills and want every computer contributing to the image. Distributed Rendering works well for us except in this one case of Fluid caches.

      Comment


      • #4
        Right but I saw in your command line that you were rendering -s -e, in that case you can submit your dr stills to backburner with DR enabled it will also work. The difference is it will reload the scene between frames (or at least I believe there used to be an option to reload) then it will most likely work for fluid cache.
        Dmitry Vinnik
        Silhouette Images Inc.
        ShowReel:
        https://www.youtube.com/watch?v=qxSJlvSwAhA
        https://www.linkedin.com/in/dmitry-v...-identity-name

        Comment


        • #5
          That sounds like a good solution for the workflow I have now.

          Thanks

          Comment

          Working...
          X