Page 1 of 1
Issue rendering vdb
Posted: Wed Nov 01, 2023 11:40 am
by aperte
Hi, I am having a hard time figuring out how to render vdb in octane blender.
I am doing this tutorial step by step :
https://www.youtube.com/watch?v=jq1mYH59UCM
I export some vdb flames from embergen, import, shade it etc...
The problems are :
1- I am importing a sequence file but octane doesn't seem to see it as such, while on the classic/not shaded viewport, the vdb sequence plays correctly. I can see only the vdb frame that was there when i switch to the octane viewport, and it stays still when i scrub through the timeline, while on the not shaded viewport the animation plays fine.
2- When I render, the flames doesnt show up in the render, while they are there in the octane viewport. Or they are shaded very differently to the point I can barely see them, I am not exactly sure.
Any help or advice would be great !

Re: Issue rendering vdb
Posted: Mon Nov 06, 2023 8:56 am
by linograndiotoy
Can you please share a VDB file which doesn't work for you?
Also, please always specify the version you're using:
viewtopic.php?f=32&t=82311
Re: Issue rendering vdb
Posted: Wed Nov 15, 2023 5:26 pm
by aperte
Hi, Thank you for your reply,
I am using Blender_Octane_Edition_2023.1_28.5_stable for windows
Here is a few frames of the vdb file that doesnt work for me
https://drive.google.com/drive/u/0/fold ... uW8EsOcITd
I tried on two computers and different builds and the problem remains the same.
I read from a c4d user who had a similar issue there was an "update volumes" somwhere but couldnt find it in blender...
Also, I have some vdb clouds in the scene wich makes the renders a lot slower, what can be a good way to optimize the volumes rendering without losing too much quality?
Re: Issue rendering vdb
Posted: Mon Nov 20, 2023 9:28 am
by linograndiotoy
Hi!
I've downloaded one of the VDB files and it simply doesn't show up in Blender, so this doesn't seems to be an Octane issue but more a Blender one.
How did you generate the VDBs?
Re: Issue rendering vdb
Posted: Mon Nov 20, 2023 1:11 pm
by aperte
Hello, thank you for looking into this,
I generated them with embergen, and at first they didn't show up for me either until I selected a different grid (flames) in the data properties tab and applied a shader, scaling them up might also help.
I might have generated the vdb with some wrong settings \ attributes since I am quite a newbie, but they show up just fine in cycles and play the sequence as they should.
I am 99% sure the bug is "octane related", I suspect the some settings of my blender octane are off or broken because I just tried in a new project file with a jangaFX free vdb and the issue is the same.
Maybe some setting isn't activated or a link got broken sowhere, I tried to re-install octane for blender but the issue remains.
I am a bit desperate my project is due in 10 days and relies heavily on vdbs... I am in the process of re shading everything in cycles but I really wish I didn't had to, I really liked the look I had in Octane and I feel like my issue has a simple fix but I can't seem to find it...
I really appreciate the time you took to look into it, thanks a lot, let me know if you think about anything I could try to fix it.
Have a good day !
Re: Issue rendering vdb
Posted: Sat Nov 25, 2023 10:50 am
by linograndiotoy
I've tried your examples in Cycles as well, with no success.
Could you please send me a Cycles scene and a VDB which is working for you?
Re: Issue rendering vdb
Posted: Sat Nov 25, 2023 4:30 pm
by aperte
Hi, I added two blend files, one from octane and one from cycles showing the issue over 7 frames
https://drive.google.com/drive/u/0/fold ... uW8EsOcITd
I found a quick fix by adding a volume displace modifier, the animation now works and renders in octane but it isn't optimal as i loose the octane properties panel in the volume settings.
Re: Issue rendering vdb
Posted: Fri Dec 01, 2023 10:24 am
by linograndiotoy
So, it works here, but we definitely need to fix the frame update.
Thanks!
Re: Issue rendering vdb
Posted: Mon Dec 11, 2023 11:44 am
by linograndiotoy
Which is now fixed.