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 ?
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?
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.
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.
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?
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.