Search Issue Tracker
Fixed in 2022.3.18f1
Fixed in 2022.3.X, 2023.2.X, 2023.3.X, 2023.3.0b3
Votes
0
Found in
2022.3.18f1
2023.2.0f1
2023.3.0b3
Issue ID
UUM-59974
Regression
Yes
Keywords for SH and SoftShadows are incorrectly set up in ShaderGraph
Keywords for Evaluate SH and SoftShadows are incorrectly set up in ShaderGraph.
Instead of being:
{code:java}
#pragma multi_compile_fragment _ _SHADOWS_SOFT _SHADOWS_SOFT_LOW _SHADOWS_SOFT_MEDIUM _SHADOWS_SOFT_HIGH
#pragma multi_compile _ EVALUATE_SH_MIXED EVALUATE_SH_VERTEX
{code}
They are:
{code:java}
#pragma multi_compile_fragment _ _SHADOWS_SOFT
#pragma multi_compile_fragment _ _SHADOWS_SOFT_LOW
#pragma multi_compile_fragment _ _SHADOWS_SOFT_MEDIUM
#pragma multi_compile_fragment _ _SHADOWS_SOFT_HIGH
#pragma multi_compile _ EVALUATE_SH_MIXED
#pragma multi_compile _ EVALUATE_SH_VERTEX
{code}
This adds more variants than needed and breaks functionality with those features.
The regressions came from these PRs
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment