Artifacts when rendering procedural Blenderman with Blender 2.8< (needs updating the assset on Blender Cloud) #86320

Closed
opened 2021-03-05 22:52:37 +01:00 by Raimund Klink · 19 comments

This was not a bug, but an artifact of the solidify with negative offset followed by a bevel modifier [which is just more apparent in 2.8+]
So the task here is just updating the asset on the Blender Cloud with slightly tweaked values on the solidify modifier.
What I have done: on object Plane.229 set the Offset on the solidify modifier from -1.0 to 0.0

Here is the updated file (opened, tweaked and resaved in 2.78c)
Blenderman.blend

Original report:

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72
system-info.txt

Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: blender/blender@02948a2cab
Worked: Blender <2.79b

Short description of error
Strange artifacts only visible in the rendered frame. Not in the viewport.

Exact steps for others to reproduce the error
Just download the project files from the official Blender site: https://cloud.blender.org/p/gallery/57e5084f0fcf294119c5055c
Open with Blender 2.8<
Press F12
Artifact should appear.
2021-02-28 20_46_51-Blender Render.png

I reduced the .blend to the responsible object:
Blender 2.zip

This was not a bug, but an artifact of the solidify with negative offset followed by a bevel modifier [which is just more apparent in 2.8+] So the task here is just updating the asset on the Blender Cloud with slightly tweaked values on the solidify modifier. What I have done: on object `Plane.229` set the Offset on the solidify modifier from -1.0 to 0.0 Here is the updated file (opened, tweaked and resaved in 2.78c) [Blenderman.blend](https://archive.blender.org/developer/F9883333/Blenderman.blend) Original report: **System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72 [system-info.txt](https://archive.blender.org/developer/F9870859/system-info.txt) **Blender Version** Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: `blender/blender@02948a2cab` Worked: Blender <2.79b **Short description of error** Strange artifacts only visible in the rendered frame. Not in the viewport. **Exact steps for others to reproduce the error** Just download the project files from the official Blender site: https://cloud.blender.org/p/gallery/57e5084f0fcf294119c5055c Open with Blender 2.8< Press F12 Artifact should appear. ![2021-02-28 20_46_51-Blender Render.png](https://archive.blender.org/developer/F9870921/2021-02-28_20_46_51-Blender_Render.png) I reduced the .blend to the responsible object: [Blender 2.zip](https://archive.blender.org/developer/F9870871/Blender_2.zip)
Author

Added subscriber: @Raimund58

Added subscriber: @Raimund58

Added subscriber: @deadpin

Added subscriber: @deadpin

To further help triage: the problem goes away when using "Clamp Overlap" in the Bevel modifier for that object. Why this only appears as a problem during the full render is still a mystery.

To further help triage: the problem goes away when using "Clamp Overlap" in the Bevel modifier for that object. Why this only appears as a problem during the full render is still a mystery.

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'

Can confirm the behavior (pretty sure it is a not a bug though).

Happens in the viewport as well if subdivision modifier is set to 2 subdivisions in the viewport.

If you look closely 2.79 actually has the same problem/artifact, just a little less extreme:
image.png

It is the solidify modifier generating intersecting edges which then the bevel modifier has problems dealing with:
solidify without offset
image.png
image.png

solidify with negative offset (as in the file)
image.png
image.png

I think there is no way of preventing the user to set up a solidify modifier in a way that would cause problems with consecutive modifiers.
Sure, bevel code changed in a way that made this more obvious in this special case, but that would not be considered a bug either.
Solution here is to slightly change the mesh or change the offset in the solidify modifier so that such intersecting edges would not be happening in the first place.

Thanx reporting, nice find, but I dont think we can really chase this further as a "proper" bug.
(feel free though to comment again if issues persist)

Can confirm the behavior (pretty sure it is a not a bug though). Happens in the viewport as well if subdivision modifier is set to 2 subdivisions in the viewport. If you look closely 2.79 actually has the same problem/artifact, just a little less extreme: ![image.png](https://archive.blender.org/developer/F9873503/image.png) It is the solidify modifier generating intersecting edges which then the bevel modifier has problems dealing with: solidify without offset ![image.png](https://archive.blender.org/developer/F9873516/image.png) ![image.png](https://archive.blender.org/developer/F9873518/image.png) solidify with negative offset (as in the file) ![image.png](https://archive.blender.org/developer/F9873523/image.png) ![image.png](https://archive.blender.org/developer/F9873526/image.png) I think there is no way of preventing the user to set up a solidify modifier in a way that would cause problems with consecutive modifiers. Sure, bevel code changed in a way that made this more obvious in this special case, but that would not be considered a bug either. Solution here is to slightly change the mesh or change the offset in the solidify modifier so that such intersecting edges would not be happening in the first place. Thanx reporting, nice find, but I dont think we can really chase this further as a "proper" bug. (feel free though to comment again if issues persist)
Author

@lichtwerk
Thank you for looking into it!
You might want to add a note to the the original Blenderman files so no more people stumble over it without a way to fix it :)

@lichtwerk Thank you for looking into it! You might want to add a note to the the original Blenderman files so no more people stumble over it without a way to fix it :)

Added subscriber: @dfelinto

Added subscriber: @dfelinto

@dfelinto : can we consider just saving this file with the solidify modifier tweaked (see above for why this fails) and reupload?

@dfelinto : can we consider just saving this file with the solidify modifier tweaked (see above for why this fails) and reupload?

@lichtwerk this is for the Blender Cloud team to decide. Having it tagged should be enough for them. Though may be better to create a new report only for the cloud (update asset, see known issue Txxx) instead.

@lichtwerk this is for the Blender Cloud team to decide. Having it tagged should be enough for them. Though may be better to create a new report only for the cloud (update asset, see known issue Txxx) instead.

Changed status from 'Archived' to: 'Confirmed'

Changed status from 'Archived' to: 'Confirmed'

I will just reuse this task here as the task for updating the asset on the cloud [will update the task description accordingly and upload the tweaked asset]

I will just reuse this task here as the task for updating the asset on the cloud [will update the task description accordingly and upload the tweaked asset]
Philipp Oeser changed title from Bug/Regression Artifacts when rendering procedural Blenderman with Blender 2.8< to Artifacts when rendering procedural Blenderman with Blender 2.8< (needs updating the assset on Blender Cloud) 2021-03-10 18:08:11 +01:00

Added subscriber: @MikeyN

Added subscriber: @MikeyN
Mike Newbon self-assigned this 2021-03-17 11:53:27 +01:00

Hey @lichtwerk are you able to provide an updated file?

I can add it to the cloud from there.

Hey @lichtwerk are you able to provide an updated file? I can add it to the cloud from there.
Author

@MikeyN The first file in the task description should be the updated file.

@MikeyN The first file in the task description should be the updated file.

@lichtwerk for the records. Blender cloud related issues have:

  • #blender_studio as tag.
  • #blender_cloud as subscriber.

This is the default values when someone reports a bug from the [Blender cloud > contact > report bug ]]. The form that is used in these cases is [ https:*developer.blender.org/transactions/editengine/maniphest.task/view/15/ | this .

@lichtwerk for the records. Blender cloud related issues have: * #blender_studio as tag. * #blender_cloud as subscriber. This is the default values when someone reports a bug from the [Blender cloud > contact > report bug ]]. The form that is used in these cases is [[ https:*developer.blender.org/transactions/editengine/maniphest.task/view/15/ | this ](https:*cloud.blender.org/contact/).

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'

File updated

File updated

@MikeyN : thx
@dfelinto : noted

@MikeyN : thx @dfelinto : noted
Sign in to join this conversation.
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: archive/blender-cloud#86320
No description provided.