Mantaflow: Flame not working correctly when animating a Fuel value. #74078

Closed
opened 2020-02-21 15:12:11 +01:00 by Yuriy · 18 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd7

Short description of error
If an object of type Flow animates the value Fuel, then the flame behaves incorrectly. When the Fuel value reaches zero.
In the first example, the flame immediately disappears. Although, logically, the fuel supply simply stopped and there would be no new flame. Only old fuel will burn out.
01.gif
test_smoke_mantaflow.blend
In the second example, the flame exists for some time, but it behaves incorrectly.
02.gif
2.82.blend

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: `77d23b0bd7` **Short description of error** If an object of type Flow animates the value Fuel, then the flame behaves incorrectly. When the Fuel value reaches zero. In the first example, the flame immediately disappears. Although, logically, the fuel supply simply stopped and there would be no new flame. Only old fuel will burn out. ![01.gif](https://archive.blender.org/developer/F8357501/01.gif) [test_smoke_mantaflow.blend](https://archive.blender.org/developer/F8357843/test_smoke_mantaflow.blend) In the second example, the flame exists for some time, but it behaves incorrectly. ![02.gif](https://archive.blender.org/developer/F8357506/02.gif) [2.82.blend](https://archive.blender.org/developer/F8357512/2.82.blend)
Author

Added subscriber: @YuraKharitonow

Added subscriber: @YuraKharitonow

Added subscriber: @iss

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

@YuraKharitonow Is it possible, that your second file is not, what you intended to upload?

So if I understand you, file test_smoke_mantaflow.blend is working as it should. is that correct?

Also we would appreciate if this could be reproduced in file that is baked in seconds rather than minutes.

@YuraKharitonow Is it possible, that your second file is not, what you intended to upload? So if I understand you, file `test_smoke_mantaflow.blend` is working as it should. is that correct? Also we would appreciate if this could be reproduced in file that is baked in seconds rather than minutes.
Author

In the file test_smoke_mantaflow.blend, the fire does not work correctly.
test_smoke_mantaflow.blend This is a light version in which smoke and flame bake quickly.
When the Fuel value reaches zero, the fire instantly disappears.
File 2.82.blend loaded correct. The result of baking as on a gif animation.

In the file **test_smoke_mantaflow.blend**, the fire does not work correctly. [test_smoke_mantaflow.blend](https://archive.blender.org/developer/F8357843/test_smoke_mantaflow.blend) This is a light version in which smoke and flame bake quickly. When the Fuel value reaches zero, the fire instantly disappears. File 2.82.blend loaded correct. The result of baking as on a gif animation.
Author

Render results. File test_smoke_mantaflow.blend.mantaflow.mp4
It can be seen that the fuel does not burn out. The fire disappears in one frame.
screen01.PNG

screen02.PNG

Render results. File **test_smoke_mantaflow.blend**.[mantaflow.mp4](https://archive.blender.org/developer/F8364810/mantaflow.mp4) It can be seen that the fuel does not burn out. The fire disappears in one frame. ![screen01.PNG](https://archive.blender.org/developer/F8364815/screen01.PNG) ![screen02.PNG](https://archive.blender.org/developer/F8364814/screen02.PNG)
Author

Also, if you pay attention, at the end of the video you can notice how the smoke is shifted jerky. I recorded a video in which you can notice a jerk when I switch between 182 and 183 frames. After frame 183, the jerk is repeated several more times. On the 188 frame smoke artifacts are visible. Perhaps this is the result of the adaptive domain. Shaders are not animated. The camera is not shaking. In the recorded video, you can see the animation curves of the camera. Perhaps this problem should be moved to a separate Task. I have not tried to reproduce the shake with poor quality smoke.jerk0001-4715.mp4
This is the latest version of my file. test_smoke_mantaflow.blend

Also, if you pay attention, at the end of the video you can notice how the smoke is shifted jerky. I recorded a video in which you can notice a jerk when I switch between 182 and 183 frames. After frame 183, the jerk is repeated several more times. On the 188 frame smoke artifacts are visible. Perhaps this is the result of the adaptive domain. Shaders are not animated. The camera is not shaking. In the recorded video, you can see the animation curves of the camera. Perhaps this problem should be moved to a separate Task. I have not tried to reproduce the shake with poor quality smoke.[jerk0001-4715.mp4](https://archive.blender.org/developer/F8366051/jerk0001-4715.mp4) This is the latest version of my file. [test_smoke_mantaflow.blend](https://archive.blender.org/developer/F8366072/test_smoke_mantaflow.blend)

Changed status from 'Needs User Info' to: 'Confirmed'

Changed status from 'Needs User Info' to: 'Confirmed'

Setting Fuel value to 0.001 had desireable effect, so I guess this could be a bug.
I won't comment on second example, perhaps the problem has same roots, but it could be unrelated bug.

Please, always report only one bug so for glitching smoke please make new report.

Setting `Fuel` value to 0.001 had desireable effect, so I guess this could be a bug. I won't comment on second example, perhaps the problem has same roots, but it could be unrelated bug. Please, always report only one bug so for glitching smoke please make new report.
Added subscriber: @Iago-Diogo-de-Vasconcelos-Mota

This bug seems to be behaving a bit differently in 2.90.0 f319eec881 . For one, the fire completely stops moving (but doesn't necessarily disappear) when Fuel is set to 0, while the rest of the smoke progresses at a normal speed.
C-Fuel Anim Bug.mp4
Flame Fuel Anim Bug-01.blend

I ran into another complication. It seems that, if I animate Fuel in a way that the last keyframe has a value of 0 (that is, the animation ends with Fuel at 0), the fire won't be visible at all in the entire animation. The smoke, however, will still be moving up much faster than before, as if the fire was still there.
C-Fuel Anim Bug-2.mp4
Flame Fuel Anim Bug-02.blend

Now, in this instance, the bug can be easily circumvented by animating Fuel to something like 0.00001, instead of 0, but I'm not sure if this bug has other side effects.

This bug seems to be behaving a bit differently in 2.90.0 f319eec88186 . For one, the fire completely stops moving (but doesn't necessarily disappear) when Fuel is set to 0, while the rest of the smoke progresses at a normal speed. [C-Fuel Anim Bug.mp4](https://archive.blender.org/developer/F8694072/C-Fuel_Anim_Bug.mp4) [Flame Fuel Anim Bug-01.blend](https://archive.blender.org/developer/F8694075/Flame_Fuel_Anim_Bug-01.blend) I ran into another complication. It seems that, if I animate Fuel in a way that the last keyframe has a value of 0 (that is, the animation ends with Fuel at 0), the fire won't be visible at all in the entire animation. The smoke, however, will still be moving up much faster than before, as if the fire was still there. [C-Fuel Anim Bug-2.mp4](https://archive.blender.org/developer/F8694079/C-Fuel_Anim_Bug-2.mp4) [Flame Fuel Anim Bug-02.blend](https://archive.blender.org/developer/F8694080/Flame_Fuel_Anim_Bug-02.blend) Now, in this instance, the bug can be easily circumvented by animating Fuel to something like 0.00001, instead of 0, but I'm not sure if this bug has other side effects.

Added subscriber: @sebbas

Added subscriber: @sebbas

Changed status from 'Confirmed' to: 'Needs User Info'

Changed status from 'Confirmed' to: 'Needs User Info'

@YuraKharitonow and @Iago-Diogo-de-Vasconcelos-Mota Can you try out the latest version of master? I committed some fixes that I think have fixed the issue (the issues from the last 2 sample files seem to be resolved). Can you confirm this?

@YuraKharitonow and @Iago-Diogo-de-Vasconcelos-Mota Can you try out the latest version of master? I committed some fixes that I think have fixed the issue (the issues from the last 2 sample files seem to be resolved). Can you confirm this?

@sebbas Alright, I'm not encountering the issue anymore in 2.91.0 deb76548c1. Fuel seems to be animating properly now, at least for me.

@sebbas Alright, I'm not encountering the issue anymore in 2.91.0 deb76548c108. Fuel seems to be animating properly now, at least for me.
Author

Yes, now this bug is not reproducible in version 2.91. But reproduced in version 2.83.4. If the fuel value is animated, then there is no fire at all.
The first GIF animation is the Modular cache.
fire_modular.gif
Second GIF animation - Replay cache
fire_replay.gif

Yes, now this bug is not reproducible in version 2.91. But reproduced in version 2.83.4. If the fuel value is animated, then there is no fire at all. The first GIF animation is the Modular cache. ![fire_modular.gif](https://archive.blender.org/developer/F8751782/fire_modular.gif) Second GIF animation - Replay cache ![fire_replay.gif](https://archive.blender.org/developer/F8751784/fire_replay.gif)

Changed status from 'Needs User Info' to: 'Resolved'

Changed status from 'Needs User Info' to: 'Resolved'
Sebastián Barschkis self-assigned this 2020-08-07 16:23:20 +02:00

Ok good, closing this report then!

@YuraKharitonow 2.83 could not get this fix as 2.90 has diverged too much from it already. That is, I would not have been able to apply this patch 1:1 onto 2.83. It can only be fixed directly in 2.83 - but our LTS rules do not allow such changes.

Ok good, closing this report then! @YuraKharitonow 2.83 could not get this fix as 2.90 has diverged too much from it already. That is, I would not have been able to apply this patch 1:1 onto 2.83. It can only be fixed directly in 2.83 - but our LTS rules do not allow such changes.
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
4 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#74078
No description provided.