Mantaflow: Noise doesn't follow smoke #81017

Open
opened 2020-09-21 03:43:36 +02:00 by Iago Mota · 9 comments

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

Blender Version
Broken: Blender 2.90
Worked: Blender 2.81

Short description of error
After enabling "Noise", the Wavelet turbulence doesn't follow the smoke. It seems to only mildly adapt to certain movements; but, unlike in 2.81 it doesn't get "dragged" by the velocity of the smoke.
NoiseDifference-C.mp4

Exact steps to reproduce the error
In any smoke simulation (preferably one where smoke is being constantly emitted), enable "Noise" and bake.

2.9 Project file: 2.9 Example.blend

2.81 Project file for comparison: 2.81 Example.blend

**System Information** Operating system: Windows 10 Graphics card: Nvidia GeForce GTX 650 Ti Processor: Intel® Core™ i7-3770 **Blender Version** Broken: Blender 2.90 Worked: Blender 2.81 **Short description of error** After enabling "Noise", the Wavelet turbulence doesn't follow the smoke. It seems to only mildly adapt to certain movements; but, unlike in 2.81 it doesn't get "dragged" by the velocity of the smoke. [NoiseDifference-C.mp4](https://archive.blender.org/developer/F8904658/NoiseDifference-C.mp4) **Exact steps to reproduce the error** In any smoke simulation (preferably one where smoke is being constantly emitted), enable "Noise" and bake. 2.9 Project file: [2.9 Example.blend](https://archive.blender.org/developer/F8904663/2.9_Example.blend) 2.81 Project file for comparison: [2.81 Example.blend](https://archive.blender.org/developer/F8904665/2.81_Example.blend)
Author
Added subscriber: @Iago-Diogo-de-Vasconcelos-Mota

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

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

A small update here. I was experimenting with different resolutions; and it certainly improves in quality as the upres factor is increased, but the noise still fails to follow the movement of the original simulation.

2.90.1Resolutions.mp4

2.90.1 Example.blend

A small update here. I was experimenting with different resolutions; and it certainly improves in quality as the upres factor is increased, but the noise still fails to follow the movement of the original simulation. [2.90.1Resolutions.mp4](https://archive.blender.org/developer/F8961177/2.90.1Resolutions.mp4) [2.90.1 Example.blend](https://archive.blender.org/developer/F8961168/2.90.1_Example.blend)
Member

Added subscribers: @sebbas, @JacquesLucke

Added subscribers: @sebbas, @JacquesLucke
Member

@sebbas is this a bug or just working differently in mantaflow?

@sebbas is this a bug or just working differently in mantaflow?

Investigated a bit and have an update:

TLDR: This is an issue which the old smoke simulation system didn't have since it worked differently.

The adaptive time-stepping is likely the cause of this problem: The current setup only uses it for the base simulation. The wavelet simulation (any resolution) runs at (fixed) 1 simulation step per frame. So, while the base simulation can simulate multiple smaller steps in one frame, the wavelet simulation cannot. Wavelet smoke plumes can therefore take different shapes.

Turning off "Adaptive Time Steps" should make wavelet smoke "follow" the base smoke better. The overall quality of the simulation might be not as good though.

Next step for me is to expand the adaptive time-stepping loop so that noise also makes uses of it. This should fix the issue.

Investigated a bit and have an update: *TLDR: This is an issue which the old smoke simulation system didn't have since it worked differently.* The adaptive time-stepping is likely the cause of this problem: The current setup only uses it for the base simulation. The wavelet simulation (any resolution) runs at (fixed) 1 simulation step per frame. So, while the base simulation can simulate multiple smaller steps in one frame, the wavelet simulation cannot. Wavelet smoke plumes can therefore take different shapes. Turning off "Adaptive Time Steps" should make wavelet smoke "follow" the base smoke better. The overall quality of the simulation might be not as good though. Next step for me is to expand the adaptive time-stepping loop so that noise also makes uses of it. This should fix the issue.
Author

Unfortunately, I'm not noticing a strong difference with Adaptive Time Steps disabled (in 2.91 Beta). I'll explore this with other simulations, though, to see if the results are any different. (upres is at 2 for this one)

2.91ASubstepOffTST.mp4

Unfortunately, I'm not noticing a strong difference with Adaptive Time Steps disabled (in 2.91 Beta). I'll explore this with other simulations, though, to see if the results are any different. (upres is at 2 for this one) [2.91ASubstepOffTST.mp4](https://archive.blender.org/developer/F9608158/2.91ASubstepOffTST.mp4)

Added subscriber: @hal9000

Added subscriber: @hal9000
Author

Alright, a bit of an update here. Mostly, I just think that this illustrates the issue in question a bit better than my previous examples. Looking back at my previous posts, there was quite a lot going on in them, plus in the last ones, the smoke was moving quite fast. And, regarding issues with Noise and fast moving smoke, I feel like I might've been entering #78738 territory, if these are indeed separate problems.

But, anyhow. I think this shows a bit more clearly how the Noise really doesn't seem to want to properly follow the movement of the smoke in Blender 3.0. Though, I understand this is likely a really challenging issue to solve. Even though this footage makes the problem more clear, you can still see the noise being pushed around and morphing here and there. So I don't think it's as simple as the movement of the noise not being affected by the base smoke sim at all.

B3NoiseBugC.mp4

Now, another thing I couldn't help but notice was the apparent difference in quality. While looking more noisy, the 3.0 version seems a bit less detailed? This could likely be a separate issue, or even that, despite both simulations having equal resolution settings (86 for the base divisions, and 2 high-resolution divisions), there is still a difference in total voxel count between the two? I apologize if it's a bit hard to see. I'll do a bit more testing on the issue to know whether this is a valid thing to point out!

Anyway, here's the project file of the 3.0 scene here.
Noise_Movement_Bug_Smokesim.blend

Alright, a bit of an update here. Mostly, I just think that this illustrates the issue in question a bit better than my previous examples. Looking back at my previous posts, there was quite a lot going on in them, plus in the last ones, the smoke was moving quite fast. And, regarding issues with Noise and fast moving smoke, I feel like I might've been entering #78738 territory, if these are indeed separate problems. But, anyhow. I think this shows a bit more clearly how the Noise really doesn't seem to want to properly follow the movement of the smoke in Blender 3.0. Though, I understand this is likely a really challenging issue to solve. Even though this footage makes the problem more clear, you can still see the noise being pushed around and morphing here and there. So I don't think it's as simple as the movement of the noise not being affected by the base smoke sim at all. [B3NoiseBugC.mp4](https://archive.blender.org/developer/F12819408/B3NoiseBugC.mp4) Now, another thing I couldn't help but notice was the apparent difference in quality. While looking more noisy, the 3.0 version seems a bit less detailed? This could likely be a separate issue, or even that, despite both simulations having equal resolution settings (86 for the base divisions, and 2 high-resolution divisions), there is still a difference in total voxel count between the two? I apologize if it's a bit hard to see. I'll do a bit more testing on the issue to know whether this is a valid thing to point out! Anyway, here's the project file of the 3.0 scene here. [Noise_Movement_Bug_Smokesim.blend](https://archive.blender.org/developer/F12819421/Noise_Movement_Bug_Smokesim.blend)
Philipp Oeser removed the
Interest
Nodes & Physics
label 2023-02-10 08:46:31 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#81017
No description provided.