Tangent shader - shadow biases badly #17899

Closed
opened 2008-10-24 19:34:33 +02:00 by Tommy Helgevold · 8 comments

%%%Machine: Hewlett packard Pavilion 6133sc
Processor: Q6600 - 2.4 Ghz Core 2 Duo Quad
Ram: 8 GB
OS: Ubuntu Linux 8.04 - latest updates - 64 bit.
Blender: 2.48a SVN

Problem:
Severe render artifacts using the TANGENT Shading option,
especially with rounded, smoothed bevels. Creates some
sort of zig-zag bounce pattern that is impossible to "bias" or
"ajust" away, no matter what shader used.

Please see included example on image (top of pot)
Also - please render closeups of the top corner of the pot (furthest
away, just zoom in on the included blend file - and render) and
the bug becomes even more apparent.

Problem 2:
There are also some ray shadow biasing issues (look at the blocky
shadows in the image example), Biassing has been used - and turned on
but to no effect.

%%%

%%%Machine: Hewlett packard Pavilion 6133sc Processor: Q6600 - 2.4 Ghz Core 2 Duo Quad Ram: 8 GB OS: Ubuntu Linux 8.04 - latest updates - 64 bit. Blender: 2.48a SVN Problem: Severe render artifacts using the TANGENT Shading option, especially with rounded, smoothed bevels. Creates some sort of zig-zag bounce pattern that is impossible to "bias" or "ajust" away, no matter what shader used. Please see included example on image (top of pot) Also - please render closeups of the top corner of the pot (furthest away, just zoom in on the included blend file - and render) and the bug becomes even more apparent. Problem 2: There are also some ray shadow biasing issues (look at the blocky shadows in the image example), Biassing has been used - and turned on but to no effect. %%%

Changed status to: 'Open'

Changed status to: 'Open'

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Member

%%%Workaround 1: As mentioned in the release notes, when there's no UV layout present, to calculate the tangents, Blender uses a default Sphere unwrap, which seems to perform badly on your model. I'd recommend unwrapping the pot manually, either trying a Sphere or Cylinder unwrap, or by controlling the layout yourself, using the other unwrap tools. At least here you have a lot of control over the direction of the anisotropic effect.

Workaround 2: Blender's current 'tangent' speculars are quite physically incorrect and them not working with ray shadows is a known issue, that I'm not sure if it's possible to resolve. Two possibilities could be to a) subdivide the mesh a lot so the blockiness goes away or b) don't use speculars, but actually add white emitting planes to the scene in place of your lamps, so the glossy anisotropic reflection can reflect it to make 'real' highlights.%%%

%%%Workaround 1: As mentioned in the release notes, when there's no UV layout present, to calculate the tangents, Blender uses a default Sphere unwrap, which seems to perform badly on your model. I'd recommend unwrapping the pot manually, either trying a Sphere or Cylinder unwrap, or by controlling the layout yourself, using the other unwrap tools. At least here you have a lot of control over the direction of the anisotropic effect. Workaround 2: Blender's current 'tangent' speculars are quite physically incorrect and them not working with ray shadows is a known issue, that I'm not sure if it's possible to resolve. Two possibilities could be to a) subdivide the mesh a lot so the blockiness goes away or b) don't use speculars, but actually add white emitting planes to the scene in place of your lamps, so the glossy anisotropic reflection can reflect it to make 'real' highlights.%%%
Member

%%%1) Yes, without UVs there's no direction info for the tangent, which is approximated then...

  1. The terminator problem still is a problem :( for regular diffuse/specular it's solvable, but for extreme cases you see the shadow (correctly) as it derives from the actual faces in geometry. Micropolygons don't solve this either btw, you always ray-trace on a more lower resolution mesh. The literature advises to add a ray-offset per material to shift the boundary, which is a hack too. Still a very interesting topic to look at once...%%%
%%%1) Yes, without UVs there's no direction info for the tangent, which is approximated then... 2) The terminator problem still is a problem :( for regular diffuse/specular it's solvable, but for extreme cases you see the shadow (correctly) as it derives from the actual faces in geometry. Micropolygons don't solve this either btw, you always ray-trace on a more lower resolution mesh. The literature advises to add a ray-offset per material to shift the boundary, which is a hack too. Still a very interesting topic to look at once...%%%

%%%1) Excellent - that solved that issue quickly and neatly.

  1. Not understood - are you saying I should render Raytraces separately with a lower resolution mesh? That's interesting, I gotta know how to do that little trick except making two separate renders.

That actually would count for an interesting feature (If it isn't there already) to render shadows on different SubSurf-levels! O_O.

%%%

%%%1) Excellent - that solved that issue quickly and neatly. 2) Not understood - are you saying I should render Raytraces separately with a lower resolution mesh? That's interesting, I gotta know how to do that little trick except making two separate renders. That actually would count for an interesting feature (If it isn't there already) to render shadows on different SubSurf-levels! O_O. %%%
Member

%%%The 2) was only a theoritical case, we don't have that feature :)%%%

%%%The 2) was only a theoritical case, we don't have that feature :)%%%
Member

%%%I posted a patch for this issue (Patch [#26632]). The patch should allow us to get much more physically accurate pictures.

Please check it.
%%%

%%%I posted a patch for this issue (Patch [#26632]). The patch should allow us to get much more physically accurate pictures. Please check it. %%%
Member

%%%Updated the patch [#26632].

Can anyone test it?
%%%

%%%Updated the patch [#26632]. Can anyone test 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
5 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#17899
No description provided.