Announcement

Collapse
No announcement yet.

VDB and interface

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

  • VDB and interface

    I noticed that if you export in .vdb PHX is not so nice with you.

    1- you can't use variables for output of .vdb, annoying but ok.
    2- you don't have backup mode to restore a simulation that was stopped.
    3- you can't store particules in .vdb since it is not meant for that...

    to keep the beloved workflow of PHX, is there a way to convert .aur into .vdb ?

  • #2
    Hello,

    We have all those in mind for a future version, but I can't say how soon we'll get to them.

    For now there is no converter but it's in the to do list.
    Georgi Zhekov
    Phoenix Product Manager
    Chaos

    Comment


    • #3
      Ok, won't make it in time for my current project. Keep up the good work!

      Comment


      • #4
        can I resimulate on .aur with .vdb output?

        Comment


        • #5
          Yes, it should work
          Georgi Zhekov
          Phoenix Product Manager
          Chaos

          Comment


          • #6
            Hey guys, just an update - with tomorrow's nightly you'll be able to resimulate using wavelet turbulence over vdbs from Phoenix.

            Cheers!
            Svetlin Nikolov, Ex Phoenix team lead

            Comment


            • #7
              Hi Svetlin,

              Do I have to update the new nightly build on all the render farm nodes? Base on what I understanding is the latest nightly build will let my workstation Resim vdb cache with wavelet turbulence, nothing involve with the rendering cos the render node only need to read the cache files in order to render. So I don't have to update nightly build on the render farm. Is this correct?

              Thanks,

              Comment


              • #8
                Hey,

                I think you'll have to update the render nodes as well, since there are changes to the loader as well and the renderer needs it.

                Cheers!
                Svetlin Nikolov, Ex Phoenix team lead

                Comment


                • #9
                  Hi Svetlin,

                  I update to Phoenix 3.04.00 and resimulate with vdb still not working for me. I got this error

                  // Error: Phoenix FD: Cannot start the Re-Simulation!

                  Please make sure the simulation was run with the 'Velocity' channel checked under the 'Output' rollout, and that the cache files in the Resimulation Input path exist.

                  Even though my output velocity was checked.

                  Can you please make a sample scene for this? I currently using Phoenix with Maya.

                  Thanks,

                  Comment


                  • #10
                    Hey - the base cache path in the Resim rollout should be the same as the Output path and the Affect option should be set to Grid as vdb resimulation won't affect particles.
                    Georgi Zhekov
                    Phoenix Product Manager
                    Chaos

                    Comment


                    • #11
                      I still got the velocity error.

                      Comment


                      • #12
                        This error means that your caches past this point miss velocity, make sure you have velocity exported for all of the frames you are trying to resimulate.
                        Georgi Zhekov
                        Phoenix Product Manager
                        Chaos

                        Comment


                        • #13
                          Hi Georgi,

                          The same scene with aur cache has no problem to resimulate. I created a very simple scene with sphere and fire preset . When I change it to vdb it keep giving me error. Can you please make an example scene with vdb?

                          Thanks

                          Comment


                          • #14
                            There you go - just make sure to use a latest nightly build.

                            The file is for Maya 2017 - let me know if you need an older one.
                            Attached Files
                            Georgi Zhekov
                            Phoenix Product Manager
                            Chaos

                            Comment


                            • #15
                              Thanks Georgi,

                              I stil get the same error actually. May I ask what version of nightly build you are using? Our TD just update Phoenix 3.04.00 few days ago. I also use Maya 2017 tho.

                              Comment

                              Working...
                              X