Search Issue Tracker
By Design
Votes
0
Found in [Package]
6.9.1, 7.1.1
Issue ID
1186309
Regression
No
Shadows are not projected correctly when using Shadow Attenuation from Shadows.hlsl in a Custom Sub Graph Function
How to reproduce:
1. Download the tester-attached package(ShadowProjection.unitypackage)
2. Create a new Universal Render Pipeline project
3. Import the package and set the included Render Pipeline Asset
4. Open the Shadow Issues/3. Shadow Projection/Shadows Projection Scene
5. Compare the Simple Lit Shadows GameObject to Custom Shadows/Custom Shadows Without mask GameObjects
Expected result: Custom Shadows/Custom Shadows Without mask GameObjects have correct shadow projections
Actual result: Custom Shadows/Custom Shadows Without mask GameObjects have incorrect projections
Reproducible with: 2019.2.7f2, 2019.3.0b4, 2020.1.0a5
Could not test with: 2017.4.32f1(ShaderGraph unavailable), 2018.4.10f1(Shader incompatibility issues)
Reproducible with package versions: 6.9.1, 7.1.1
Could not test with package versions: 6.9.0(Shader Incompatibility issues)
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
- 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
Resolution Note:
The Position node in the Sub Graph was set to Object Space, which was causing the shadows to be projected incorrectly. Changing Space to World Space fixes the shadow projection