Cycles Normal Baking Incorrect Edges with Extrusion #56579

Closed
opened 2018-08-27 23:28:14 +02:00 by Jonathan Lampel · 9 comments

System Information
Windows 10, Ryzen Threadripper, GeForce 1080Ti

Blender Version
Broken: 2.79 bb98e83b99
Worked: Can't find a build that does

Short description of error
When baking normals in Cycles, using Extrude instead of a cage object results in incorrect shading on sharp edges. It appears that each face of the virtual cage is firing rays in the direction of its original normals instead of the extruded normals.

This is never the desired behavior for a cage, because the result is the same as what can be accomplished without a cage.

Using Extrude at a value of 0.1:
cage_extrude.png 2018-08-27 14_13_53-Blender_ [C__Users_Jonathan_Desktop_baked-cube.blend].png

Using a linked duplicate cage object with a displacement of 0.1:
cage_objectpng.png 2018-08-27 14_18_04-Blender_ [C__Users_Jonathan_Desktop_baked-cube.blend].png

Exact steps for others to reproduce the error

  1. Unwrap a cube, with margins.
  2. Create a second cube with beveled edges, marked sharp, and set to smooth shading.
  3. Bake the beveled cube's normals to the original cube with 'Cage' enabled and Extrude set to 0.1
  4. Create a linked duplicate of the original cube and give it a displacement modifier with a value of 0.1
  5. Bake the beveled cube's normals to the original cube with 'Cage' enabled and the cage object set to the duplicated cube
  6. Compare both normal maps

baked-cube.blend

**System Information** Windows 10, Ryzen Threadripper, GeForce 1080Ti **Blender Version** Broken: 2.79 bb98e83b99e Worked: Can't find a build that does **Short description of error** When baking normals in Cycles, using Extrude instead of a cage object results in incorrect shading on sharp edges. It appears that each face of the virtual cage is firing rays in the direction of its original normals instead of the extruded normals. This is never the desired behavior for a cage, because the result is the same as what can be accomplished without a cage. Using Extrude at a value of 0.1: ![cage_extrude.png](https://archive.blender.org/developer/F4415725/cage_extrude.png) ![2018-08-27 14_13_53-Blender_ [C__Users_Jonathan_Desktop_baked-cube.blend].png](https://archive.blender.org/developer/F4415745/2018-08-27_14_13_53-Blender___C__Users_Jonathan_Desktop_baked-cube.blend_.png) Using a linked duplicate cage object with a displacement of 0.1: ![cage_objectpng.png](https://archive.blender.org/developer/F4415751/cage_objectpng.png) ![2018-08-27 14_18_04-Blender_ [C__Users_Jonathan_Desktop_baked-cube.blend].png](https://archive.blender.org/developer/F4415755/2018-08-27_14_18_04-Blender___C__Users_Jonathan_Desktop_baked-cube.blend_.png) **Exact steps for others to reproduce the error** 1. Unwrap a cube, with margins. 2. Create a second cube with beveled edges, marked sharp, and set to smooth shading. 3. Bake the beveled cube's normals to the original cube with 'Cage' enabled and Extrude set to 0.1 4. Create a linked duplicate of the original cube and give it a displacement modifier with a value of 0.1 5. Bake the beveled cube's normals to the original cube with 'Cage' enabled and the cage object set to the duplicated cube 6. Compare both normal maps [baked-cube.blend](https://archive.blender.org/developer/F4427267/baked-cube.blend)

Added subscriber: @JonathanLampel-4

Added subscriber: @JonathanLampel-4

Added subscriber: @jenkm

Added subscriber: @jenkm

You need to attach your .blend file.

You need to attach your .blend file.

Whoops, thought I had. Done!

Whoops, thought I had. Done!

Added subscribers: @brecht, @mont29

Added subscribers: @brecht, @mont29
Brecht Van Lommel was assigned by Bastien Montagne 2018-09-03 15:01:45 +02:00

@brecht no idea whether this is bug or intended behavior, will let you decide.

@brecht no idea whether this is bug or intended behavior, will let you decide.
Brecht Van Lommel was unassigned by Dalai Felinto 2019-12-23 16:36:01 +01:00

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Germano Cavalcante self-assigned this 2020-02-11 13:23:14 +01:00

I reproduced this bug in blender 2.79b, but not the latest daily build, so it appears the bug has been fixed already.

Please try the latest daily build: https://builder.blender.org/download/

If the problem persists, please let us know so we can re-open the report. Don't forget to mention the specific version you tested again.

I reproduced this bug in blender 2.79b, but not the latest daily build, so it appears the bug has been fixed already. Please try the latest daily build: https://builder.blender.org/download/ If the problem persists, please let us know so we can re-open the report. Don't forget to mention the specific version you tested again.
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
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#56579
No description provided.