- User Since
- May 3 2017, 9:39 AM (128 w, 6 d)
Aug 8 2019
I'll try a buildbot build and report back.
Sorry, by "Stable" I meant the Official Release, yeah, that's the one I'm currently using. I haven't tried the buildbot ones after official hit.
I'd also like to mention that I've been using the 2.8 alphas for a long time without this kind of behavior, just started happening with Stable, although this might of course just be a coincidence.
Nothing to upgrade, I'm up to date (I also cannot update drivers separately, because MacOS and AMD). Also, as mentioned in the previous issue, this also happens rarely, about twice per hour.
Jul 6 2019
Jun 24 2019
The mesh was generated using a cloth simulation with a previous beta version of Blender 2.8. I was able to render without any problems on said version. Not sure why it's it corrupted now, but I don't expect Blender to hard crash either 🙂.
Jun 21 2019
Jun 19 2019
Thanks @Jeroen Bakker (jbakker) !
After some testing, the only "workaround" I can find is bumping AA samples to 32, which makes the Alpha 96.5% instead of 87.5% when using 8 samples. Still not really usable, but I'll work like this for now.
@Jeroen Bakker (jbakker) Thanks for looking into this (I was the person that posted about it on Blender Artists).
May 3 2017
Thank you, that certainly seems to fix the issue, although it makes all Renderlayers transparent (which is not the case in Blender Internal, although I'm not sure if that matters :D)... In any case, I guess this is not a real issue and can be closed.