Fri, Jun 28
This is because it previously relied on Blender Internal to triangulate the meshes, but that's missing now.
Thu, Jun 27
May 21 2019
May 20 2019
Apr 11 2019
More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.
Apr 4 2019
Mar 28 2019
This is most likely to be an out of memory error. Unfortunately we are still searching for the best way to prevent this but this is out of our hands (the driver manages the resources).
Mar 18 2019
I noticed the same with mesh hair (imported from DAZ studio), I ended up deleting all the faces that are not visible from the outside, then some more and finally I was able to get it to render. Without the hair mesh the freestyle render is so fast I barely notice it.
Mar 14 2019
Indeed seems to be fixed, perhaps due to rB41cb5658803bf3b96f18e93c74c6af66ecdb1e83.
It seems this bug was fixed recently, at least on Linux.
Can someone confirm this?
Feb 20 2019
Feb 14 2019
Jus these things:
Does it print anything suspicious if you run blender with --debug-gpu and render? (So it crashes)
Yes works fine with Cycles, Crashes with Eevee.
i just checked with latest beta and for me freestyle only works, if I select a collection with no sub-collections.
don't know if this is a bug or meant to be, but I would prefer if it could render all sub-collections as freestyle too.
Feb 13 2019
Does it only happen with eevee? Does it crash if you choose cycles instead?
Yep same thing
It renders fine for me:
Feb 1 2019
This is solved in 2.8, where freestyle uses the same triangulation as everywhere else in Blender.
Jan 31 2019
Confirming - got the same issue
Jan 28 2019
Updating blender2.8 -> master in my local repo, and rebuilding, showed the problem is resolved. :)
In 2.80 (git built within the week (168a6a4bfc1)).
Linux (Debian stable).
Official Nvidia drivers. Geforce 970. Driver Version: 390.48
Jan 25 2019
Excellent! You guys are too fast for me. :)
This was just fixed, your build is one day too old.
Jan 24 2019
Jan 23 2019
Jan 22 2019
Jan 21 2019
Jan 18 2019
I have tried your file. If I set the collection to "Inclusive", neither cube will be freestyled. If I set it to exclusive, then both cubes will have freestyled edges. The issue I'm having is that I cannot make it so one cube is freestyled and the other not be.
Well, like I said: in the file I posted I cannot reproduce the issue, both inclusive/exclusive collection do work on my side, have you checked that file (if that works for you as well, it gives us a hint on how to proceed)
This bug occurs with both Eevee and cycles.
Cannot really reproduce here.