EEVEE-Next: Subsurface material disapear if Raytraced Transmission is turned on #121667

Closed
opened 2024-05-10 19:41:01 +02:00 by Clément Foucault · 1 comment

Happens only in a certain specific configuration.

Openning the file should exhibit the issue.

This happens only if the second object doesn't enabled Raytraced Transmission.

Might be caused by the optimization inside can_use_default_cb.

Happens only in a certain specific configuration. Openning the file should exhibit the issue. This happens only if the second object doesn't enabled `Raytraced Transmission`. Might be caused by the optimization inside `can_use_default_cb`.
Clément Foucault added this to the 4.2 LTS milestone 2024-05-10 19:41:01 +02:00
Clément Foucault added the
Interest
EEVEE
Status
Confirmed
Type
Report
Priority
High
labels 2024-05-10 19:41:02 +02:00
Iliya Katushenock added the
Module
EEVEE & Viewport
label 2024-05-10 19:42:10 +02:00
Contributor

I did a little bit of investigation on this issue.

Depending on can_use_default_cb result some materials might be replaced with default for shadow and prepass subpasses.
Down the line these end up in different layers of DeferredPipeline, respectively opaque_layer_ or refraction_layer_.
At the end only one of these layers is actually rendered (Renderdoc shows one of them empty).

Which layer is rendered seems to be related to whichever of the materials gets first to the rendering.
I have attached simple scene with few cubes and alternating Raytraced Transmission settings. You can try to toggle Hide in Viewport on the first (left most) cube to see the effect - either all "regular" materials are rendered or all "ray-traced". But never both.

Technically there is hard check closure_count_ == 0 inside each layer which prevents it from rendering.
But I was not able to comprehend why it ends up 0 on one or another layer.

Hope this will be helpful.

I did a little bit of investigation on this issue. Depending on `can_use_default_cb` result some materials might be replaced with _default_ for `shadow` and `prepass` subpasses. Down the line these end up in different layers of `DeferredPipeline`, respectively `opaque_layer_` or `refraction_layer_`. At the end only one of these layers is actually rendered (Renderdoc shows one of them empty). Which layer is rendered seems to be related to whichever of the materials gets first to the rendering. I have attached simple scene with few cubes and alternating `Raytraced Transmission` settings. You can try to toggle `Hide in Viewport` on the first (left most) cube to see the effect - either all "regular" materials are rendered or all "ray-traced". But never both. Technically there is hard check `closure_count_ == 0` inside each layer which prevents it from rendering. But I was not able to comprehend why it ends up `0` on one or another layer. Hope this will be helpful.
Blender Bot added
Status
Resolved
and removed
Status
Confirmed
labels 2024-05-15 20:06:46 +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#121667
No description provided.