Normal edit modifier produces jagged edged renderings in 2.77 #48576

Closed
opened 2016-06-02 22:27:53 +02:00 by Wasili Novratidis · 5 comments

System Information
Windows 10 Pro, Nvidia GTX 660

Blender Version
Broken: (example: 2.77.1 11b0874)
Worked: (in 2.76 various versions)

Short description of error
When applying the normal edit modifier when rendering in Blender Internal it produces a jagged edge where the normal edit modifier has been applied. There is also a weird view in the viewport but I could not reproduce this in the startup file. See images

the jaw line has the jagged edge:
normaleditmodifier.jpg

See the facebook post for things we already tried to counter this effect:
https://www.facebook.com/groups/BNPRandFreestyle/permalink/1180238755332559/

Exact steps for others to reproduce the error
this could also be reproduced by using a start up file of susanne and applying the normal edit without any material applied to it.
normaleditmodifier.blend

**System Information** Windows 10 Pro, Nvidia GTX 660 **Blender Version** Broken: (example: 2.77.1 11b0874) Worked: (in 2.76 various versions) **Short description of error** When applying the normal edit modifier when rendering in Blender Internal it produces a jagged edge where the normal edit modifier has been applied. There is also a weird view in the viewport but I could not reproduce this in the startup file. See images the jaw line has the jagged edge: ![normaleditmodifier.jpg](https://archive.blender.org/developer/F315779/normaleditmodifier.jpg) See the facebook post for things we already tried to counter this effect: https://www.facebook.com/groups/BNPRandFreestyle/permalink/1180238755332559/ **Exact steps for others to reproduce the error** this could also be reproduced by using a start up file of susanne and applying the normal edit without any material applied to it. [normaleditmodifier.blend](https://archive.blender.org/developer/F315781/normaleditmodifier.blend)

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @WasiliNovratidis-1

Added subscriber: @WasiliNovratidis-1

Added subscriber: @mont29

Added subscriber: @mont29

This is not a bug actually. Issue here is that your are pushing normals way out of the 'safe area', making many of them reversed compared to default ones (computed from neighbor face normals).

Up till 2.76, Blender did not handle correctly that 'inversion of normals', leaving face normals opposed to its vertices ones, which was really bad and inconsistent. Since 2.77, winding of such faces is now reversed, to make face normal match the direction of its vertices ones.

In your example .blend, several faces are 'reversed' that way, producing the black patches. I’ll commit soon a new setting to the modifier allowing to limit the maximum angle between original and new normals, keeping this below 90° should help prevent most of those face normals inversions.

Editing normals in such an aggressive way also raises another issue, present since the beginning, which is it makes the terminator problem much more visible. Nothing to be done here really, you have to handle it yourself I’m afraid.

This is not a bug actually. Issue here is that your are pushing normals way out of the 'safe area', making many of them reversed compared to default ones (computed from neighbor face normals). Up till 2.76, Blender did not handle correctly that 'inversion of normals', leaving *face* normals opposed to its vertices ones, which was really bad and inconsistent. Since 2.77, winding of such faces is now reversed, to make face normal match the direction of its vertices ones. In your example .blend, several faces are 'reversed' that way, producing the black patches. I’ll commit soon a new setting to the modifier allowing to limit the maximum angle between original and new normals, keeping this below 90° should help prevent most of those face normals inversions. Editing normals in such an aggressive way also raises another issue, present since the beginning, which is it makes the terminator problem much more visible. Nothing to be done here really, you have to handle it yourself I’m afraid.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2016-06-06 21:43:28 +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
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#48576
No description provided.