The shadow line is jagged in Cycles #77375

Closed
opened 2020-06-04 15:31:53 +02:00 by Fei Bao · 14 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75

Blender Version
Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: 211b6c29f7
Worked: (newest version of Blender that worked as expected)

Short description of error
Eevee vs Cycles (Shade smooth is activated).
It's been there for a long time.
image.png image.png

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75 **Blender Version** Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: `211b6c29f7` Worked: (newest version of Blender that worked as expected) **Short description of error** Eevee vs Cycles (Shade smooth is activated). It's been there for a long time. ![image.png](https://archive.blender.org/developer/F8576673/image.png) ![image.png](https://archive.blender.org/developer/F8576671/image.png) **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)]
Author

Added subscriber: @bao007fei

Added subscriber: @bao007fei

Added subscriber: @NXSK

Added subscriber: @NXSK

I have the same issue

shading issue.jpg

The sphere is subdivided by 10 times from a primitive cube and shaded smooth.
The lighting is very simple, just a HDR image.
But I still can see the light transition breaks between faces.

I have the same issue ![shading issue.jpg](https://archive.blender.org/developer/F8576718/shading_issue.jpg) The sphere is subdivided by 10 times from a primitive cube and shaded smooth. The lighting is very simple, just a HDR image. But I still can see the light transition breaks between faces.

Added subscriber: @rjg

Added subscriber: @rjg

This looks like the shadow terminator problem to me. In 2.90 there will be an option to shift the terminator towards the light source, hiding the artifacts at the cost of energy conservation. See c7280ce65b and D7634

This looks like the shadow terminator problem to me. In 2.90 there will be an option to shift the terminator towards the light source, hiding the artifacts at the cost of energy conservation. See c7280ce65b and [D7634](https://archive.blender.org/developer/D7634)
Author

@NXSK
untitled.png Only one HDR image for light, primitive sphere with smooth shade, looks fine.
image.png Make sure to use Catmull-Clark type instead of Simple type.

@NXSK ![untitled.png](https://archive.blender.org/developer/F8576768/untitled.png) Only one HDR image for light, primitive sphere with smooth shade, looks fine. ![image.png](https://archive.blender.org/developer/F8576774/image.png) Make sure to use Catmull-Clark type instead of Simple type.

In #77375#944922, @bao007fei wrote:
@NXSK
untitled.png Only one HDR image for light, primitive sphere with smooth shade, looks fine.
image.png Make sure to use Catmull-Clark type instead of Simple type.

No. This is nothing to do with the subdivision surface modifier. If the normal is smoothed, the shading from viewer angle should be smooth, without any light breakups.

I think it might be the problem that robert says. And this issue might be there for a long time.

> In #77375#944922, @bao007fei wrote: > @NXSK > ![untitled.png](https://archive.blender.org/developer/F8576768/untitled.png) Only one HDR image for light, primitive sphere with smooth shade, looks fine. > ![image.png](https://archive.blender.org/developer/F8576774/image.png) Make sure to use Catmull-Clark type instead of Simple type. No. This is nothing to do with the subdivision surface modifier. If the normal is smoothed, the shading from viewer angle should be smooth, without any light breakups. I think it might be the problem that robert says. And this issue might be there for a long time.
Author

In #77375#944924, @NXSK wrote:

In #77375#944922, @bao007fei wrote:
@NXSK
untitled.png Only one HDR image for light, primitive sphere with smooth shade, looks fine.
image.png Make sure to use Catmull-Clark type instead of Simple type.

No. This is nothing to do with the subdivision surface modifier. If the normal is smoothed, the shading from viewer angle should be smooth, without any light breakups.

I think it might be the problem that robert says. And this issue might be there for a long time.

For your situation, only one HDR for light. I tried and didn't see any light break problem. Maybe the texture is not perfectly seamless?
For me it only appears for built-in lights with low subdivision geometry.

> In #77375#944924, @NXSK wrote: >> In #77375#944922, @bao007fei wrote: >> @NXSK >> ![untitled.png](https://archive.blender.org/developer/F8576768/untitled.png) Only one HDR image for light, primitive sphere with smooth shade, looks fine. >> ![image.png](https://archive.blender.org/developer/F8576774/image.png) Make sure to use Catmull-Clark type instead of Simple type. > > No. This is nothing to do with the subdivision surface modifier. If the normal is smoothed, the shading from viewer angle should be smooth, without any light breakups. > > I think it might be the problem that robert says. And this issue might be there for a long time. For your situation, only one HDR for light. I tried and didn't see any light break problem. Maybe the texture is not perfectly seamless? For me it only appears for built-in lights with low subdivision geometry.
Author

In #77375#944920, @rjg wrote:
This looks like the shadow terminator problem to me. In 2.90 there will be an option to shift the terminator towards the light source, hiding the artifacts at the cost of realism and lack of energy conservation. See c7280ce65b and D7634

Good to know, Thanks:D

Hope it can be fixed completely someday without any extra options and costs.

> In #77375#944920, @rjg wrote: > This looks like the shadow terminator problem to me. In 2.90 there will be an option to shift the terminator towards the light source, hiding the artifacts at the cost of realism and lack of energy conservation. See c7280ce65b and [D7634](https://archive.blender.org/developer/D7634) Good to know, Thanks:D Hope it can be fixed completely someday without any extra options and costs.

In #77375#944956, @bao007fei wrote:

In #77375#944924, @NXSK wrote:

In #77375#944922, @bao007fei wrote:
@NXSK
untitled.png Only one HDR image for light, primitive sphere with smooth shade, looks fine.
image.png Make sure to use Catmull-Clark type instead of Simple type.

No. This is nothing to do with the subdivision surface modifier. If the normal is smoothed, the shading from viewer angle should be smooth, without any light breakups.

I think it might be the problem that robert says. And this issue might be there for a long time.

For your situation, only one HDR for light. I tried and don't see any light break problem. Maybe the texture is not perfectly seamless?
For me it only appear for built-in lights with low subdivision geometry.

My texture is procedual. Some simple material won't show this issue.

And I'm curious about my previous work: a game flash light with low poly counts. Without normal map it still looks fine. But a sphere with a procedual carbon weave, it looks ugly, even if it is subdivided, just the jagged "teeth" becomes denser.

I asked my friends about this issue. They say Radeon Prorender and Octane render have the same issue. I think this might be the problem of path tracing shading algorithm.

> In #77375#944956, @bao007fei wrote: >> In #77375#944924, @NXSK wrote: >>> In #77375#944922, @bao007fei wrote: >>> @NXSK >>> ![untitled.png](https://archive.blender.org/developer/F8576768/untitled.png) Only one HDR image for light, primitive sphere with smooth shade, looks fine. >>> ![image.png](https://archive.blender.org/developer/F8576774/image.png) Make sure to use Catmull-Clark type instead of Simple type. >> >> No. This is nothing to do with the subdivision surface modifier. If the normal is smoothed, the shading from viewer angle should be smooth, without any light breakups. >> >> I think it might be the problem that robert says. And this issue might be there for a long time. > > For your situation, only one HDR for light. I tried and don't see any light break problem. Maybe the texture is not perfectly seamless? > For me it only appear for built-in lights with low subdivision geometry. My texture is procedual. Some simple material won't show this issue. And I'm curious about my previous work: a game flash light with low poly counts. Without normal map it still looks fine. But a sphere with a procedual carbon weave, it looks ugly, even if it is subdivided, just the jagged "teeth" becomes denser. I asked my friends about this issue. They say Radeon Prorender and Octane render have the same issue. I think this might be the problem of path tracing shading algorithm.
Author

In #77375#944967, @NXSK wrote:

In #77375#944956, @bao007fei wrote:

In #77375#944924, @NXSK wrote:

In #77375#944922, @bao007fei wrote:
@NXSK
untitled.png Only one HDR image for light, primitive sphere with smooth shade, looks fine.
image.png Make sure to use Catmull-Clark type instead of Simple type.

No. This is nothing to do with the subdivision surface modifier. If the normal is smoothed, the shading from viewer angle should be smooth, without any light breakups.

I think it might be the problem that robert says. And this issue might be there for a long time.

For your situation, only one HDR for light. I tried and don't see any light break problem. Maybe the texture is not perfectly seamless?
For me it only appear for built-in lights with low subdivision geometry.

My texture is procedual. Some simple material won't show this issue.

And I'm curious about my previous work: a game flash light with low poly counts. Without normal map it still looks fine. But a sphere with a procedual carbon weave, it looks ugly, even if it is subdivided, just the jagged "teeth" becomes denser.

I asked my friends about this issue. They say Radeon Prorender and Octane render have the same issue. I think this might be the problem of path tracing shading algorithm.

I've never seen this problem beyond Cycles. Really weird.

> In #77375#944967, @NXSK wrote: >> In #77375#944956, @bao007fei wrote: >>> In #77375#944924, @NXSK wrote: >>>> In #77375#944922, @bao007fei wrote: >>>> @NXSK >>>> ![untitled.png](https://archive.blender.org/developer/F8576768/untitled.png) Only one HDR image for light, primitive sphere with smooth shade, looks fine. >>>> ![image.png](https://archive.blender.org/developer/F8576774/image.png) Make sure to use Catmull-Clark type instead of Simple type. >>> >>> No. This is nothing to do with the subdivision surface modifier. If the normal is smoothed, the shading from viewer angle should be smooth, without any light breakups. >>> >>> I think it might be the problem that robert says. And this issue might be there for a long time. >> >> For your situation, only one HDR for light. I tried and don't see any light break problem. Maybe the texture is not perfectly seamless? >> For me it only appear for built-in lights with low subdivision geometry. > > My texture is procedual. Some simple material won't show this issue. > > And I'm curious about my previous work: a game flash light with low poly counts. Without normal map it still looks fine. But a sphere with a procedual carbon weave, it looks ugly, even if it is subdivided, just the jagged "teeth" becomes denser. > > I asked my friends about this issue. They say Radeon Prorender and Octane render have the same issue. I think this might be the problem of path tracing shading algorithm. I've never seen this problem beyond Cycles. Really weird.

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
Brecht Van Lommel self-assigned this 2020-06-04 17:29:27 +02:00

The task for this is #68920 (Cycles: improve shadow terminator handling).

The task for this is #68920 (Cycles: improve shadow terminator handling).
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#77375
No description provided.