Baking of normals show different results between versions #107930

Open
opened 2023-05-14 21:19:40 +02:00 by Saphi · 4 comments

System Information
Operating system: Win 10
Graphics card: Geforce 3060

Blender Version
Broken: 3.5.1
Worked: 3.4.1

This changed in 75ad8da1ea

Short description of error

Baking of normal map differnet between Blender versions

Exact steps for others to reproduce the error
The Attached blend file will output differnt result when trying to bake the normals.
The Mesh is part of a comercial mesh I use, therefore I cannot share the whole mesh, but in the blendfile you just need to bake the normals in blender 3.4.1 and then in 3.5.1
The results are differnet.

Blender 3.5.1 seams to have some bug in the baking or handles the baking differnt.

Edit:
Seams like the Auto-Smooth of meshes bauses this difference between the versions

**System Information** Operating system: Win 10 Graphics card: Geforce 3060 **Blender Version** Broken: 3.5.1 Worked: 3.4.1 This changed in 75ad8da1ea6799e3983e4146f4b20dc4bfbb8415 **Short description of error** Baking of normal map differnet between Blender versions **Exact steps for others to reproduce the error** The Attached blend file will output differnt result when trying to bake the normals. The Mesh is part of a comercial mesh I use, therefore I cannot share the whole mesh, but in the blendfile you just need to bake the normals in blender 3.4.1 and then in 3.5.1 The results are differnet. Blender 3.5.1 seams to have some bug in the baking or handles the baking differnt. Edit: Seams like the Auto-Smooth of meshes bauses this difference between the versions
Saphi added the
Priority
Normal
Status
Needs Triage
Type
Report
labels 2023-05-14 21:19:41 +02:00
Member

Related to #106439 and #107579 .

Related to #106439 and #107579 .
Member

Will check when that changed

Will check when that changed
Member

This changed in 75ad8da1ea

@HooglyBoogly : looks like an unintentional change?

This changed in 75ad8da1ea6799e3983e4146f4b20dc4bfbb8415 @HooglyBoogly : looks like an unintentional change?
Hans Goudey self-assigned this 2023-05-18 21:58:47 +02:00
Member

Sorry for the delay investigating this.

This happens because before 75ad8da1ea, the split edges code took custom normals into account when deciding whether to split an edge. i.e. if the custom normals were facing in the same direction around and edge, it wouldn't be split. The new algorithm is fairly different internally, it would be difficult to take that into account. And the old behavior also had a performance cost, for something that arguably wasn't that useful.

A simple fix is changing the auto smooth angle to 180 degrees, so no splitting will happen. As a benefit, computation should be a bit faster that way too.

This is a fundamental problem with the current custom normals UX in my opinion. "Auto Smooth" and custom normals are conflated, so you need to enable auto smooth to use custom normals, and it's easy to forget to disable the automatic splitting (by maxing out the angle threshold). This is changed/fixed in #108014.

Because this is a relatively niche problem with a simple workaround, and the system will be reworked in 4.0, I'm inclined to call this a known issue.

Sorry for the delay investigating this. This happens because before 75ad8da1ea6799e3983e4146f4b20dc4bfbb8415, the split edges code took custom normals into account when deciding whether to split an edge. i.e. if the custom normals were facing in the same direction around and edge, it wouldn't be split. The new algorithm is fairly different internally, it would be difficult to take that into account. And the old behavior also had a performance cost, for something that arguably wasn't that useful. A simple fix is changing the auto smooth angle to 180 degrees, so no splitting will happen. As a benefit, computation should be a bit faster that way too. This is a fundamental problem with the current custom normals UX in my opinion. "Auto Smooth" and custom normals are conflated, so you need to enable auto smooth to use custom normals, and it's easy to forget to disable the automatic splitting (by maxing out the angle threshold). This is changed/fixed in #108014. Because this is a relatively niche problem with a simple workaround, and the system will be reworked in 4.0, I'm inclined to call this a known issue.
Hans Goudey added
Type
Known Issue
Priority
Normal
and removed
Type
Report
Priority
High
labels 2023-06-21 17:53:18 +02:00
Hans Goudey removed their assignment 2023-06-21 20:35:31 +02: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
4 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#107930
No description provided.