Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.34f1
2022.3.17f1
2023.2.5f1
2023.3.0b1
Issue ID
UUM-60060
Regression
No
GameObject shadows disappear if the Rotation is 90 degrees and have a specific Scale value when the Directional Light Rotation is at 90 degrees
How to reproduce:
1. Open the user’s attached “ShadowsBugTest2023.zip” project
2. In the Hierarchy, select GameObjects with the “Bugged” name
3. In the Inspector window, slowly change their Scale value and observe the result
Expected result: GameObject has shadows with any Scale values
Actual result: GameObject doesn’t have shadows with specific Scale values
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.5f1, 2023.3.0b1
Reproduced on: macOS 13.6.3 (Intel)
Not reproducible on: No other environment tested
Notes:
- Reproducible with both both “Forward” and “Deferred” Rendering Paths
- Not reproducible on DirectX on Windows
- Reproducible on iOS
- In Frame Debugger, “Shadows.RenderShadowMap" shows that “Bugged” GameObjects are left out of the ShadowMap calculation entirely
- Not reproducible with URP
- Not reproducible if changing the Rotation of “Bugged” GameObjects to 90.1
- Not reproducible if changing the Rotation of “Directional Light” GameObject to 90.1
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.