Wed, Feb 15
Thu, Feb 2
Dec 28 2016
Dec 5 2016
I confirmed this is a regression from the 2.76 release. I will look into the issue.
Nov 18 2016
Thanks Bastien for the triage, and I confirmed the issue on my side. I will look into it as soon as time permits.
@Tamito Kajiyama (kjym3) Care to check this one? thanks :)
Nov 17 2016
Oct 30 2016
If I remember correctly, I didn't even consider the possibility of imposing the constraint that there must be at least one lineset. It is easy to check if there's a lineset, and I was not aware of negative effects due to an empty set of linesets.
Oct 29 2016
This issue has been resolved. Thanks for the bug report!
I can confirm the issue. The UI code doesn't have a check for lineset existence, resulting in firing up errors in the console.
@Folkert de Vries (flokkievids) Would you mind take a look? Thanks.
Oct 27 2016
Sep 30 2016
Sep 29 2016
Sep 28 2016
Sep 22 2016
Aug 23 2016
Thanks @Sergey Sharybin (sergey) for the triage. I will look into the reported issue.
It's a bit cruel to ask freestyle to outline all the hair actually...
It appears having 14 children is an issue. When changing it down to 1 it doesn't bog down. 3.4ghz cpu too.
Aug 15 2016
I understand this, even within one material instance. However I may need
to model without material surface "differences". Is there a way
to disable this, or to have blender detect plane coincidences with
freestyle line coincidences more systematically?
Aug 13 2016
Aug 12 2016
@Zachary1234 (Zachary1234) OK… editing to initial report does not trigger any new mail, so it goes unnoticed quite easily, unlike new comment. ;)
I see that this has been added as a comment. I believe I deleted a bunch of emails by mistake. Can Bastien
at least reply to me again? What is the view to my bug raise here? Will there be anything actioned?
Aug 11 2016
Aug 5 2016
Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
@Zachary1234 (Zachary1234): Please make a new report, following our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
-I just wanted to add the comment that I have been encountering this notification error too.
It occurs in image and animation render. In may occur during baking.
However, during command line animation render, it occurs far too much,
and takes away computation time between finishing one frame and starting the next.
Jul 12 2016
I have uploaded the ported code to: https://github.com/DarkDefender/blender-npr-tess2
Jun 20 2016
Apr 28 2016
Hi, what is the status of this bug, are there any development progresses on this bug? Subdivision the face or the line to solve this issue is not quite good method, and it takes a lot of time.
See my similar detailed bug report in Any feature in Blender which can show front edges and back edges differently like in Sketchup - Blender Stack Exchange.
Apr 27 2016
After all I just installed the new nvidia drivers I was skipping ( because I thought they were just "game-ready" stuff ) and it got solved. So, my fault here.
Apr 26 2016
Can not reproduce the issue on Windows 10 with GTX980Ti. Things to check:
Apr 6 2016
Apr 5 2016
Apr 4 2016
Can confirm the issue… Note that this is more a warning that a real error - yet it should not happen (changes were made recently in how ID usercount is managed, we are now much stricter on this aspect, but it means some areas still need fixing…).