Smoke is not rendering in Blender 2.8 #59838

Closed
opened 2018-12-25 06:51:42 +01:00 by Escape Freedom · 78 comments

System Information
Operating system: OSX 10.13.1
Graphics card: Dual NVIDIA Quadro 4000

Blender Version
Broken: All 2.80 version till date.
(example: 2.79b release)
(example: 2.80, edbf15d3c0, blender2.8, 2018-11-28, as found on the splash screen)
Worked: (optional) 2.79b release

Short description of error

I can see smoke simulation (Easy smoke or Custom Smoke) in viewport but can't render it, scene is rendering without smoke.

Exact steps for others to reproduce the error

  • Start Blender 2.8 Beta ( Any version of December ) > default scene.
  • Select default cube
  • Then Object>Quick Effect>Quick Smoke (Alternatively you can create your own smoke)
  • Playback the scene in viewport, you can see smoke coming out of the cube.
  • Render the frame or whole animation with Eevee or Cycles, other objects are there but no smoke. Tried CPU render, GPU render and there is no smoke.

Based on the default startup or an attached .blend file (as simple as possible).

**System Information** Operating system: OSX 10.13.1 Graphics card: Dual NVIDIA Quadro 4000 **Blender Version** Broken: All 2.80 version till date. (example: 2.79b release) (example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen) Worked: (optional) 2.79b release **Short description of error** I can see smoke simulation (Easy smoke or Custom Smoke) in viewport but can't render it, scene is rendering without smoke. **Exact steps for others to reproduce the error** - Start Blender 2.8 Beta ( Any version of December ) > default scene. - Select default cube - Then Object>Quick Effect>Quick Smoke (Alternatively you can create your own smoke) - Playback the scene in viewport, you can see smoke coming out of the cube. - Render the frame or whole animation with Eevee or Cycles, other objects are there but no smoke. Tried CPU render, GPU render and there is no smoke. Based on the default startup or an attached .blend file (as simple as possible).
Author

Added subscriber: @escape_freedom13

Added subscriber: @escape_freedom13

Added subscriber: @crantisz

Added subscriber: @crantisz

I don't think that it is bug. You just need to enable volumetric in render tab:

Снимок экрана от 2018-12-25 09-45-40.png

And for final render you need to save file first, because blender needs place to save baking data (this for cycles too).

Correct me if I'm wrong, I will mark it as invalid

I don't think that it is bug. You just need to enable volumetric in render tab: ![Снимок экрана от 2018-12-25 09-45-40.png](https://archive.blender.org/developer/F6063504/Снимок_экрана_от_2018-12-25_09-45-40.png) And for final render you need to save file first, because blender needs place to save baking data (this for cycles too). Correct me if I'm wrong, I will mark it as invalid

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Michael Soluyanov self-assigned this 2018-12-25 07:47:36 +01:00
Author

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'
Author

Firstly, many many thanks for the reply.

I thought that it may be a OSX build problem, so I tried current Linux build blender-2.80-6d89337257b6-linux-glibc224-x86_64 with same result even after using your suggestions. Saved the project and Turned volumetrix on in Eevee (I think volume is on by default in cycles, atleast there are no check box for it).

This is my Eevee viewport (You also can see volumetric settings at right of the screen)
Viewport_2018-12-25_12-25-33.png

This is my Eevee render result, can see whole domain but not the smoke
Eevee_2018-12-25_12-26-32.png

This is my Cycles Viewport (You also can see volume settings at right of the screen)
Viewport_2018-12-25_12-26-32.png

This is my Cycles render result, can see the default cube but not the smoke.
Cycles_2018-12-25_12-26-32.png

Workflow on Cycles

  • Open default scene
  • Saved project
  • Changed Render Engine to cycles
  • Saved project
  • Created Quick Smoke
  • Saved project
  • Played back whole animation in viewport
  • Saved project
  • Rendered the project.

This is my 2.79b render (Just rendered with same procedure)
Blender 2.79b Render.png

There are others in the forum who are facing the same problems. Some says that it happens sometimes. Random switching between Eevee and Cycles sometimes fixed this for some people.

Thanks again with thumbs up.

Firstly, many many thanks for the reply. I thought that it may be a OSX build problem, so I tried current Linux build blender-2.80-6d89337257b6-linux-glibc224-x86_64 with same result even after using your suggestions. Saved the project and Turned volumetrix on in Eevee (I think volume is on by default in cycles, atleast there are no check box for it). This is my Eevee viewport (You also can see volumetric settings at right of the screen) ![Viewport_2018-12-25_12-25-33.png](https://archive.blender.org/developer/F6063677/Viewport_2018-12-25_12-25-33.png) This is my Eevee render result, can see whole domain but not the smoke ![Eevee_2018-12-25_12-26-32.png](https://archive.blender.org/developer/F6063699/Eevee_2018-12-25_12-26-32.png) This is my Cycles Viewport (You also can see volume settings at right of the screen) ![Viewport_2018-12-25_12-26-32.png](https://archive.blender.org/developer/F6063709/Viewport_2018-12-25_12-26-32.png) This is my Cycles render result, can see the default cube but not the smoke. ![Cycles_2018-12-25_12-26-32.png](https://archive.blender.org/developer/F6063750/Cycles_2018-12-25_12-26-32.png) Workflow on Cycles - Open default scene - Saved project - Changed Render Engine to cycles - Saved project - Created Quick Smoke - Saved project - Played back whole animation in viewport - Saved project - Rendered the project. This is my 2.79b render (Just rendered with same procedure) ![Blender 2.79b Render.png](https://archive.blender.org/developer/F6063813/Blender_2.79b_Render.png) There are others in the forum who are facing the same problems. Some says that it happens sometimes. Random switching between Eevee and Cycles sometimes fixed this for some people. Thanks again with thumbs up.
Author

Please read my previous comment.

I've done a new project step by step following this video tutorial

But no smoke/fire there. Always there is smoke and fire in solid view viewports but not in render view or render. But many people find it helpful. But I've tried this on two completely different setup, different built and different platform, but unfortunately with same result. Maybe developers are missing this because it's happening in some machines.

System 1

OSX 10.13.1
GPU Dual NVIDIA Quadro 4000 (Without SLI)
Blender 2.80 Beta 22nd Dec Built

System 2

Ubuntu Studio 18.04
GPU ATI Radeon HD 5450
blender-2.80-6d89337257b6-linux-glibc224-x86_64

Please read my previous comment. I've done a new project step by step following this video tutorial [[https://www.youtube.com/watch?v=_2m_xkSZrvc]] But no smoke/fire there. Always there is smoke and fire in solid view viewports but not in render view or render. But many people find it helpful. But I've tried this on two completely different setup, different built and different platform, but unfortunately with same result. Maybe developers are missing this because it's happening in some machines. System 1 OSX 10.13.1 GPU Dual NVIDIA Quadro 4000 (Without SLI) Blender 2.80 Beta 22nd Dec Built System 2 Ubuntu Studio 18.04 GPU ATI Radeon HD 5450 blender-2.80-6d89337257b6-linux-glibc224-x86_64

Added subscriber: @macintosh_robert

Added subscriber: @macintosh_robert

I am on OSX mojave 10.14 and have the same issue. It seems voumetrics only work for the bounding box of an object. If I use a procedural texture to drive

the density or color of an object the volumetric of the bounding box will just disappear. [[ https://blenderartists.org/t/volumetric-in-eevee-doesnt-work/1134833 | Here it was posted in blender artist with more details.

I am on OSX mojave 10.14 and have the same issue. It seems voumetrics only work for the bounding box of an object. If I use a procedural texture to drive the density or color of an object the volumetric of the bounding box will just disappear. [[ https://blenderartists.org/t/volumetric-in-eevee-doesnt-work/1134833 | Here it was posted in blender artist with more details.

To Escape freedom:
I just attempted what you tried and I noticed if I use the viewport render ( top left in viewport select view and select viewport render) it will work but if I use the Render image on the render tab on top header, it will not show up. Might be a workaround for now. Maybe something to do with the compositor or something?

To Escape freedom: I just attempted what you tried and I noticed if I use the viewport render ( top left in viewport select view and select viewport render) it will work but if I use the Render image on the render tab on top header, it will not show up. Might be a workaround for now. Maybe something to do with the compositor or something?

Closed as duplicate of #58793

Closed as duplicate of #58793

Added subscriber: @ZedDB

Added subscriber: @ZedDB

I think the root case for this not working is the same as in #58793.
So if this still is an issue after that one has been solved, feel free to reopen this.

I think the root case for this not working is the same as in #58793. So if this still is an issue after that one has been solved, feel free to reopen this.

Added subscriber: @veggiet

Added subscriber: @veggiet

I have experienced a similar issue. Using blender-2.80-1c7695b8483d-windows64, when I render smoke in Eevee I get nothing. When I render in Cycles I see the smoke, when I render in "Workbench" mode, I also see smoke. In the viewport I can see it all correctly.

Windows 10 Pro, Version 1803, OS build 17134.523
NVIDIA GeForce GTX 960
blender-2.80-1c7695b8483d-windows64

I have experienced a similar issue. Using blender-2.80-1c7695b8483d-windows64, when I render smoke in Eevee I get nothing. When I render in Cycles I see the smoke, when I render in "Workbench" mode, I also see smoke. In the viewport I can see it all correctly. Windows 10 Pro, Version 1803, OS build 17134.523 NVIDIA GeForce GTX 960 blender-2.80-1c7695b8483d-windows64

Added subscriber: @Carlosan

Added subscriber: @Carlosan

Added subscriber: @rimpotche

Added subscriber: @rimpotche

Windows 7 Blender 2.80 Hash ad707115d5
It seems that it's impossible to bake for Cycles, always get reply "No active image found...".
But the baking for Workbench works, so do the baking for Workbench first then it works in Cycles.

Windows 7 Blender 2.80 Hash ad707115d5bc It seems that it's impossible to bake for Cycles, always get reply "No active image found...". But the baking for Workbench works, so do the baking for Workbench first then it works in Cycles.

Added subscriber: @Ethanicus

Added subscriber: @Ethanicus

Added subscriber: @MarcLogic

Added subscriber: @MarcLogic

I have this same issue with smoke in 2.8 beta on Linux. Simply can't get the smoke effect to render with cycles ( other than the viewport preview render).

I have this same issue with smoke in 2.8 beta on Linux. Simply can't get the smoke effect to render with cycles ( other than the viewport preview render).

Added subscriber: @New3000

Added subscriber: @New3000

This comment was removed by @New3000

*This comment was removed by @New3000*

Added subscriber: @theahuramazda

Added subscriber: @theahuramazda

I have the same issue and to get it to work in a full render in Cycles, I selected the Domain object and clicked on "Current Cache to Bake" in the Cache section.

I'm using blender-2.80-0ba143a1d675-win64 on Windows 10

I have the same issue and to get it to work in a full render in Cycles, I selected the Domain object and clicked on "Current Cache to Bake" in the Cache section. I'm using blender-2.80-0ba143a1d675-win64 on Windows 10

Added subscriber: @tupini07

Added subscriber: @tupini07

Added subscriber: @coral

Added subscriber: @coral

I didn't see a bug in Smoke simulation. I created a little tutorial. Watch this video and try following the same steps.
https://youtu.be/BXLWiASSPmU

I didn't see a bug in Smoke simulation. I created a little tutorial. Watch this video and try following the same steps. https://youtu.be/BXLWiASSPmU

Added subscriber: @neffson-2

Added subscriber: @neffson-2

Found the solution to your problem.
You have to make sure your material is set up the right way.
For some reason blender didn't do that for me so I had to do it manually.

Hope this helps!

Screen Shot 2019-05-06 at 21.36.16.png

Found the solution to your problem. You have to make sure your material is set up the right way. For some reason blender didn't do that for me so I had to do it manually. Hope this helps! ![Screen Shot 2019-05-06 at 21.36.16.png](https://archive.blender.org/developer/F7010638/Screen_Shot_2019-05-06_at_21.36.16.png)

Added subscriber: @BigfootLives

Added subscriber: @BigfootLives

In #59838#672265, @neffson-2 wrote:
Found the solution to your problem.
You have to make sure your material is set up the right way.
For some reason blender didn't do that for me so I had to do it manually.

Hope this helps!

Screen Shot 2019-05-06 at 21.36.16.png

I tried this exact setup and smoke is still invisible in Eevee. Seems like the issue is still present.

> In #59838#672265, @neffson-2 wrote: > Found the solution to your problem. > You have to make sure your material is set up the right way. > For some reason blender didn't do that for me so I had to do it manually. > > Hope this helps! > > ![Screen Shot 2019-05-06 at 21.36.16.png](https://archive.blender.org/developer/F7010638/Screen_Shot_2019-05-06_at_21.36.16.png) I tried this exact setup and smoke is still invisible in Eevee. Seems like the issue is still present.

Added subscriber: @NinovanHooff

Added subscriber: @NinovanHooff

In #59838#674273, @BigfootLives wrote:

In #59838#672265, @neffson-2 wrote:
Found the solution to your problem.
You have to make sure your material is set up the right way.
For some reason blender didn't do that for me so I had to do it manually.

Hope this helps!

Screen Shot 2019-05-06 at 21.36.16.png

I tried this exact setup and smoke is still invisible in Eevee. Seems like the issue is still present.

This in fact worked for me in the most current 2.80 beta build from the Blender PPA
On ubuntu 18.10 64 bit. Both viewport and render show smoke in eevee when volumetric is on

> In #59838#674273, @BigfootLives wrote: >> In #59838#672265, @neffson-2 wrote: >> Found the solution to your problem. >> You have to make sure your material is set up the right way. >> For some reason blender didn't do that for me so I had to do it manually. >> >> Hope this helps! >> >> ![Screen Shot 2019-05-06 at 21.36.16.png](https://archive.blender.org/developer/F7010638/Screen_Shot_2019-05-06_at_21.36.16.png) > > > I tried this exact setup and smoke is still invisible in Eevee. Seems like the issue is still present. This in fact worked for me in the most current 2.80 beta build from the [Blender PPA ](https://launchpad.net/~thomas-schiex/+archive/ubuntu/blender) On ubuntu 18.10 64 bit. Both viewport and render show smoke in eevee when volumetric is on

Added subscriber: @SCOTTROSS-1

Added subscriber: @SCOTTROSS-1

Under volumetric, try turning the "end" up to a higher number like 5000. Film needs to be set to sky not transparent. These are both under the render tab.

Under volumetric, try turning the "end" up to a higher number like 5000. Film needs to be set to sky not transparent. These are both under the render tab.

Added subscriber: @buttonbasherbirdy

Added subscriber: @buttonbasherbirdy

Sup’ guys dont know if this was mentioned yet but I had been having the same problems and i had also activated ‘volumetric lighting’, spelt ‘density’ correctly etc etc. But the one thing that actually solved it for me was going into the ‘Volumetric’ setting and turning up the ‘End Value’ until the fire looked suitable for the shot. Hopes this helps for the future!

Sup’ guys dont know if this was mentioned yet but I had been having the same problems and i had also activated ‘volumetric lighting’, spelt ‘density’ correctly etc etc. But the one thing that actually solved it for me was going into the ‘Volumetric’ setting and turning up the ‘End Value’ until the fire looked suitable for the shot. Hopes this helps for the future!

Added subscriber: @Drowningman_jr

Added subscriber: @Drowningman_jr

Well, it seems I am the only one with this problem. I can't turn on volumetrics, like the button for it is nonexistent, please help.
image.png

Well, it seems I am the only one with this problem. I can't turn on volumetrics, like the button for it is nonexistent, please help. ![image.png](https://archive.blender.org/developer/F7712750/image.png)

Added subscriber: @juang3d

Added subscriber: @juang3d

Volumetrics don't have an On/Off button since some versions ago, they are automatically enabled as soon as you have a volumetric shader in the scene.

Volumetrics don't have an On/Off button since some versions ago, they are automatically enabled as soon as you have a volumetric shader in the scene.

Added subscriber: @sseral

Added subscriber: @sseral

Yes mate. Your solution is the ony one that works. Thank you.

Yes mate. Your solution is the ony one that works. Thank you.

Added subscriber: @AkshithShetty

Added subscriber: @AkshithShetty

Yeah one thing to say, I think cycles does not render smoke in my case. I added emission texture and made it look like fire.But when I tried to render it as smoke it didn't render. But as fire it actually did.

Yeah one thing to say, I think cycles does not render smoke in my case. I added emission texture and made it look like fire.But when I tried to render it as smoke it didn't render. But as fire it actually did.

Added subscriber: @MMMM

Added subscriber: @MMMM

Funny thing, I had this working... accidentally deleted my box and couldn't get it to work again.

You probably won't believe what I did to get it to work:
Select the Smoke Domain box, while in object mode, CTRL-A, all transforms. Renders in Cycles now. (still doesn't in Eevee, but I'm not using Eevee, so I'm not gonna mess with it.)

Note:
Blender 2.81
Using default "quick smoke" and only altering the prepopulated density setting to 250 to create "steam".
Not density under the object's smoke property, NOR the density under the smoke domain's smoke property, the density under the smoke domain's material settings is the one I changed

Donut11.png

Funny thing, I had this working... accidentally deleted my box and couldn't get it to work again. You probably won't believe what I did to get it to work: Select the Smoke Domain box, while in object mode, CTRL-A, all transforms. Renders in Cycles now. (still doesn't in Eevee, but I'm not using Eevee, so I'm not gonna mess with it.) Note: Blender 2.81 Using default "quick smoke" and only altering the prepopulated density setting to 250 to create "steam". **Not density under the object's smoke property, NOR the density under the smoke domain's smoke property, the density under the smoke domain's material settings is the one I changed** ![Donut11.png](https://archive.blender.org/developer/F8184490/Donut11.png)

Added subscriber: @JamesScott

Added subscriber: @JamesScott

Save the file, then in Smoke Domain settings "Bake" under Cache.

Save the file, then in Smoke Domain settings "Bake" under Cache.

Added subscriber: @wender1

Added subscriber: @wender1

In #59838#637076, @theahuramazda wrote:
I have the same issue and to get it to work in a full render in Cycles, I selected the Domain object and clicked on "Current Cache to Bake" in the Cache section.

I'm using blender-2.80-0ba143a1d675-win64 on Windows 10

I was having this smoke not rendering issue too, so i tryed the solution above and it works like a charm! Thanks @theahuramazda.

> In #59838#637076, @theahuramazda wrote: > I have the same issue and to get it to work in a full render in Cycles, I selected the Domain object and clicked on "Current Cache to Bake" in the Cache section. > > I'm using blender-2.80-0ba143a1d675-win64 on Windows 10 I was having this smoke not rendering issue too, so i tryed the solution above and it works like a charm! Thanks @theahuramazda.

Added subscriber: @Singularity42

Added subscriber: @Singularity42

I am having the same problem in 2.81.

I found baking the physics seemed to fix it.

I am too new to blender to know whether this is a bug or not, but it didn't seem intuitive to me.

I am having the same problem in 2.81. I found baking the physics seemed to fix it. I am too new to blender to know whether this is a bug or not, but it didn't seem intuitive to me.

Added subscriber: @itplainedge

Added subscriber: @itplainedge

Win 10/64bit running Blender 8.1. Same problem following Andrew Price's tutorial (Blender 8.1 tutorial ) last minute of video.

Basically if anyone was having the problem like me, following the video you create a quick smoke and after that is created, the object that is selected is the domain. I went into the domain object and changed it to flow and made it smoke/fire and it didn't work. After scratching my head and looking here and trying it all I tinkered around more and noticed that if after I created the quick smoke, I then had to select the monkey head (object being applied to) then I was able to get the rendering to work.

Win 10/64bit running Blender 8.1. Same problem following Andrew Price's tutorial ([Blender 8.1 tutorial ](https://www.youtube.com/watch?v=MyxWDHy4ppY)) last minute of video. Basically if anyone was having the problem like me, following the video you create a quick smoke and after that is created, the object that is selected is the domain. I went into the domain object and changed it to flow and made it smoke/fire and it didn't work. After scratching my head and looking here and trying it all I tinkered around more and noticed that if after I created the quick smoke, I then had to select the monkey head (object being applied to) then I was able to get the rendering to work.

Added subscriber: @netcob

Added subscriber: @netcob

Workaround? Solve? Having the same issue in 2.81a. But if I bake the smoke domain before cycle rendering it works fine.

Workaround? Solve? Having the same issue in 2.81a. But if I bake the smoke domain before cycle rendering it works fine.

Removed subscriber: @Ethanicus

Removed subscriber: @Ethanicus

Added subscriber: @SenJacob

Added subscriber: @SenJacob

I have same issue in blender 2.82. Changing Type to "Replay" under Cache settings of Domain object's physics settings worked.
Also, with setting Type as "Final" and Bake All also works.
The default "Modular" Type option does not work for me.

image.png

I have same issue in blender 2.82. Changing Type to "Replay" under Cache settings of Domain object's physics settings worked. Also, with setting Type as "Final" and Bake All also works. The default "Modular" Type option does not work for me. ![image.png](https://archive.blender.org/developer/F8338985/image.png)

Added subscriber: @MauricioTarno

Added subscriber: @MauricioTarno

In #59838#871380, @SenJacob wrote:
I have same issue in blender 2.82. Changing Type to "Replay" under Cache settings of Domain object's physics settings worked.
Also, with setting Type as "Final" and Bake All also works.
The default "Modular" Type option does not work for me.

image.png

Can confirm!

> In #59838#871380, @SenJacob wrote: > I have same issue in blender 2.82. Changing Type to "Replay" under Cache settings of Domain object's physics settings worked. > Also, with setting Type as "Final" and Bake All also works. > The default "Modular" Type option does not work for me. > > ![image.png](https://archive.blender.org/developer/F8338985/image.png) Can confirm!

Added subscriber: @shelbs

Added subscriber: @shelbs

Had similar problem in cycles. Could see smoke in viewport in cycles+eevee, but not in final render.

I found that by setting the cache type to Modular, doing a full bake, and then switching to eevee, viewport rendering, and then switching back to cycles, I could now see my smoke in the final cycles render.

I believe that ensuring the entire simulation was baked was not the important step, but that toggling the renderer and making it render did something to get out of a broken state.

So it seems like there is a way to solve this problem. But feels like a bug to me.

I am on Linux, with GeForce GTX 1080 NVIDIA. Blender 2.83
NVIDIA-SMI 440.82 Driver Version: 440.82 CUDA Version: 10.2

Had similar problem in cycles. Could see smoke in viewport in cycles+eevee, but not in final render. I found that by setting the cache type to Modular, doing a full bake, and then switching to eevee, viewport rendering, and then switching back to cycles, I could now see my smoke in the final cycles render. I believe that ensuring the entire simulation was baked was not the important step, but that toggling the renderer and making it render did something to get out of a broken state. So it seems like there is a way to solve this problem. But feels like a bug to me. I am on Linux, with GeForce GTX 1080 NVIDIA. Blender 2.83 NVIDIA-SMI 440.82 Driver Version: 440.82 CUDA Version: 10.2

I don't think that this should be closed. Am I in the right thread? I can submit a full bug report if needed.

@ZedDB

I don't think that this should be closed. Am I in the right thread? I can submit a full bug report if needed. @ZedDB

Added subscriber: @KingKilo

Added subscriber: @KingKilo

I have a similar problem with #77977 (both in 2.82 and 2.83)

I'm working in Cycles, when I put it on "replay", I can see my smoke simulation in the viewport. But this is impossible to work with, on large scale smoke.
When I put it on "Modular" and BAKE my simulation, I can't see the smoke in my viewport, NOR in the final render..
However, when I bake NOISE, I suddenly can.

Switching to Eevee and back to cycles does nothing for me.

I tried baking Raw, OpenVDB and Uni Cache.
No changes.

Definitely a bug.
If this could be re-opened, that'd be great.

I have a similar problem with #77977 (both in 2.82 and 2.83) I'm working in **Cycles**, when I put it on "replay", I can see my smoke simulation in the viewport. But this is impossible to work with, on large scale smoke. When I put it on "Modular" and BAKE my simulation, I can't see the smoke in my viewport, NOR in the final render.. However, when I bake *NOISE*, I suddenly can. Switching to Eevee and back to cycles does nothing for me. I tried baking Raw, OpenVDB and Uni Cache. No changes. Definitely a bug. If this could be re-opened, that'd be great.

Added subscriber: @baberone

Added subscriber: @baberone

I had the same issue, after baking everything still no smoke.

I've added the Smoke domain material to the emitter too and since it seems to work.

I had the same issue, after baking everything still no smoke. I've added the Smoke domain material to the emitter too and since it seems to work.

Added subscriber: @Nepomuk

Added subscriber: @Nepomuk

Hi Folks,
I have seen many people with the same issue, perhaps it simply gets unstable in lower-end machines.
I have seen no positive comments about the Mantaflow engine so far. From high instability to non working at all.
Perhaps the devs could consider something simpler, with less tweaks, but reliable that could quickly emulate a simple fire and smoke (as in the previous 7.9 versions), and then build add-ons for more precise sims.
This is just my opinion, based on overall impressions I have seen over the net.
Blender is an impressive platform and is getting impressively better over time, but this particular feature needs urgent improvement regarding stability and reliability.

Hi Folks, I have seen many people with the same issue, perhaps it simply gets unstable in lower-end machines. I have seen no positive comments about the Mantaflow engine so far. From high instability to non working at all. Perhaps the devs could consider something simpler, with less tweaks, but reliable that could quickly emulate a simple fire and smoke (as in the previous 7.9 versions), and then build add-ons for more precise sims. This is just my opinion, based on overall impressions I have seen over the net. Blender is an impressive platform and is getting impressively better over time, but this particular feature needs urgent improvement regarding stability and reliability.

Added subscriber: @JeetGT

Added subscriber: @JeetGT

2 years passed, and this BUG still exists very much in Blender 2.82 EEVEE. The rendering of smoke is completely random, unstable and unpredictable. I can vouch this at least for EEVEE (I have not tested in Cycles). In last 2 weeks, I have tried to generate at least 50 different scenes with varying settings and I can finally confirm that it is simply a BUG in Blender.

There are numerous things that can affect the rendering. There are intuitive things like turning on volumetrics or using a higher clipping end. Then there are absolutely stupid things where we need to type-in "color" in the attribute field of the Principled Volume shader attached to the domain object. Then we have to also ensure adequate lighting for the scene. We have to change the cache type, we have to change the cache size. We have to switch the renderer between EEVEE & Cycles, and what not! Something works sometimes. And sometimes, nothing works! It just does not render.

I am extremely surprised to see that this issue has been closed without any real solution. The status is changed to "Duplicate" but there is no reference given to the other thread in order to follow that instead. Countless people have encountered this BUG, they are experiencing even today and the developers seem to not accept this as a BUG. Come on guys. Let us agree that something is seriously broken and let us solve this. Let us make this Fire & Smoke simulation stable across the platforms. It is very much frustrating.

2 years passed, and this BUG still exists very much in Blender 2.82 EEVEE. The rendering of smoke is completely random, unstable and unpredictable. I can vouch this at least for EEVEE (I have not tested in Cycles). In last 2 weeks, I have tried to generate at least 50 different scenes with varying settings and I can finally confirm that it is simply a BUG in Blender. There are numerous things that can affect the rendering. There are intuitive things like turning on volumetrics or using a higher clipping end. Then there are absolutely stupid things where we need to type-in "color" in the attribute field of the Principled Volume shader attached to the domain object. Then we have to also ensure adequate lighting for the scene. We have to change the cache type, we have to change the cache size. We have to switch the renderer between EEVEE & Cycles, and what not! Something works sometimes. And sometimes, nothing works! It just does not render. I am extremely surprised to see that this issue has been closed without any real solution. The status is changed to "Duplicate" but there is no reference given to the other thread in order to follow that instead. Countless people have encountered this BUG, they are experiencing even today and the developers seem to not accept this as a BUG. Come on guys. Let us agree that something is seriously broken and let us solve this. Let us make this Fire & Smoke simulation stable across the platforms. It is very much frustrating.

Added subscribers: @paul-124, @rjg

Added subscribers: @paul-124, @rjg

@JeetGT @paul-124 @KingKilo This ticket was closed because the issue it was a duplicate of was supposedly fixed. If there is a new (or continued) problem with Mantaflow please create a new ticket an provide the necessary information that allow us to investigate this. In particular we need to know what steps results in incorrect behavior and which OS/hardware is affected by this issue. This guide may help you write a good bug report with all the required information.

Submit a new report through Help > Report a bug in Blender and carefully follow the submission template . Please provide system information (operating system, GPU, driver version), Blender version, a short and precise description of the issue, step by step instructions to reproduce it and, if relevant, a minimal .blend file that showcases the problem.

@JeetGT @paul-124 @KingKilo This ticket was closed because the issue it was a duplicate of was supposedly fixed. If there is a new (or continued) problem with Mantaflow please create a new ticket an provide the necessary information that allow us to investigate this. In particular we need to know what steps results in incorrect behavior and which OS/hardware is affected by this issue. [This guide ](https://blender.stackexchange.com/questions/1377/best-place-to-put-bug-reports/173685#173685) may help you write a good bug report with all the required information. Submit a new report through *Help > Report a bug* in Blender and carefully follow the [submission template ](https://developer.blender.org/maniphest/task/edit/form/1/). Please provide **system information** (operating system, GPU, driver version), **Blender version**, a **short and precise description** of the issue, step by step **instructions to reproduce it** and, if relevant, **a minimal .blend file that showcases the problem**.

Added subscriber: @jordalefou

Added subscriber: @jordalefou

Hi, similar trouble, but fixed using smoke material:
https://docs.blender.org/manual/en/2.80/physics/smoke/material.html

Linux Centos 8 Workstation
AMD Ryzen 9 3900X 12-Core Processo
GeForce GTX 1660 SUPER, OpenCL 1.2 CUDA 11.1.70
32GiB System memory
Blender version: 2.90.1, python version: 3.7.7
render smoke.png

Hi, similar trouble, but fixed using smoke material: https://docs.blender.org/manual/en/2.80/physics/smoke/material.html Linux Centos 8 Workstation AMD Ryzen 9 3900X 12-Core Processo GeForce GTX 1660 SUPER, OpenCL 1.2 CUDA 11.1.70 32GiB System memory Blender version: 2.90.1, python version: 3.7.7 ![render smoke.png](https://archive.blender.org/developer/F9023797/render_smoke.png)
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
37 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#59838
No description provided.