Geometry Nodes - Set Shade Smooth node - not clear when "Autosmooth" is on #107354

Closed
opened 2023-04-26 01:18:09 +02:00 by Andres Stephens · 5 comments
Contributor

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68

Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3
Worked: version 3.5.0

Short description of error
blender_lcA7ECNtiB.png
Previously in Blender 3.5.0 you could Set Shade Smooth and the mesh would set the normals to shade smooth. Now in 3.5.1 and 3.6 builds, this node sets to what is apparently the "Autosmooth" normals mode - and when you apply the GN modifier, it will have the mesh set to autosmooth. This is not ideal UX - needs fixing and/or a socket to toggle autosmooth would be nice in this node.

Right now, the Set Shade Smooth is not setting normals to Smooth if Autosmooth is on, meaning it may cause unintended behaviour as a UX.

If you join meshes, realize instances or get mesh data from collection or objects, then it's broken and the autosmooth tick in the Normals panel does nothing, so you can't redefine autosmooth with the Set Shade Smooth.

Exact steps for others to reproduce the error

  1. Create a Suzanne - check if autosmooth is on
  2. Create a Geometry Nodes tree
  3. Add a Set Shade Smooth node and bool it on
  4. Apply modifier stack
  5. Notice the Normals Autosmooth socket is still on and that the normals are not smoothed by the node
**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68 **Blender Version** Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3` Worked: version 3.5.0 **Short description of error** ![blender_lcA7ECNtiB.png](/attachments/086be55d-ad17-42b8-a691-b016fea584c1) Previously in Blender 3.5.0 you could Set Shade Smooth and the mesh would set the normals to shade smooth. Now in 3.5.1 and 3.6 builds, this node sets to what is apparently the "Autosmooth" normals mode - and when you apply the GN modifier, it will have the mesh set to autosmooth. This is not ideal UX - needs fixing and/or a socket to toggle autosmooth would be nice in this node. Right now, the Set Shade Smooth is not setting normals to Smooth if Autosmooth is on, meaning it may cause unintended behaviour as a UX. If you join meshes, realize instances or get mesh data from collection or objects, then it's broken and the autosmooth tick in the Normals panel does nothing, so you can't redefine autosmooth with the Set Shade Smooth. **Exact steps for others to reproduce the error** 1. Create a Suzanne - check if autosmooth is on 2. Create a Geometry Nodes tree 3. Add a Set Shade Smooth node and bool it on 4. Apply modifier stack 5. Notice the Normals Autosmooth socket is still on and that the normals are not smoothed by the node
Andres Stephens added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-04-26 01:18:10 +02:00
Author
Contributor

Looks like this MAY be intended behaviour, where autosmooth in the Properties Editor>Mesh>Normals panel overrides the geometry nodes settings...

blender_EFW2SnLDUw.gif

This could be closed I guess.... I will update description.

Looks like this MAY be intended behaviour, where autosmooth in the Properties Editor>Mesh>Normals panel overrides the geometry nodes settings... ![blender_EFW2SnLDUw.gif](/attachments/c7b46c8e-92d7-417b-b026-369995c957f2) This could be closed I guess.... I will update description.
Andres Stephens changed title from Geometry Nodes - Set Shade Smooth - broken smooth setting, sets to "Autosmooth" instead to Geometry Nodes - Set Shade Smooth node - not clear when "Autosmooth" is on 2023-04-26 01:46:28 +02:00
Author
Contributor

To clarify, using shade smooth before or after getting mesh data from a collection makes the Autosmooth override useless in the parent geometry nodes object - making it default to parent object regardless of autosmooth settings.

To clarify, using shade smooth before or after getting mesh data from a collection makes the Autosmooth override useless in the parent geometry nodes object - making it default to parent object regardless of autosmooth settings.
Member

This looks expected indeed.

where autosmooth in the Properties Editor>Mesh>Normals panel overrides the geometry nodes settings

Same behavior is visible when you set "shade smooth" from context menu.

Worked: version 3.5.0

Don't think this is a regression. For me results are same in versions prior to 3.5

Will close this for now. Feel free to comment if there is misunderstanding, will reopen the report.

This looks expected indeed. > where autosmooth in the Properties Editor>Mesh>Normals panel overrides the geometry nodes settings Same behavior is visible when you set "shade smooth" from context menu. > Worked: version 3.5.0 Don't think this is a regression. For me results are same in versions prior to 3.5 Will close this for now. Feel free to comment if there is misunderstanding, will reopen the report.
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-04-26 14:34:51 +02:00

Shade smooth flag is object data i guess? Modifiers can't change that.

Shade smooth flag is object data i guess? Modifiers can't change that.
Author
Contributor

Thanks for clarifying @PratikPB2123 , seems the issue is more specific with the "Realize Instances" node. I will make another specific task for it.

Thanks for clarifying @PratikPB2123 , seems the issue is more specific with the "Realize Instances" node. I will make another specific task for it.
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#107354
No description provided.