4.1 beta shade smooth geonode ingores all edge mark sharp both from manual marking or modifiers #119133

Open
opened 2024-03-06 19:41:47 +01:00 by ValyArhal · 6 comments

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.61

Blender Version
Broken: version: 4.1.0 Beta, branch: blender-v4.1-release, commit date: 2024-03-03 21:50, hash: 8f68dfe0c24e
Worked: (newest version of Blender that worked as expected)

As shown in the video bevel edge mark sharp are completely ignored, manual edge marks as well behave completely randomly depending on edge angle

mark sharp is how it is internally controlled when using auto smooth by angle from the right click menu, yet the geonode completely ignores any kind of marking

broken shading when using shade smooth and mark sharp(images)

**System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.61 **Blender Version** Broken: version: 4.1.0 Beta, branch: blender-v4.1-release, commit date: 2024-03-03 21:50, hash: `8f68dfe0c24e` Worked: (newest version of Blender that worked as expected) As shown in the video bevel edge mark sharp are completely ignored, manual edge marks as well behave completely randomly depending on edge angle mark sharp is how it is internally controlled when using auto smooth by angle from the right click menu, yet the geonode completely ignores any kind of marking broken shading when using shade smooth and mark sharp(images)
ValyArhal added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2024-03-06 19:41:48 +01:00
Member

Thanks for the report. Could you attach the file from the video so we can investigate this further? Or at least a file with that object included.

Thanks for the report. Could you attach the file from the video so we can investigate this further? Or at least a file with that object included.
Hans Goudey added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-03-06 20:30:24 +01:00
Author

Thanks for the report. Could you attach the file from the video so we can investigate this further? Or at least a file with that object included.

file has been added, it has nothing to do with the file tho, it's been like this since the 4.1 shade smooth change
this whole system should have never been regressed to this point

> Thanks for the report. Could you attach the file from the video so we can investigate this further? Or at least a file with that object included. file has been added, it has nothing to do with the file tho, it's been like this since the 4.1 shade smooth change this whole system should have never been regressed to this point
Author

blender/blender#116922 also mentions in part the same issue as well as the whole concept of this new system being actively worse,
including blender/blender#118118 which brings up issues with backwards compatibility making it a one way trip that can corrupt files from my experience,
with additional mentions of mark sharp being non-distinguishable from a sharp edge blender/blender#114722

blender/blender#116922 also mentions in part the same issue as well as the whole concept of this new system being actively worse, including blender/blender#118118 which brings up issues with backwards compatibility making it a one way trip that can corrupt files from my experience, with additional mentions of mark sharp being non-distinguishable from a sharp edge blender/blender#114722
Member

Sorry if I'm not getting something obvious, but could you describe in more detail what is wrong with the model? Or alternatively, could you share something set up in 4.0 that has this problem when moved to 4.1? Maybe I'm missing something but when I compare the file loaded in 4.0 and 4.1, I'm not noticing any meaningful differences.

Sorry if I'm not getting something obvious, but could you describe in more detail what is wrong with the model? Or alternatively, could you share something set up in 4.0 that has this problem when moved to 4.1? Maybe I'm missing something but when I compare the file loaded in 4.0 and 4.1, I'm not noticing any meaningful differences.
Author

the main issue here is the mark sharp is not behaving like it did before, and not working if the mark is generated with things like modifiers and such, barely works by chance when marked manually as shown in the first video

it acts as a modifier making the order of the stack confusing to find where in the stack will shade correctly ignoring anything below, simply putting it at the end of the stack doesn't work with every model, slows the entire modeling process needlessly to check for mark sharp and why a model looks wrong, takes longer to calculate by multiple seconds, needs to be at the end of the modifier stack for the shading to work but can create issues with other modifiers which need to be at the end of the stack to work, it's not just mark sharp making the main part of the issues it's when the sharp geometry is considered

the main issue here is the mark sharp is not behaving like it did before, and not working if the mark is generated with things like modifiers and such, barely works by chance when marked manually as shown in the first video it acts as a modifier making the order of the stack confusing to find where in the stack will shade correctly ignoring anything below, simply putting it at the end of the stack doesn't work with every model, slows the entire modeling process needlessly to check for mark sharp and why a model looks wrong, takes longer to calculate by multiple seconds, needs to be at the end of the modifier stack for the shading to work but can create issues with other modifiers which need to be at the end of the stack to work, it's not just mark sharp making the main part of the issues it's when the sharp geometry is considered
Author

needs to be at the end of the modifier stack for the shading to work but can create issues with other modifiers which need to be at the end of the stack to work
additional proof that, the geonode requiring to be at the end creates massive issues: 1 blender artist thread 2 blender/blender#116395

`needs to be at the end of the modifier stack for the shading to work but can create issues with other modifiers which need to be at the end of the stack to work` additional proof that, the geonode requiring to be at the end creates massive issues: 1 [blender artist thread](https://blenderartists.org/t/blender-4-1-auto-smooth-is-now-a-modifier-only/1488922/433) 2 blender/blender#116395
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#119133
No description provided.