Blender Freestyle LineSet Visibility problem at Render #49017

New Issue

Zachary1234 · 2016-08-05T03:48:39+02:00

Zachary1234 commented

2016-08-05 03:48:39 +02:00

System Information
Windows 10 64 bit Home

Blender Version
2.77a

Short description of error
Coincident planes with FreeStyle lines don't detect or render properly
via the Visibility condition for animation or image render.
This can occur via Freestyle Edges or Freestyle Faces.
This seems to be an issue inside Blender, irrespective
of the render engine.

Exact steps for others to reproduce the error

Have one smaller plane precisely located on another larger one.
Both have the identical material reference to prevent z-fighting.
There are no textures or images on the planes.
It isn't always possible to have 1 smallest unit offset between planes,
if for example one wants to do an origami simulation
with all paper folds accumulating to a virtual, zero thickness.

This issue can also prevent itself when animating
between various such states using Key Frames,
maybe involving the AnimAll plugin.

Examples include frames 400, 670, 560-580.

file.blend

**System Information** Windows 10 64 bit Home **Blender Version** 2.77a **Short description of error** Coincident planes with FreeStyle lines don't detect or render properly via the Visibility condition for animation or image render. This can occur via Freestyle Edges or Freestyle Faces. This seems to be an issue inside Blender, irrespective of the render engine. **Exact steps for others to reproduce the error** Have one smaller plane precisely located on another larger one. Both have the identical material reference to prevent z-fighting. There are no textures or images on the planes. It isn't always possible to have 1 smallest unit offset between planes, if for example one wants to do an origami simulation with all paper folds accumulating to a virtual, zero thickness. This issue can also prevent itself when animating between various such states using Key Frames, maybe involving the AnimAll plugin. Examples include frames 400, 670, 560-580. [file.blend ](https://blenderartists.org/forum/attachment.php?attachmentid=448546&d=1470892940)

Zachary1234 commented

2016-08-05 03:48:39 +02:00

Changed status to: 'Open'

Zachary1234 commented

2016-08-05 03:48:39 +02:00

Added subscriber: @poweruserm

blender-admin commented

2016-08-05 03:48:39 +02:00

#54532 was marked as duplicate of this issue

Bastien Montagne commented

2016-08-05 08:48:04 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2016-08-05 08:48:04 +02:00

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.

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 commented

2016-08-12 06:13:31 +02:00

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?

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?

Tamito Kajiyama was assigned by Bastien Montagne

2016-08-12 10:59:21 +02:00

Bastien Montagne commented

2016-08-12 10:59:21 +02:00

Added subscriber: @kjym3

Bastien Montagne commented

2016-08-12 10:59:21 +02:00

@poweruserm OK… editing to initial report does not trigger any new mail, so it goes unnoticed quite easily, unlike new comment. ;)

Thing is, coplanar faces are always (and will always be) a nest for render artifacts… I will let @kjym3 decide here, but pretty sure there is no bug here, deciding what to render in coplanar case is mostly a matter of “randomness”.

@poweruserm OK… editing to initial report does not trigger any new mail, so it goes unnoticed quite easily, unlike new comment. ;) Thing is, coplanar faces are always (and will always be) a nest for render artifacts… I will let @kjym3 decide here, but pretty sure there is no bug here, deciding what to render in coplanar case is mostly a matter of “randomness”.

Zachary1234 commented

2016-08-15 03:41:48 +02:00

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?

My model example in particular does require such freestyle line consistency,
without any offset between planes at all.

Shouldn't there be a per material and per object setting to disable
micro surface differences? This particular circumstance will require so.

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? My model example in particular does require such freestyle line consistency, without any offset between planes at all. - Shouldn't there be a per material and per object setting to disable micro surface differences? This particular circumstance will require so.

Aaron Carlisle commented

2017-09-19 05:26:33 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2017-09-19 05:26:33 +02:00

@kjym3 Hey, by any chance can you take a look at this? @poweruserm was asking on IRC today if there is any chance that this could be fixed/improved/a way around the issue. Thanks.

Tamito Kajiyama commented

2017-09-19 09:17:18 +02:00

Animated edge marks could be a partial solution (a workflow in this approach could be tedious and even not applicable in some cases though) -- see https://wiki.blender.org/index.php/User:Kjym3/DevFundProject/InterimReport for more information.

Another development direction would be to make edge coincidence a new feature edge type. Having that implemented, it would be easier to select coincident edges and distinguish one from another in support of other edge selection criteria (e.g., face marks).

As @mont29 pointed out, Freestyle is unable to address the visibility of coincident edges automatically, so that a degree of randomness is expected.

Animated edge marks could be a partial solution (a workflow in this approach could be tedious and even not applicable in some cases though) -- see https://wiki.blender.org/index.php/User:Kjym3/DevFundProject/InterimReport for more information. Another development direction would be to make edge coincidence a new feature edge type. Having that implemented, it would be easier to select coincident edges and distinguish one from another in support of other edge selection criteria (e.g., face marks). As @mont29 pointed out, Freestyle is unable to address the visibility of coincident edges automatically, so that a degree of randomness is expected.

Tamito Kajiyama commented

2018-04-07 16:17:28 +02:00

Added subscriber: @lichtwerk

Tamito Kajiyama was unassigned by Dalai Felinto

2019-12-23 16:37:02 +01:00

Jeroen Bakker commented

2020-01-27 09:42:48 +01:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2020-01-27 09:42:48 +01:00

Changed status from 'Confirmed' to: 'Archived'

Jeroen Bakker closed this issue

2020-01-27 09:42:48 +01:00

Jeroen Bakker self-assigned this 2020-01-27 09:42:48 +01:00

Jeroen Bakker commented

2020-01-27 09:42:48 +01:00

Original file cannot be accessed anymore. Next time, please upload it to the tracker so we can make sure that the file is accessible always.
I will close this issue as freestyle is working as expected. New developments isn't a bug. As freestyle isn't actively developed and it isn't clear what needs to be done I will register this issue as TODO/invalid.

Original file cannot be accessed anymore. Next time, please upload it to the tracker so we can make sure that the file is accessible always. I will close this issue as freestyle is working as expected. New developments isn't a bug. As freestyle isn't actively developed and it isn't clear what needs to be done I will register this issue as TODO/invalid.

Zachary1234 commented

2021-10-31 10:25:10 +01:00

To whom it may concern,
Here is my model file, I believe, and a one frame render that reveals the problem I was dealing with:

{F11635891}

I found that when using one material on multiple surfaces that weren't 3D separate, but were superimposed,
and that I also needed the "automatic" faculty of FreeStyle Line Edges, to associate to only one surface
instance, but not other surfaces or a material, FreeStyle Line Edges grows confused during rendering.
Blender, at that time, didn't have further logic to discriminate between material duplicate coincident surfaces,
when one is to be considered "upper" or "lower", and in different, partial places of involved surfaces.

Has anything happened since I tried to bost this "error" in this place, in Blender 3D? Does
this fall under a heading of something that someone could do something about?

To whom it may concern, Here is my model file, I believe, and a one frame render that reveals the problem I was dealing with: {[F11635891](https://archive.blender.org/developer/F11635891/Animation.blend)}![issue.jpg](https://archive.blender.org/developer/F11635897/issue.jpg) I found that when using one material on multiple surfaces that weren't 3D separate, but were superimposed, and that I also needed the "automatic" faculty of FreeStyle Line Edges, to associate to only one surface instance, but not other surfaces or a material, FreeStyle Line Edges grows confused during rendering. Blender, at that time, didn't have further logic to discriminate between material duplicate coincident surfaces, when one is to be considered "upper" or "lower", and in different, partial places of involved surfaces. Has anything happened since I tried to bost this "error" in this place, in Blender 3D? Does this fall under a heading of something that someone could do something about?

Zachary1234 commented

2021-10-31 10:44:28 +01:00

What I think should happen is that there should be a change or a setting of some kind
that tells Freestyle line edges to associate to only one surface at a time, and some
notion of "upper" and "lower" surfaces. But what does someone else think?
Have there been changes made to Blender, or any of its free plugins,
that would clearly help in these regards?

- What I think should happen is that there should be a change or a setting of some kind that tells Freestyle line edges to associate to only one surface at a time, and some notion of "upper" and "lower" surfaces. But what does someone else think? Have there been changes made to Blender, or any of its free plugins, that would clearly help in these regards?

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender Freestyle LineSet Visibility problem at Render #49017