Mantaflow: OpenVDB glitches due to Adaptive Domain #79711

System Information
Operating system: Windows 10
Graphics card: Nvidia GeForce GTX 650 Ti
Processor: Intel® Core™ i7-3770

Blender Version
Broken: Blender 2.91.0 (b522e834ec)
Worked: never

Short description of error
The Adaptive Domain causes the smoke to shift when imported as a volume object (Import OpenVDB)
VDB_Ad_D-vid-C.mp4

Exact steps to reproduce the error (based on the .blend file)
VDB_Adaptive_Domain.blend

Enable Adaptive Domain.
Bake the smoke simulation.
The file uses relative paths, so it should import the cache automatically after the first step, but if it doesn't, select fluid_data_0001 and load the cached files.
Play the animation.

Added subscriber: @Iago-Diogo-de-Vasconcelos-Mota

#83990 was marked as duplicate of this issue

#80884 was marked as duplicate of this issue

#80382 was marked as duplicate of this issue

Added subscribers: @sebbas, @JacquesLucke

I can confirm that. Not sure how an adaptive domain works in openvdb caches. Maybe @sebbas can give us some insights.

Changed status from 'Needs Triage' to: 'Confirmed'

Added subscriber: @BlendedBrain

Added subscriber: @mano-wii

Added subscriber: @srghvn

Added subscriber: @Gadas

Little update here. I just tested this example file in 2.92 9a7da1242d, and the behavior seems a lot stranger. On the left, you see the imported VDB smoke, which hasn't been scaled or rotated, only translated to the left of the original simulation.

VDB_Ad_D-vid2.mp4

Something else to notice is how the bounds are slightly skewed.

Added subscriber: @CGJ

Added subscriber: @jumaku87

https://youtu.be/TNVuq5-0Zlk yup.. adaptive domain generated openvdb in mantaflow does generate these weird issues - scale, position etc. Something like its missing origin and related scale and position... something very weird.
Only deactivating adaptive domain will leave these glitches out. :/

https://youtu.be/TNVuq5-0Zlk?t=97 this might be better angle view...
And I also tried to applied scaling (ctrl + a -> all transforms, or scale... no affect - blender just says: objects have no data to transform ) - so that didn't work either.. no matter is it accepted/applied or not. same weird bug/glitches happen if openvdb import is generated in mantaflow with adaptvive domain..

And I am using density_noise in this one, but same does happen with basic data density - domain / openvdb version is jumping/vibrating when adaptive domain scales bigger - so it looks like it has no origin (or origin is changing its position) and scale relation is wrong (its changing) when adaptive domain scale get bigger or smaller.

Also border collisions doesn't seem to work with adaptive domain if i remember right.

Added subscriber: @Dxn

I think this is because the center of the object is to one side and it scales in relation to that center

Added subscriber: @Julia-11

Added subscriber: @god1ged

In #79711#1108269, @Dxn wrote:
I think this is because the center of the object is to one side and it scales in relation to that center

So how to solve this ? I've got the same problem

Added subscriber: @finalflasher

In #79711#1110552, @god1ged wrote:

In #79711#1108269, @Dxn wrote:
I think this is because the center of the object is to one side and it scales in relation to that center

So how to solve this ? I've got the same problem

it has to be fixed... since Dalai sar has taken it in account so we can expect quite soon

Added subscriber: @Sparazza

Added subscriber: @zrp

Added subscriber: @kursadk

Is there an eta for this? I got hit by this issue very hard atm myself. So I can totally confirm this on 3.0 nightly blender-3.0.0-alpha+master.118803893e65-windows.amd64-release.

It would be at least great to know if this will be fixed anytime soon since this is a pipeline problem really and there does not seem to exists an easy solution for it.

Added subscriber: @Samu89

I have the same problem with 2.93.0
This post is the only reference to the problem I could find. So unless we are missing something I reckon it's a bug. And a big one imo. The whole vdb workflow is broken, because without adaptive domain, simulating anything is an absolute pain. I'm actually a bit surprised that there's not more people complaining about this all over the internet. That's what makes me think it's a fixable problem in Blender's current state

bug.mp4

bug.blend

In the vdb file, the center of the object is in the corner and not in the center, so when resizing the domain moves that way outside of that, we can notice that the way of scaling does not work well.

thanks for your great work to all developers :)

Added subscriber: @Dawe69

Really waiting for a solution to this so, is it worked on?

Best
/Daniel

This might be a bit of repetition, but I just wanted to make sure if the issue really was with Blender's implementation of Mantaflow and not OpenVDB. I always found it a bit strange how the problem only seemed to manifest when importing the smoke separately through OpenVDB, but not when playing back the simulation itself. But, at this point, I think it's quite clear that the problem is with Blender's Mantaflow smoke simulator.

Here, I did the same thing as with the previous examples, but I also tried recreating the original Blender simulation in Houdini, making sure that I do have a resizing container (basically Adaptive Domain in Houdini), and importing that as a VDB sequence in Blender as well. In the end, the VDB sequence imported from Houdini looks just fine, while the VDB sequence imported from Blender is resizing and shifting terribly.
VDBImportBugPRUpdate.mp4
Also, (not shown here) I imported the Mantaflow VDB sequence into Houdini, and, just like when importing it into Blender, the problem was just the same. (By the way, the original Blender simulation isn't perfect either; I think I can see an example of #91174, but I guess that's besides the point here.) Now, I want to make a correction to something I previously said that was likely misleading: The skewing in the bounds of the imported VDB sequence are either inconsequential, or a problem with Blender's OpenVDB, not Mantaflow. In the video above, you can see that even in the sequence imported from Houdini, the lines around the smoke container aren't fully aligned, the corner angles aren't rectangular. I previously raised this skewing as a concern regarding Mantaflow, but it doesn't seem to be related.

Anyway, the Blender simulation here was done in 3.0. And here's the .blend just in case:

BlenderVDBImportBug.blend

looks like the imported blender adaptive vdb isn't registering and saving loc rot scale data perframe of vdb before getting exported

Mantaflow (fluid simulator) has no active developer at the moment. Moving those bugs as known issues so at least other users can find their issues already reported.

Added subscriber: @Esteban-G-Vega

It is very sad that this is still the same today. It is impossible to take blender seriously as a VFX pipeline without solving basic problems like this :(

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Mantaflow: OpenVDB glitches due to Adaptive Domain #79711