Page MenuHome

Smoke not rendering randomly, video and blend attached
Confirmed, NormalPublicBUG


System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: rBf6cb5f54494e

Short description of error
Smoke renders haphazardly in the viewport. see
Sometimes it's fixed by toggling Adaptive Domain on/off and changing its Add Reosultion value up, e.g. 0, 16, 512, 32, 64, etc.

This is random and not guaranteed to fix it.

Exact steps for others to reproduce the error
Open the attached .blend file, Play (hit Space).
Smoke sometimes renders correctly in the viewport, sometimes it doesn't.

Event Timeline

Richard Antalik (ISS) changed the task status from Needs Triage to Confirmed.Jan 20 2020, 11:48 PM
Richard Antalik (ISS) added a project: Physics.

Currently smoke is not applied to particles, so it is impossible to triage this.

But I will confirm as in "it's very broken"

Bastien Montagne (mont29) changed the task status from Confirmed to Needs Information from User.Mon, Feb 17, 4:23 PM
Bastien Montagne (mont29) edited projects, added Nodes & Physics; removed Physics.

Can someone please reconfirm that issue? in 2.82 we now have a new fluid solver system, so not sure the report is still valid...

Richard Antalik (ISS) changed the task status from Needs Information from User to Confirmed.Mon, Feb 17, 6:05 PM
Richard Antalik (ISS) changed the subtype of this task from "Report" to "Bug".

There are still problems with this file.
After setting particle system as flow source, result was smoky pancake. Can not see anything obviously broken in that file.

I see similar random behaviour. After adding quick smoke to a new default cube it renders find. If I change any parameter about the simulation the smoke stops rendering after baking and I can't figure out the logic to make it work again.

I am using 2.82 release version on a Mac Pro. I also tried with Windows 10 and get the exact same behaviour.