Thu, Feb 14
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.
Wed, Feb 13
Does it only happen with eevee? Does it crash if you choose cycles instead?
Yep same thing
It renders fine for me:
Fri, Feb 1
This is solved in 2.8, where freestyle uses the same triangulation as everywhere else in Blender.
Thu, Jan 31
Confirming - got the same issue
Mon, Jan 28
Updating blender2.8 -> master in my local repo, and rebuilding, showed the problem is resolved. :)
In 2.80 (built within the week), in Linux (Debian stable w/official Nvidia drivers), appending objects from a 2.79 project, then Freestyles enabled, also results in a black render. The render layer also appears black in the compositor -- and only when Freestyles is enabled -- the objects show fine when freestyles is disabled.
Fri, Jan 25
Excellent! You guys are too fast for me. :)
This was just fixed, your build is one day too old.
Thu, Jan 24
Wed, Jan 23
Tue, Jan 22
Mon, Jan 21
Fri, Jan 18
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.
Jan 4 2019
Dec 22 2018
Dec 5 2018
Nov 4 2018
Nov 2 2018
Oct 26 2018
Sep 24 2018
Thanks, will commit the patch.