Wow that looks so good dude! Holy smokes 
4 Likes
Wow, looks really nice. I am glad you are back at it !!!
I saw you asked Pablo how to join development on Blender Today ! I hope that works out somehow !!!
3 Likes
And an example of a simple explosion. Simulation and rendering made internal and for a better look some additional image editing has been made in a proper image editor.
28 Likes
those looks fantastic !
2 Likes
Looks awesome! Is this the place to follow your progress on this?
1 Like
Wow, that is a huge improvement over your previous tests! Would be great to see it in motion.
1 Like
Thanks. Yes, I’ll make updates here about some more significant changes 
5 Likes
It’s coming soon. But I need to make a GUI first so the scene creation would be a bit easier than manually placing everything in a text file, launching by terminal and hoping it turns out well
7 Likes
Hey, so I just made some modifications for making it look nice in motion both in code and in the scene. So there it is 
41 Likes
The new modifications are definitely worth for the time you have taken I hope you achieve realtime results soon.
2 Likes
This looks great! I can’t wait to see how it turns out!
5 Likes
漂亮！非常期待。
Beautiful!
Very much looking forward to it.
Blender devs we want this, thanks
OpenVDB exporter is almost ready (It works but some frames have some transform glitches)(not sure yet if that’s on my or blender side but I’m working on it).
The simulation below has been simulated and exported in 512 grid resolution in matters of ~0.45sec/frame (simulation+exporting time).
Shading and rendering made in blender 3.1 beta (I should update but whatever).
Final color grading and motion blur added in post production
23 Likes
The bug was in Blender. In summary you have to close blender project that uses exported vdbs during the simulation even if you are on the frame that does not use it (so it should be freed from the memory but it’s not?) and after reopening bleder everything works correctly (for now at least)
7 Likes
I’m just trying to render an explosion with the resolution of almost 900^3 for 150 frames. The simulation part was about 1.5sec/frame, exporting around 4sec/frame, everything no problem, no crashes…
…and rendering in blender (3.1.1 this time) is like the third hour of constant crashes (sometimes few crashes per frame). Three times it restarted my whole computer and in total I have about 65 frames ready. So I’m affraid I would have to resimulate the whole scene in lower resolution in order to be able to actually render this in Cycles.
Sooo when thinking about blender implementation the stability and speed of the blender as a whole will be definitely important.
4 Likes
That’s actually bonkers. I’ve also tried rendering OpenVDB from EmberGen previously and can confirm that Blender is excruciatingly slow at volumetrics and constantly runs out of memory while rendering them. But since “running out of memory” isn’t considered a valid bug report, we don’t get any improvements regarding that… I guess the only option is to use Eevee with 4px resolution max and a really close volumentrics distance.
1 Like
After next 3 crashes, tears and an hour of rendering, the 512^3 simulation is ready
22 Likes
Yeah, the problem is that it is “running out of memory” when looking at the nvidia-smi it does not aaand I have like 24GB of VRAM and 128GB of RAM so it should run smoothly. So it is not really the hardware problem but either a bug or some weird handling of data.
edit* Considering that on 18GB I’m simulating the 900^3 domain
2 Likes
This looks awesome!
Did you consider to take part in this years GSOC ?
1 Like