- User Since
- Nov 11 2018, 2:08 AM (40 w, 6 d)
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.