Bug with 4.2 Smoothing Modifier smoothing result, compared to old smoothing in 4.0. #127694

Closed
opened 2024-09-16 14:30:44 +02:00 by Synced3D · 3 comments

System Information
Operating system: Windows-11-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 561.09

Blender Version
Broken: version: 4.2.1 LTS, branch: blender-v4.2-release, commit date: 2024-08-19 11:21, hash: 396f546c9d82
Worked: (newest version of Blender that worked as expected)

Short description of error
With the new smoothing as modifier, compared to the old smoothing workflow, I am running into multiple issues that lead to bad smoothing results, especially when working with smoothing and other modifiers at the same time.

In the attached files you find a blend file that includes smoothing together with a bevel modifier, using weighted edges and hardened normals. I also add a screenshot of the same project file opened in 4.0.1 (left) where it is smoothed correctly and 4.2.1 (right) with broken smoothing.

Exact steps for others to reproduce the error

  • Shade object smooth
  • Add bevel modifier
  • Set bevel modifier to weight and width; enable harden normals
  • set weight on specific edges

Overall Feedback - Next to this fundamental smoothing issue, the new workflow overall is terrible for bigger projects, especially for backwards compatibility if you have hundreds of objects in a scene.

Sadly me and my entire team at work do avoid switching from 4.01 to 4.2.1 because of exactly this reason.

I personally don´t see any advantage at all of having smoothing as a modifier. In my opinion it creates more steps and unnecessary work, compared to the "good old" smoothing workflow. As far as I can tell, me and my team at work are by far not the only ones in the blender community who see it this way.

Please consider changing the smoothing workflow back to how it was and always has worked through the last years.

Other than that, keep up the great work at Blender! I´m a Blender Artist for more than 17 years and you guys enabled my career with that! Thank you!

**System Information** Operating system: Windows-11-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 561.09 **Blender Version** Broken: version: 4.2.1 LTS, branch: blender-v4.2-release, commit date: 2024-08-19 11:21, hash: `396f546c9d82` Worked: (newest version of Blender that worked as expected) **Short description of error** With the new smoothing as modifier, compared to the old smoothing workflow, I am running into multiple issues that lead to bad smoothing results, especially when working with smoothing and other modifiers at the same time. In the attached files you find a blend file that includes smoothing together with a bevel modifier, using weighted edges and hardened normals. I also add a screenshot of the same project file opened in 4.0.1 (left) where it is smoothed correctly and 4.2.1 (right) with broken smoothing. **Exact steps for others to reproduce the error** - Shade object smooth - Add bevel modifier - Set bevel modifier to weight and width; enable harden normals - set weight on specific edges Overall Feedback - Next to this fundamental smoothing issue, the new workflow overall is terrible for bigger projects, especially for backwards compatibility if you have hundreds of objects in a scene. Sadly me and my entire team at work do avoid switching from 4.01 to 4.2.1 because of exactly this reason. I personally don´t see any advantage at all of having smoothing as a modifier. In my opinion it creates more steps and unnecessary work, compared to the "good old" smoothing workflow. As far as I can tell, me and my team at work are by far not the only ones in the blender community who see it this way. Please consider changing the smoothing workflow back to how it was and always has worked through the last years. Other than that, keep up the great work at Blender! I´m a Blender Artist for more than 17 years and you guys enabled my career with that! Thank you!
Synced3D added the
Status
Needs Triage
Severity
Normal
Type
Bug
labels 2024-09-16 14:30:45 +02:00

Thanks for the report. This issue seems to be a feature request, not a bug.

You could try to increase the angle value of the smooth by angle modifier or completly disable it (as you already use the shade smooth option on the object) to get similar results in version 4.2 as in 4.0 (see image).

For user requests and feedback, please use other channels: https://developer.blender.org/docs/handbook/communication/user_feedback/

For more information on why this isn't considered a bug, visit: https://developer.blender.org/docs/handbook/bug_reports/not_a_bug/

Thanks for the report. This issue seems to be a feature request, not a bug. You could try to increase the angle value of the smooth by angle modifier or completly disable it (as you already use the shade smooth option on the object) to get similar results in version 4.2 as in 4.0 (see image). For user requests and feedback, please use other channels: https://developer.blender.org/docs/handbook/communication/user_feedback/ For more information on why this isn't considered a bug, visit: https://developer.blender.org/docs/handbook/bug_reports/not_a_bug/

It seems you saved your file in 4.2 with applied modifier, after that you opened file in 4.0 and change modifiers to achieve the same result as before, but now file contains unused crease_edge and sharp_edge which is meaningless in 4.0, and now when you open file in 4.2 again this attributes makes things different compare in older version.
Can you test your file if you'll clrear unused attribtes in 4.0 and open this in 4.2?

It seems you saved your file in 4.2 with applied modifier, after that you opened file in 4.0 and change modifiers to achieve the same result as before, but now file contains unused `crease_edge` and `sharp_edge` which is meaningless in 4.0, and now when you open file in 4.2 again this attributes makes things different compare in older version. Can you test your file if you'll clrear unused attribtes in 4.0 and open this in 4.2?
Iliya Katushenock added
Status
Needs Information from User
Interest
Modeling
and removed
Status
Needs Triage
labels 2024-09-16 17:17:12 +02:00
Author

To avoid all conflicts, I just have remodeled a similar object in 4.2 real quick.

It seems that @Mattis-Vossmeier was correct. If I just "shade smooth" and highlight the edges that are not supposed to be smooth with sharp edges and then use the bevel modifier with weighted edges and hardened normals, it seems to work.

However, if I do shade smooth by angle (auto smooth) and then use the bevel modifier with weighted edges and hardened normals, then the issue (broken normals) appears.

So I guess Mattis is right that this is not a bug (even if it seemed like it is as you might understand) but rather a feature request.

Taking this into consideration - That would mean that for compatibility with older projects, one has to go through every model and change the smoothing plus adding sharp edges for similar results, correct?

So I assume that a feature request indeed would be good since it gives the impression that the new auto smooth is just adding working steps instead of making life easier.

To avoid all conflicts, I just have remodeled a similar object in 4.2 real quick. It seems that @Mattis-Vossmeier was correct. If I just "shade smooth" and highlight the edges that are not supposed to be smooth with sharp edges and then use the bevel modifier with weighted edges and hardened normals, it seems to work. However, if I do shade smooth by angle (auto smooth) and then use the bevel modifier with weighted edges and hardened normals, then the issue (broken normals) appears. So I guess Mattis is right that this is not a bug (even if it seemed like it is as you might understand) but rather a feature request. Taking this into consideration - That would mean that for compatibility with older projects, one has to go through every model and change the smoothing plus adding sharp edges for similar results, correct? So I assume that a feature request indeed would be good since it gives the impression that the new auto smooth is just adding working steps instead of making life easier.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2024-09-16 19:31:02 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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 & 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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
Asset System
Module
Asset System
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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#127694
No description provided.