So far the volume grid works basicly good. But if you want to render an animation from a written vdb file it instantly crashes. (single frame and interactive render works fine!)
also the imported vdb files are wrong scaled. ( I use turbulence fd to write the vdb files)
Thank you for reporting, we will look into it.
As a side-note, this might be connected to turbulence fd and how they write vdb files, as for me it didn’t crash when rendering an animation and I used a different source vdb file.
Would it be possible to upload the .vdb file through our private uploader?
Hey jan,
but its not possible to render inside the volume grid box from the vdb files?
It disappears when I go inside, only the shadows of the sim are rendering.
Bug?
Not a bug but a limitation, the camera has to be outside the volume (same with Volume Material, and same with both of those, Volume Grid and Volume Material, in 3ds Max).
I have to join the others:
i think it’s a real bummer that you always have to resort to another renderer for volumetric animations, because you simply can’t render “fly-throughs” with corona. honestly, i also thought that this problem was being worked on. too bad.
Yes I’m basicly so happy with corona, but have to change for an animation completely to octane. Thats bad.
And the devs think there is no need, I was working since the beginning of coronarenderer with it…and now I think about to change.
maybe there are others they need the function here to change the mind of the devs?
IME, development thrives on: “Build it and they will come.” Same philosophy got Corona started and on its feet
Also, technology is already implemented but is missing the last ~10%… looking from economic POV, there are more important things to do first and good devs are scarce (S-curve). So “shit ain’t worth it” for another couple of years…
“Now, what else is there?”
This kind of clouds. Ancient, simple, cheap and fast.