Creator of BlenderGuru.com.
Blender user since 2003.
- User Since
- Jan 19 2011, 1:47 PM (538 w, 5 d)
Creator of BlenderGuru.com.
Jan 25 2021
Correct. Still unsolved.
@Sebastián Barschkis (sebbas) have you had a chance to revisit it yet?
Nov 28 2020
Just tried it in 2.91 using the .blend from the OP and am still seeing lines.
And yeah displacement + normals is a super common workflow. If it's breaking it as badly as this IMO it should be high priority.
Nov 27 2020
Hey @Germano Cavalcante (mano-wii),
This shouldn't be related to Cycles Adaptive Subdivision at all. This happens in based displacement which is different to adaptive.
Nov 10 2020
Nov 2 2020
Oct 16 2020
Hey. I downloaded the nightly build and it seems to have resolved it (fingers crossed!). I'll report back if I see it again.
Oct 15 2020
On twitter John Malcolm said this:
Sep 25 2020
Any update on this one? I just tested it in 2.9 using the bug blend file attached in OP and it's still happening.
Jul 21 2020
Nice! I'll give it a try tomorrow once the builds are updated with the new fix.
Jul 20 2020
Any update on this? Sean Kennedy also ran into it.
Jun 30 2020
Whoa that was fast! Thanks so much Philipp.
Jun 29 2020
May 4 2020
Apr 13 2020
Nice! Thanks Sebastian. I'm yet to test it myself, but good to see another one marked as resolved.
Apr 4 2020
Just rendered the animation successfully without crashing. Not sure if it was factory settings, or the reformat that did it, but either way we can close this now. Thanks!
Mar 30 2020
Thanks so much! Just tried with the latest build and it seems to work without error now. Beautiful! Cheers
Legendary! Thanks for fixing this so quickly :)
@Ankit Meel (ankitm)
Sorry for the lack of replying. I didn't realize there was an action item for me.
I've just reformatted my machine. I'll try rendering on a clean version with factory settings of the latest build tonight. Will report back with an answer.
Mar 27 2020
Any updates on this? Hoping to use this in a landscape tutorial.
Mar 22 2020
Mar 20 2020
@Sebastián Barschkis (sebbas) The Slow option is confusing because the user expects it to change the weight of the dissolve (similar to a power curve), but not the end frame.
Mar 19 2020
You're right. Seems if you increase it to 5000 the smoke is visible for a few frames after fire disperses:
Mar 16 2020
Unless I'm mistaken, that is no longer true. In the link you posted the top voted answer is:
Mar 14 2020
Mar 11 2020
@Richard Antalik (ISS) Changing the resolution doesn't change much. It just makes the gaps between the lines smaller:
Awesome! Yeah I was hoping that setting would go lower. Will try it in the new version and let you know if it feels awkward using such low values. Cheers
Mar 10 2020
No this is separate. The lines are part of the simulation, not the shader.
Also, I remember the previous minimum amount was 0.10. Does this change let it go to 0.01?
I agree with Aaron. It made me confused before.
Thank you for the fast response!
Mar 9 2020
Just chiming in to confirm that this is still very much a bug in Blender 2.82 using Mantaflow. Seems to appear in every single smoke animation.
Just chiming in to confirm this bug. I've also encountered it several times.
Ohh it's a bug! That explains why setting CFL to a low value creates chaos: it wasn't increasing the steps automatically!
Mar 5 2020
Very true, sorry I didn't read through that page clearly enough. Thanks Aaron!
Mar 4 2020
Thanks! I completely missed that page.
Mar 2 2020
Feb 26 2020
Feb 25 2020
Feb 20 2020
Here's another example with viewport Color Mapping set to show Density. This demonstrates that it recognizes the density but ignores it.
@Felix Holzapfel (Wooody)
I appreciate the workaround, but I don't think this solves the problem. Not only would it instantly make the adaptive domain box huge (thus defeating it's purpose) but that smoke density will appear in the render which I obviously don't want. At the moment it's just easier to turn it off, but that drastically increases bakes.
Feb 19 2020
Here's another example showing how severe it is. Blend File:
Feb 18 2020
Confirming this bug in Blender 2.82. Changing the Threshold doesn't seem to make a difference.
Jan 22 2020
What's the verdict on the above post? Can it be fixed?
Dec 20 2019
Oct 25 2019
I've discovered this only appears when High-Resolution is checked in Smoke Domain Settings. And it's more noticeable with more divisions (level 2 onwards).
Oct 22 2019
Thanks for the quick fix on the smoke @Sebastián Barschkis (sebbas).
Oct 9 2019
Is there really no faster timeline for this?
Jul 26 2019
Oh I see.
Jun 26 2019
Jun 21 2019
Interesting! I didn't know UE4 had it default on as well. But you're right that a "Game View" toggle allows users to see it the correct way, whereas no such toggle exists in Eevee. Hence confusion.
Jun 20 2019
Apr 23 2019
Mar 14 2019
Ditto this. Annoying little bug.
Feb 19 2019
Feb 16 2019
Jan 25 2019
Jan 18 2019
Ah I didn't even know that option was there!
Jan 17 2019
Jun 21 2017
Jun 20 2017
Sep 23 2016
May 14 2016
Oh man just saw this! I guess I didn't have email notifications turned on. Sorry for missing all these comments!
Apr 12 2016
Apr 14 2015
Ditto that! Anyone know how complex it would be to fix?
Nov 28 2014
Jul 12 2014
Sorry for the lack of information. The build I used was yesterday's hash: 83f5d41, where it was crashing.
Jul 11 2014
Apr 23 2014
Mar 10 2014
Just tried that and can confirm it as well (on Windows).
Mar 9 2014
Feb 19 2014
Thanks guys much appreciated :)
Feb 18 2014
That sounds like a good idea. Removing the option would stop the mistake from happening all together.
Ah I see. So could the two options be tethered then to avoid confusion? Like when you click Link, Instance Groups is automatically checked too?
Seems others on twitter have been confused by this too.
Feb 13 2014
@Warren Bahler (russcript)
Actually that may be an argument against using that symbol, since they perform completely different functions and would therefore confuse users.
Feb 11 2014
Wow that's an awesome addition. Thanks @Campbell Barton (campbellbarton) :)