Bevel, Edge Split and the shading regression #35616

Closed
opened 2013-06-03 15:51:56 +02:00 by Moolah Nasreddin · 4 comments

%%%--- Operating System, Graphics card ---
win32

I've made this report previously thinking about to post it in this thread http://projects.blender.org/tracker/?func=detail&atid=498&aid=35584&group_id=9
But I've realized that I need to create a new report.

- Short description of error ---

Bevel and Edge Split modifiers can't be used together effectively now. A possible solution is to give "mark sharp" for bevels' boundaries in Bevel modifier.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

- Further it's just a long version of the description including the steps---

Please, don't take it as a disrespect. I know that improving a program is a hard work. But I think about this case (described down here) as a regression.

I've made a working example that is a part of a real model. The mesh is supposed to use for baking as a high-poly input.

Please, open Shading_Regression_example.blend with Blender 2.66 (I've used r54698) and notice how good it looks. And actually the "optimized" side (there is everything marked and described) looks worse than another (with n-gons). It's related to the combination of Bevel and EdgeSpit modifiers. I've already used this method to model and bake. It works almost perfect and (that is very important) saves a lot of time.
Also switch off "Edge Angle" in the Edge Split modifier and you'll see that it works good without it (and gives a nice and smooth shading).
This was before "the shading commit" that was mentioned in this thread http://projects.blender.org/tracker/?func=detail&atid=498&aid=35584&group_id=9

Now open the blend with Blender 2.67b. You'll see that any side looks bad. Probably it's because Bevel modifier gives n-gons. And now this robust combination Bevel+Edge Split is useless in most of complex hi-poly meshes. Even flat surfaces looks bad.
Then if you'll switch off "Edge Angle" in the Edge Split modifier the result looks just horrible.

BUT! When I've applied Bevel and manually set some of the necessary edges to Sharp the model looks nice again!

You can see this in Possible_Solution_for_EdgeSplit_and_Bevel.blend
Unfortunately it's not with "interactive bevels" now. And manually marking all edges that need to be Sharp is a waste of time.

As a solution I can suggest to propagate the input mesh's edges that were marked as sharp to Bevel modifier. So it will "mark" bevels' boundary edges as sharp (maybe as an option). I guess it's possible to make and will give great results.

Thank you for your hard work, guys! :)%%%

%%%--- Operating System, Graphics card --- win32 I've made this report previously thinking about to post it in this thread http://projects.blender.org/tracker/?func=detail&atid=498&aid=35584&group_id=9 But I've realized that I need to create a new report. - Short description of error --- Bevel and Edge Split modifiers can't be used together effectively now. A possible solution is to give "mark sharp" for bevels' boundaries in Bevel modifier. - Steps for others to reproduce the error (preferably based on attached .blend file) --- - Further it's just a long version of the description including the steps--- Please, don't take it as a disrespect. I know that improving a program is a hard work. But I think about this case (described down here) as a regression. I've made a working example that is a part of a real model. The mesh is supposed to use for baking as a high-poly input. Please, open Shading_Regression_example.blend with Blender 2.66 (I've used r54698) and notice how good it looks. And actually the "optimized" side (there is everything marked and described) looks worse than another (with n-gons). It's related to the combination of Bevel and EdgeSpit modifiers. I've already used this method to model and bake. It works almost perfect and (that is very important) saves a lot of time. Also switch off "Edge Angle" in the Edge Split modifier and you'll see that it works good without it (and gives a nice and smooth shading). This was before "the shading commit" that was mentioned in this thread http://projects.blender.org/tracker/?func=detail&atid=498&aid=35584&group_id=9 Now open the blend with Blender 2.67b. You'll see that any side looks bad. Probably it's because Bevel modifier gives n-gons. And now this robust combination Bevel+Edge Split is useless in most of complex hi-poly meshes. Even flat surfaces looks bad. Then if you'll switch off "Edge Angle" in the Edge Split modifier the result looks just horrible. BUT! When I've applied Bevel and manually set some of the necessary edges to Sharp the model looks nice again! You can see this in Possible_Solution_for_EdgeSplit_and_Bevel.blend Unfortunately it's not with "interactive bevels" now. And manually marking all edges that need to be Sharp is a waste of time. As a solution I can suggest to propagate the input mesh's edges that were marked as sharp to Bevel modifier. So it will "mark" bevels' boundary edges as sharp (maybe as an option). I guess it's possible to make and will give great results. Thank you for your hard work, guys! :)%%%

Changed status to: 'Open'

Changed status to: 'Open'

%%%Yes this is a regression, but its a duplicate of [#34445], (which you also reported).

New bevel isnt maintaining edge data which is needed in this case.

closing.%%%

%%%Yes this is a regression, but its a duplicate of [#34445], (which you also reported). New bevel isnt maintaining edge data which is needed in this case. closing.%%%

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

%%%Sorry! I can forget some things :)%%%

%%%Sorry! I can forget some things :)%%%
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
2 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#35616
No description provided.