Search Issue Tracker
Feature Request
Votes
0
Found in
2021.3.40f1
2022.3.35f1
Issue ID
UUM-74918
Regression
No
Visual Effect's Alpha Clipping is missing for shadows when a corrupted Shader Graph is used
Reproduction steps:
1. Open the attached “IN-78720_CorruptedSG.zip” project
2. Open the “SampleScene”
3. Observe the Scene view
Expected result: The “Fire” Visual Effect’s shadow takes into account ShaderGraph’s Alpha Clipping
Actual result: The “Fire” Visual Effect’s shadow does not respect ShaderGraph’s Alpha Clipping
Reproducible with: 2021.3.40f1, 2022.3.35f1, 2023.3.0a16
Not reproducible with: 6000.0.8f1
Fixed in: 2023.3.0a17
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Also reproducible in Player
- In 2023.3.0a17 or higher, converting the “Output Particle Quad” to “Output Particle ShaderGraph” solves the issue
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
Resolution Note:
This is a side effect of the unsupported shader keyword with ShaderGraph in Visual Effect Graph.
The support was only made available in 2023.3a17 and greater and won't be backported.
Before this version, the usage of Shader Keyword led to only a warning which should probably be considered an error
"(Keyword) blackboard properties in Shader Graph are currently not supported in Visual Effect shaders. Falling back to default generation path."
To fix this side effect, we recommend removing the shader keyword from the ShaderGraph blackboard.