Material glitches at joints when using Bevel modifier #97000

Open
opened 2022-04-03 14:22:43 +02:00 by George Hawkins · 6 comments

System Information
Operating system: Ubuntu 20.04.3 LTS
Graphics card: GeForce RTX 2060

Blender Version
Broken: 3.1.2, cc66d1020c, master, 2022-03-31
Worked:

Short description of error

I know people experience no end of unexpected Bevel behavior due to issues with their geometry. But I think this is a genuine bug - as do people who responded to my Blender SE question: https://blender.stackexchange.com/q/258493/124535

Robin Betts commented there that "it looks like a bug. But at least a consistent, and therefore traceable bug. It seems to be in the 'Automatic' (-1) material offset setting, which should split the bevel down the middle at material boundaries. It's getting the boundary 1-off at the end of a patch/arc spread of faces."

At joints where two materials meet, the Bevel modifier seems to miscalculate which faces of the bevel should contain one material and which the other, as shown here:

image.png

If I apply the modifier, I can then correct the issue by hand.

The above picture is from Blender 3.1.2. The problem seems to have been there for a long time, things look different but are still incorrect in 2.93.7:

image.png

The complete mesh is fairly simple (I cut it out of a larger object for this bug report) and I've confirmed there are no overlapping vertices etc.:

image.png

I actually started with a much simpler mesh but converted to triangles to ensure the issue wasn't somehow n-gon related (it isn't):

image.png

Exact steps for others to reproduce the error

Create a simple shape like the one shown in the last image above and use two different materials for your object, e.g. above, I've applied one material to the darker colored faces and the other to the lighter colored faces.

Then apply a Bevel modifier and then look at the object in a Viewport Shading mode that shows materials, e.g. Material Preview or Rendered (you can even see the issue with Solid viewport shading if you set the Viewport Display for one of the materials to be a different color to the default grey).

Here are two small .blend files - the first created in Blender 3.1.2 and the second in Blender 2.93.7:

bevel-3.1.2.blend

bevel-2.93.7.blend

You can find a larger .blend file containing the original full mesh in my Blender SE question: https://blender.stackexchange.com/q/258493/124535

**System Information** Operating system: Ubuntu 20.04.3 LTS Graphics card: GeForce RTX 2060 **Blender Version** Broken: 3.1.2, cc66d1020c3b, master, 2022-03-31 Worked: **Short description of error** I know people experience no end of unexpected Bevel behavior due to issues with their geometry. But I think this is a genuine bug - as do people who responded to my Blender SE question: https://blender.stackexchange.com/q/258493/124535 Robin Betts commented there that "it looks like a bug. But at least a consistent, and therefore traceable bug. It seems to be in the 'Automatic' (-1) material offset setting, which should split the bevel down the middle at material boundaries. It's getting the boundary 1-off at the end of a patch/arc spread of faces." At joints where two materials meet, the Bevel modifier seems to miscalculate which faces of the bevel should contain one material and which the other, as shown here: ![image.png](https://archive.blender.org/developer/F12966244/image.png) If I apply the modifier, I can then correct the issue by hand. The above picture is from Blender 3.1.2. The problem seems to have been there for a long time, things look different but are still incorrect in 2.93.7: ![image.png](https://archive.blender.org/developer/F12966264/image.png) The complete mesh is fairly simple (I cut it out of a larger object for this bug report) and I've confirmed there are no overlapping vertices etc.: ![image.png](https://archive.blender.org/developer/F12966270/image.png) I actually started with a much simpler mesh but converted to triangles to ensure the issue wasn't somehow n-gon related (it isn't): ![image.png](https://archive.blender.org/developer/F12966292/image.png) **Exact steps for others to reproduce the error** Create a simple shape like the one shown in the last image above and use two different materials for your object, e.g. above, I've applied one material to the darker colored faces and the other to the lighter colored faces. Then apply a *Bevel* modifier and then look at the object in a *Viewport Shading* mode that shows materials, e.g. *Material Preview* or *Rendered* (you can even see the issue with *Solid* viewport shading if you set the *Viewport Display* for one of the materials to be a different color to the default grey). Here are two small `.blend` files - the first created in Blender 3.1.2 and the second in Blender 2.93.7: [bevel-3.1.2.blend](https://archive.blender.org/developer/F12966314/bevel-3.1.2.blend) [bevel-2.93.7.blend](https://archive.blender.org/developer/F12966315/bevel-2.93.7.blend) You can find a larger `.blend` file containing the original full mesh in my Blender SE question: https://blender.stackexchange.com/q/258493/124535
Author

Added subscriber: @GeorgeHawkins

Added subscriber: @GeorgeHawkins
Member

Added subscriber: @OmarEmaraDev

Added subscriber: @OmarEmaraDev
Member

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

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Minimal file to reproduce the issue. Defaults with Miter Outer -> Arc.

bevelMaterialBleed.blend

Minimal file to reproduce the issue. Defaults with Miter Outer -> Arc. [bevelMaterialBleed.blend](https://archive.blender.org/developer/F12969254/bevelMaterialBleed.blend)

Added subscriber: @thefoofighter

Added subscriber: @thefoofighter

This issue is still present in 3.2

As mentioned it only appears to happen when Miter Outer is set to Arc
image.png
image.png

This issue is still present in 3.2 As mentioned it only appears to happen when **Miter Outer** is set to **Arc** ![image.png](https://archive.blender.org/developer/F13213138/image.png) ![image.png](https://archive.blender.org/developer/F13213144/image.png)
Philipp Oeser removed the
Interest
Modeling
label 2023-02-09 15:27:55 +01:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 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: blender/blender#97000
No description provided.