- User Since
- Nov 11 2018, 2:08 AM (87 w, 1 d)
Fri, Jun 26
Thu, Jun 25
May 19 2020
Apr 29 2020
Apr 28 2020
I have to agree with Duarte.
Apr 24 2020
Mar 24 2020
Mar 17 2020
Mar 9 2020
Feb 13 2020
Jan 17 2020
I just checked it again and there's some inconsistent behavior happening.
Jan 11 2020
This issue is still happening for me. Attached is a screen recording of it using the latest 2.82 Beta
Dec 10 2019
Nov 16 2019
Further testing appears to show that adjusting the number of particles fixes the problem. So for example, if instead of the default 1000, I change it to 999 or 1001, the the dynamics work again.
Nov 15 2019
Nov 9 2019
Nov 2 2019
Derek. It appears you are right. I tried it with my second test file, that had the dark small squares, and turning that value to 0 solved the problem.
Oct 31 2019
I hear you. But this was the exact glitch I created this bug report from. Those images are created from the same file I posted when I created the bug report back in July.
Maybe the dark black squares are a different issue. I’ll try later today with the other file I posted.
I did restart the render every time. Attached are render images of both before and after adjusting the empty space parameter and also one of the fix I found, moving the ground plane slightly (0.01)
The empty space parameter actually made it worse when turned to 0. That said, playing a little more with it I found that my ground, was overlapping the edge of the domain, moving it slightly fixed the problem in this scene. I'll need to do more tests to see if that is always the case, or if it just happened for this specific scene.
Oct 9 2019
Thanks Sebastián. This is great! There's probably still some problems, but at least this makes the smoke simulator usable again until MantaFlow comes out.
Oct 7 2019
Sep 30 2019
Question for the devs. Is there a reason why we can't revert back to 2.79's behaviour. I understand that there are some bugs in it, but for the most part it was working in 2.79. Now there's features we can't even use.
Can we just bring back the old behaviour, even with the bugs, until we get MantaFlow? Maybe it's set as an "experimental feature" .
Jul 20 2019
Any plans for this to be fixed before the final since the launch has been delayed with RC2?
Jul 14 2019
Jul 13 2019
Here's another example. This time in a Windows 10 machine with an 1050ti card and up to date drivers.
You can see the small dark areas on the floor are shadow glitches.
Jul 12 2019
Jul 5 2019
Thanks for the quick reply @Brecht Van Lommel (brecht).
May 31 2019
This appears to have been fixed in the latest build.
May 17 2019
Are developers considering merging mantaflow into blender for 2.80 release? If not, I think these bugs should be addressed. As it is, we have a broken simulation system that should not be shipping with an official release.
I have also recently noticed this. I'm working on a mixed platform pipeline to which I introduced blender. The acceptance has been good and people are excited about what blender can do. That said, not everyone is going to change overnight to blender. And for the time being I still have to export the final scenes (and simulations) to be rendered in Arnold. Not having a correct naming structure is causing several problems with the workflow and being able to sell the team on blender's capabilities.
I have also noticed this recently. I simple fix could be to have the index before the frame number. i.e: fileName_index_frameNumber
May 14 2019
You are correct. It is possible to bring it from 2.79. That's what I'm doing now, but it's a much slower (and limited) workflow.
May 13 2019
Any news on this? I'm also working on a simulation that requires subframe sampling and it would be great for this to work.