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

New Issue

MACHIN3 · 2019-05-20T15:30:53+02:00

MACHIN3 commented

2019-05-20 15:30:53 +02:00

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.

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.

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

MACHIN3 commented

2019-05-20 15:30:53 +02:00

Added subscriber: @MACHIN3

MACHIN3 commented

2019-05-20 15:31:30 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-05-20 18:51:11 +02:00

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.

MACHIN3 commented

2019-05-20 19:01:13 +02:00

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

2019-05-20 19:03:14 +02:00

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

2019-05-20 19:05:15 +02:00

Clément Foucault was assigned by Brecht Van Lommel

2019-05-20 19:42:19 +02:00

Brecht Van Lommel commented

2019-05-20 19:46:20 +02:00

@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 Van Lommel 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

2019-05-21 08:58:37 +02:00

MACHIN3 commented

2019-05-21 09:37:33 +02:00

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.

Clément Foucault commented

2019-05-23 14:40:08 +02:00

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.

Clément Foucault commented

2019-05-23 14:40:16 +02:00

Changed status from 'Open' to: 'Resolved'

Clément Foucault closed this issue

2019-05-23 14:40:16 +02:00

Sign in to join this conversation.