Quick Smoke Doesn't Work In Already Established Scene #82280

New Issue

Danny · 2020-10-31T19:59:12+01:00

Danny commented

2020-10-31 19:59:12 +01:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38

Blender Version
Broken: version: 2.83.8, branch: master, commit date: 2020-10-21 08:12, hash: 5949b796f0
Worked: Never.

Short description of error
When adding Quick Smoke to an object in an established scene with many elements, the domain is created, the flow object and domain settings can all be set accordingly, but there is no smoke. The domain remains invisible/empty, even after baking the sim. This is repeatable in multiple established projects. However in a brand new blend file that is completely empty, the exact same setup, works fine.

Exact steps for others to reproduce the error
In my scene, I add a simple object (doesn't matter which one), like a cube for example. With this object selected, I then go to Object > Quick Effects > Quick Smoke. From here, the domain is created, but no initial smoke is present, i.e. no indication that the smoke has been added. Further, after setting up the domain and flow object settings, and baking the sim, there is still no smoke. I can perform this exact process in a brand new blend file and it works fine, however will not work in my scene. When I open existing projects, it works about 50% of the time. No settings anywhere else i.e. render, output, display, etc... changes anything.

Blend file attached.witchs_cottage_scene_006.zip

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38 **Blender Version** Broken: version: 2.83.8, branch: master, commit date: 2020-10-21 08:12, hash: `5949b796f0` Worked: Never. **Short description of error** When adding Quick Smoke to an object in an established scene with many elements, the domain is created, the flow object and domain settings can all be set accordingly, but there is no smoke. The domain remains invisible/empty, even after baking the sim. This is repeatable in multiple established projects. However in a brand new blend file that is completely empty, the exact same setup, works fine. **Exact steps for others to reproduce the error** In my scene, I add a simple object (doesn't matter which one), like a cube for example. With this object selected, I then go to Object > Quick Effects > Quick Smoke. From here, the domain is created, but no initial smoke is present, i.e. no indication that the smoke has been added. Further, after setting up the domain and flow object settings, and baking the sim, there is still no smoke. I can perform this exact process in a brand new blend file and it works fine, however will not work in my scene. When I open existing projects, it works about 50% of the time. No settings anywhere else i.e. render, output, display, etc... changes anything. Blend file attached.[witchs_cottage_scene_006.zip](https://archive.blender.org/developer/F9142147/witchs_cottage_scene_006.zip)

Danny commented

2020-10-31 19:59:12 +01:00

Added subscriber: @DannyBCreative

Robert Guetzkow commented

2020-11-01 15:46:18 +01:00

Added subscriber: @rjg

Robert Guetzkow commented

2020-11-01 15:46:18 +01:00

I can reproduce that in Blender 2.83.8 and 2.90.1 the animation replay doesn't show smoke, but 2.92 (current master) appears to be working fine. The type is correctly set to Replay so it's not the same issue as #73799 which was fixed by e9a3a1afd1. Changing the cache type to All (2.90.1) or Final (2.83.8) and baking works. The smoke is correctly displayed afterwards.

Tested on:
Operating system: Linux-5.4.0-52-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 20.0.8
CPU: i7-4800MQ (Haswell)

I can reproduce that in Blender 2.83.8 and 2.90.1 the animation replay doesn't show smoke, but 2.92 (current master) appears to be working fine. The type is correctly set to *Replay* so it's not the same issue as #73799 which was fixed by e9a3a1afd1. Changing the cache type to *All* (2.90.1) or *Final* (2.83.8) and baking works. The smoke is correctly displayed afterwards. Tested on: Operating system: Linux-5.4.0-52-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 20.0.8 CPU: i7-4800MQ (Haswell)

Robert Guetzkow commented

2020-11-01 15:57:25 +01:00

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

Robert Guetzkow commented

2020-11-01 15:57:25 +01:00

Marking this as confirmed since I can reproduce the replay issue but cannot reproduce the issue after baking.

Jacques Lucke commented

2020-11-04 15:52:33 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2020-11-04 15:52:33 +01:00

It seems to work just as expected for me. Can you make a very short video that shows the issue?

2020-11-04 15-50-38.mp4

It seems to work just as expected for me. Can you make a very short video that shows the issue? [2020-11-04 15-50-38.mp4](https://archive.blender.org/developer/F9196038/2020-11-04_15-50-38.mp4)

Danny commented

2020-11-04 21:50:55 +01:00

Here is a quick video as requested.

QuickSmoke_Fail.mp4

Here is a quick video as requested. [QuickSmoke_Fail.mp4](https://archive.blender.org/developer/F9200101/QuickSmoke_Fail.mp4)

Fernando Alcala commented

2020-11-05 04:28:40 +01:00

Added subscriber: @Fernando-Alcala

Fernando Alcala commented

2020-11-05 04:28:40 +01:00

I had no issues
2020-11-04 19-13-46.mp4

I had no issues [2020-11-04 19-13-46.mp4](https://archive.blender.org/developer/F9202937/2020-11-04_19-13-46.mp4)

Jacques Lucke commented

2020-11-05 11:37:14 +01:00

I wonder why these videos had to be so long. A 10-20s clip should be more than enough I think...
Anyway, can you try what happens when you go to frame 1 after adding quick smoke and then press play?

I wonder why these videos had to be so long. A 10-20s clip should be more than enough I think... Anyway, can you try what happens when you go to frame 1 after adding quick smoke and then press play?

Robert Guetzkow commented

2020-11-05 12:37:08 +01:00

@JacquesLucke Using Jump to Endpoint and then playing works fine in 2.83.8 and 2.90.1, just dragging the play head to the start and then playing doesn't. This does work in 2.92 though.

@JacquesLucke Using *Jump to Endpoint* and then playing works fine in 2.83.8 and 2.90.1, just dragging the play head to the start and then playing doesn't. This does work in 2.92 though.

Jacques Lucke commented

2020-11-05 12:39:38 +01:00

@rjg, can you bisect this?

Danny commented

2020-11-05 16:59:46 +01:00

My video was as long as it was to provide all the steps I was going through, and to show that the exact same steps used in a new blend file worked fine. You can clearly see in my video, it's not working. Also, well before I initiated this bug report, this was discussed publicly with other Blender users, with many expressing they faced the same problem, which is why I was encouraged to initiate this bug report.

Anyway, going to frame 1 after adding quick smoke, then pressing play, does nothing. It simply does not work. Again, I can start a new blend file (as shown in my video) and it works as expected.

My video was as long as it was to provide all the steps I was going through, and to show that the exact same steps used in a new blend file worked fine. You can clearly see in my video, it's not working. Also, well before I initiated this bug report, this was discussed publicly with other Blender users, with many expressing they faced the same problem, which is why I was encouraged to initiate this bug report. Anyway, going to frame 1 after adding quick smoke, then pressing play, does nothing. It simply does not work. Again, I can start a new blend file (as shown in my video) and it works as expected.

Robert Guetzkow commented

2020-11-06 11:36:09 +01:00

I will try to bisect this now. Might take a while since I reproduced this on my old laptop and building takes a bit longer.

Robert Guetzkow commented

2020-11-07 13:46:37 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Robert Guetzkow closed this issue

2020-11-07 13:46:37 +01:00

Robert Guetzkow self-assigned this 2020-11-07 13:46:37 +01:00

Robert Guetzkow commented

2020-11-07 13:46:37 +01:00

Added subscriber: @fclem

Robert Guetzkow commented

2020-11-07 13:46:37 +01:00

The problem is that the compilation of the workbench volume shader was broken for quite a long time (see #80141, bug introduced in da741013a1) for the driver version on the system I could reproduce this with. Through bisecting I can only tell that 2654e9c9c1 is the first version that allows to use Quick Smoke properly again, but that isn't anything new. I suspect that the problem was fixed during one of the refactoring commits by @fclem, but those wouldn't be backported to 2.83 anyway.

For this reason I believe this issue does not require further investigation. It is fixed in 2.91 and newer versions of Blender, which is why I consider this resolved.

The problem is that the compilation of the workbench volume shader was broken for quite a long time (see #80141, bug introduced in da741013a1) for the driver version on the system I could reproduce this with. Through bisecting I can only tell that 2654e9c9c1 is the first version that allows to use Quick Smoke properly again, but that isn't anything new. I suspect that the problem was fixed during one of the refactoring commits by @fclem, but those wouldn't be backported to 2.83 anyway. For this reason I believe this issue does not require further investigation. It is fixed in 2.91 and newer versions of Blender, which is why I consider this resolved.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Quick Smoke Doesn't Work In Already Established Scene #82280