Search Issue Tracker
Fixed
Fixed in 6000.0.27f1, 6000.1.0a3, 7000.0.0a8
Votes
1
Found in
6000.0.21f1
6000.1.0a1
Issue ID
UUM-82787
Regression
Yes
2D Light overlap order is not evaluated when shadows are being produced with Render Graph Compatibility Mode Disabled
How to reproduce:
1. Open the attached “Light2D-OverlapOperationBug.zip” project
2. Make sure Render Graph Compatibility Mode is disabled (Project Settings > Graphics > Render Graph)
3. Open the “SampleScene”
4. Observe the Scene View
5. Disable the “orcSprite” GameObject
6. Observe the result
Expected result: Light overlap does not change when shadows are no longer being produced
Actual result: Light overlap order is different when shadows are being produced
Reproducible in: 2023.3.0a18, 6000.0.21f1
Not reproducible in 2021.3.44f1, 2022.3.48f1, 2023.3.0a17
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Notes:
- Moving the “orcSprite” GameObject out of the view and disabling the shadow component of the “SportLight2(green)_Shadows” GameObject can also be done instead of step 4 to reproduce the issue.
- Issue does not reproduce with Render Graph Compatibility Mode enabled
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