Import EmberGen VDB files in Octane for Blender w/ Lino Grandi | NVIDIA Studio Session

Arm yourself with the best method to import embergen VDB files in Octane for Blender with 3D artist Lino Grandi!
Check out Lino's stunning work on Artstation: www.artstation.com/linograndi
NVIDIA GPUs accelerate your work with incredible boosts in performance. Less time staring at pinwheels of death means bigger workloads, more features, and creating your work faster than ever. Welcome to NVIDIA Studio-and your new, more creative, process. RTX Studio laptops and desktops are purpose-built for creators, providing the best performance for video editing, 3D animation, graphic design, and photography.
For more information about NVIDIA Studio, visit: www.nvidia.com/studio
CONNECT WITH US ON SOCIAL
Instagram: / nvidiacreators
Twitter: / nvidiacreators
Facebook: / nvidiacreators

[@ReviewHole]

Volume properties does not exist in the cube's data tab for me.

[@godzoookie]

Shift A>Volume>import VDB, 14:06

[@ReviewHole]

@@godzoookie thanks! I seem to remember getting this to work but i'll remember this for next time.

[@activemotionpictures]

Thank you for showing us the naming $4f$ is a variable naming convention to read the vdb sequence. Thank you so much for sharing this!

[@PrometheusPhamarus]

Thanks Lino for the showcase, Embergen is on my eyes and in my mind.

[@JohnFranklin1982]

Thank you very much! Exactly what I needed!

[@goldstick3D]

Hah, I skipped forward a lot and then thought how many interesting custom nodes you've got there.. But then realized that it's octane :D

[@marconwps]

Great Lino =) !!!

[@WillFalcon]

EmberGen render is very fast comparing to octane and/or cycles, so It is a good isea to use it to render animation and import blender/C4D camera into the EmberGen

[@cresshead]

nice vid great info

[@MrPK]

thanks

[@jcnwillemsen]

correction: there seems to be a major discrepancy between viewport and render density. Make sure you check the 'octane camera imager' on your active scene camera, this will show render output in viewport.
----------------
Finally got it to work:
For those that struggle with smoke/blackbody relation:
- select the same blender volume grid attribute as emitter used in the octane volume setting, so Temp Temp, or flame flame ect
- I use a very low density, like 0.001, higher values cause problems with the blackbody shading.
- adding value to texture in blackbody emission can be usefull for creating more light radiation from the object.

[@nehvis8109]

For some reason linking the black body emission node does absolutely nothing for me. Other people seem to have the same problem, so I guess it has to do with the newer version. Any ideas?

[@glamlin7432]

2.83 no octane vdb?

[@NonStopMixaTron]

I'm curious about this too

[@zander8713]

@@NonStopMixaTron @Glam lin I believe you have to use the Import OpenVDB in-Blender method (When you hit shift-A)

[@NonStopMixaTron]

@@zander8713 Yes you are correct. I figured this out a couple days after making this post and never came back to update.

[@zander8713]

@@NonStopMixaTron Yeah I figured. I made this mainly for others browsing the comments section :)

[@haronbahamuthat407]

@@zander8713 thanks! at first i did that, but denoiser didn't work on the edges so i thought it must have to do with improper octane vdb loading..? but it's not that, they just made it normal in blenderoctane to import vdb as usual.

[@lionsden1946]

Is there an update for this that works in the latest version of Blender?

[@Smuffy]

Cant get the fire to come through please help!

[@godzoookie]

When I duplicate (Shift D) VDB and change settings for frame start etc. all copies change in Blender 2.93.2

[@godzoookie]

When will I learn to watch whole video before commenting?