Page MenuHome

Viewport display broken for fire- solid and rendered mode (Cycles & Eevee)
Confirmed, NormalPublicBUG


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 431.86

Blender Version
Broken: version: 2.83 (sub 0), branch: master, commit date: 2020-01-14 20:45, hash: rB1ec08999b6a2
Worked: (optional)

Short description of error
[Fire seems to get 'stuck' in the viewport (as in it does not disappear), it does however behave correctly when F12 rendered.
This happens in 2.83Alpha and 2.82Beta (both downloaded as of today, approx 16:00 Sydney time 15 Jan 2020)]

Exact steps for others to reproduce the error
[Bake the attached and observe.
here's what it looks like-

It works Ok when F12 rendered as seen here-

I couldn't be bothered to render out the clip in Cycles but stills show the error is only in the viewport-

Here's the .blend-

This works properly in the 26November2019 build, here's what that looks like-
[Based on the default startup or an attached .blend file (as simple as possible)]

Event Timeline

Richard Antalik (ISS) changed the task status from Needs Triage to Confirmed.Wed, Jan 15, 1:56 PM
Richard Antalik (ISS) added a project: Physics.
Richard Antalik (ISS) changed the subtype of this task from "Report" to "Bug".

Just FYI: this bug is not consistent- as in it definitely shows in the .blend I uploaded, but not in every sim I make.
And one very important question- is / should Mantaflow be exactly the same iteration in both 2.82Beta and 2.83Alpha? As in should I mainly be using and reporting bugs from 2.82 or 2.83?