Page 1 of 1

VDB problem, plugin vs standalone

Posted: Mon Jun 18, 2018 11:07 pm
by sjogren
Hi. I have a problem with VDB in the Modo plugin?
There is a difference when this VDB-fire dissolves if you render it with the plugin or with the standalone, I dont know if Im doing something wrong or what it could be? I wanted to use "flame" as the VDB grid mapping, as it is called in Octane!
The image shows frame 15, 16 and 17 in both the plug in and standalone, and the Modo renderer is not shown but similar to the standalone!
Image

/Niklas

Re: VDB problem, plugin vs standalone

Posted: Tue Jun 19, 2018 2:15 pm
by face_off
Was there supposed to be an image in your post?

Paul

Re: VDB problem, plugin vs standalone

Posted: Tue Jun 19, 2018 9:53 pm
by sjogren
Hi and yes it was supposed to be an image there! I added a new picture, unfortunately it was pretty low resolution but I hope it's visible?
The main problem is that the fire/smoke should almost be dissolved as it renders in Octane standalone, In the plugin the smoke is thick, blobby and appears to be cut off! Is there a difference in how the vdb-file is read?
/Niklas

Re: VDB problem, plugin vs standalone

Posted: Sat Jun 30, 2018 4:00 am
by face_off
I can't see any image. You probably need to increase the density. Have you watched https://www.youtube.com/watch?v=0pTMl5G5sJU?. IMO the best way to render VDB's in the plugin is to load the VDB file into an ORBX file and assign that as a Proxy mesh.

Paul

Re: VDB problem, plugin vs standalone

Posted: Mon Jul 02, 2018 11:19 pm
by sjogren
face_off wrote: IMO the best way to render VDB's in the plugin is to load the VDB file into an ORBX file and assign that as a Proxy mesh.
Thank you, must have missed or forgotten this, It works really well!
/Niklas