Eevee principled BSDF SSS not mixing correctly with transparent BSDF #64883

Closed
opened 4 years ago by MACHIN3 · 8 comments

System Information
Operating system: Linux-4.13.10-041310-generic-x86_64-with-debian-stretch-sid 64 Bits
Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.67

Blender Version
Broken: version: 2.80 (sub 70), branch: master, commit date: 2019-05-20 06:52, hash: f606f58845

Short description of error
This is a follow up to #64762 , so I think @brecht might want to take a look at this.
The problem is a bit hard to pin point, but there still seem to be a problem with linear interpolation of alpha mapped normal maps. This time they are only triggered when a value node, specifically with a value of 0, is used as the input for either Subsurface, Clearcoat or Transmission on the Principled PBR node.
When the value node is muted, or the connections are cut, the issue is gone. That is despite the fact, that the values on the Principled node are the same, as the value coming from the input node.

interpolation_issue_with_transparenct_shader.jpg

There is another, perhaps related, darkening issue. If instead of using the transparent shader to mask the object, the alpha inputof the Principled PBR node is use, the entere material darkens.
This again is triggered by the Subsurface, Clearcoat or Transmission inputs, and vanishes when the value node is muted or the connections are cut.

darkness_issue_with_principled_shaders_alpha_input.jpg

I also think this only happens for non-metallic materials, but I'm not sure.

Please check out the video demo for clarity.

linear_interpolation_of_alpha_mapped_normal_map2.blend

Exact steps for others to reproduce the error

  • open the blend file above
  • notice - what appears like - interpolation issues on the transparent border
  • mute or disconnect the value node, feeding a value of 0 to subsurface, clearcoat and transmission
    • the issue should be gone, but note that the input values are the same as before
  • unmute/reconnect the value node
  • feed the Principled output directly Material Output, to use the shaders own alpha input in favor of the Transparent and Mix shaders
    • now the entire material should darken
    • mute or disconnect value node again, and the material will behave as expected
**System Information** Operating system: Linux-4.13.10-041310-generic-x86_64-with-debian-stretch-sid 64 Bits Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.67 **Blender Version** Broken: version: 2.80 (sub 70), branch: master, commit date: 2019-05-20 06:52, hash: `f606f58845` **Short description of error** This is a follow up to [#64762 ](https://developer.blender.org/T64762), so I think @brecht might want to take a look at this. The problem is a bit hard to pin point, but there still seem to be a problem with linear interpolation of alpha mapped normal maps. This time they are only triggered when a value node, specifically with a value of 0, is used as the input for **either** Subsurface, Clearcoat or Transmission on the Principled PBR node. When the value node is muted, or the connections are cut, the issue is gone. That is despite the fact, that the values on the Principled node are the same, as the value coming from the input node. ![interpolation_issue_with_transparenct_shader.jpg](https://archive.blender.org/developer/F7050891/interpolation_issue_with_transparenct_shader.jpg) There is another, perhaps related, darkening issue. If instead of using the transparent shader to mask the object, the alpha inputof the Principled PBR node is use, the entere material darkens. This again is triggered by the Subsurface, Clearcoat or Transmission inputs, and vanishes when the value node is muted or the connections are cut. ![darkness_issue_with_principled_shaders_alpha_input.jpg](https://archive.blender.org/developer/F7050902/darkness_issue_with_principled_shaders_alpha_input.jpg) I also think this only happens for non-metallic materials, but I'm not sure. Please check out the [video demo ](https://www.youtube.com/watch?v=__NbVnvmhyM) for clarity. [linear_interpolation_of_alpha_mapped_normal_map2.blend](https://archive.blender.org/developer/F7050791/linear_interpolation_of_alpha_mapped_normal_map2.blend) **Exact steps for others to reproduce the error** * open the blend file above * notice - what appears like - interpolation issues on the transparent border * mute or disconnect the value node, feeding a value of 0 to subsurface, clearcoat and transmission * the issue should be gone, but note that the input values are the same as before * unmute/reconnect the value node * feed the Principled output directly Material Output, to use the shaders own alpha input in favor of the Transparent and Mix shaders * now the entire material should darken * mute or disconnect value node again, and the material will behave as expected
Poster

Added subscriber: @MACHIN3

Added subscriber: @MACHIN3
Poster

Added subscriber: @brecht

Added subscriber: @brecht
brecht commented 4 years ago
Owner

There is indeed something weird going on with Eevee, normally plugging in a Value node or setting the value directly should make no difference.

As far as I can tell, this is unrelated to the normal map as unplugging it gives the same dark border. It is also not clear what the purpose is of using alpha twice in the shader node setup, as using the Alpha socket means it's already mixing with a Transparent BSDF internally.

There is indeed something weird going on with Eevee, normally plugging in a Value node or setting the value directly should make no difference. As far as I can tell, this is unrelated to the normal map as unplugging it gives the same dark border. It is also not clear what the purpose is of using alpha twice in the shader node setup, as using the Alpha socket means it's already mixing with a Transparent BSDF internally.
Poster

It is also not clear what the purpose is of using alpha twice in the shader node setup, as using the Alpha socket means it's already mixing with a Transparent BSDF internally.

This is really just my old setup of using the transparecny shader, and then quickly switching it over to the Alpha input. I plan to get rid of the transparent shader, but left it in because it somehow produces a different result.

You are right, it is unrelated to the normal map. I'm updating the title.

> It is also not clear what the purpose is of using alpha twice in the shader node setup, as using the Alpha socket means it's already mixing with a Transparent BSDF internally. This is really just my old setup of using the transparecny shader, and then quickly switching it over to the Alpha input. I plan to get rid of the transparent shader, but left it in because it somehow produces a different result. You are right, it is unrelated to the normal map. I'm updating the title.
MACHIN3 changed title from linear interpolation + darkness issues with alpha mapped normal maps and the principled BSDF shader to linear interpolation + darkness issues with alpha masked principled BSDF shader 4 years ago
MACHIN3 changed title from linear interpolation + darkness issues with alpha masked principled BSDF shader to linear interpolation + darkness issues with alpha masked principled BSDF shader + Subsurface, Clearcoat and Transmission inputs 4 years ago
fclem was assigned by brecht 4 years ago
brecht commented 4 years ago
Owner

@fclem, I think this one is for you.

Here's an example file, unplugging the Value node from Subsurface avoids the black border.
eevee_sss_transparent.blend

For some reason, the subsurface (and some other) variations of the principled BSDF are not working well when mixed with a Transparent BSDF. This happens without using the new Alpha socket.

@fclem, I think this one is for you. Here's an example file, unplugging the Value node from Subsurface avoids the black border. [eevee_sss_transparent.blend](https://archive.blender.org/developer/F7052029/eevee_sss_transparent.blend) For some reason, the subsurface (and some other) variations of the principled BSDF are not working well when mixed with a Transparent BSDF. This happens without using the new Alpha socket.
brecht changed title from linear interpolation + darkness issues with alpha masked principled BSDF shader + Subsurface, Clearcoat and Transmission inputs to Eevee principled BSDF SSS not mixing correctly with transparent BSDF 4 years ago
Poster

eevee_clearcoat_alpha.blend

In an attempt to avoid it being overlooked, I want to point out, that it's not just Subsurface, but also Clear Coat and Transmission causing this. Also, as you can see in the file attached, there is an issue with the Alpha input as well, which leads to darkening of the material.

[eevee_clearcoat_alpha.blend](https://archive.blender.org/developer/F7055381/eevee_clearcoat_alpha.blend) In an attempt to avoid it being overlooked, I want to point out, that it's not just Subsurface, but also Clear Coat and Transmission causing this. Also, as you can see in the file attached, there is an issue with the Alpha input as well, which leads to darkening of the material.
fclem commented 4 years ago
Collaborator

Fixed by df7f69b873.

The only issue then is that the normal map is not in linear mode.

Fixed by df7f69b873. The only issue then is that the normal map is not in linear mode.
fclem commented 4 years ago
Collaborator

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
fclem closed this issue 4 years ago
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#64883
Loading…
There is no content yet.