Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Fixed in 6000.0.1f1
Votes
2
Found in
2021.3.32f1
2022.3.13f1
2023.1.20f1
2023.2.0b17
2023.3.0a14
6000.0.0b11
Issue ID
UUM-56213
Regression
No
The Realtime Point Lights are casting shadows non-dependant on the surrounding GameObjects when the Camera is being moved around the Scene
How to reproduce:
1. Open the “TestPointLightRepro“ project
2. Open the “ReproScene“
3. Open the “Window > Sequencing > Timeline“
4. In the Timeline window open the “CameraTimeline.playable“
5. Play the Timeline
6. Observe the shadows cast by the Point Lights in the Scene
Expected result: The shadows are not cast when the Point Light has no GameObjects around it
Actual result: The shadows are cast even when the Point Light has no GameObjects around it
Reproducible with: 2021.3.32f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0b17, 2023.3.0a14
Reproducible on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Notes:
- Reproducible in Player
- Also reproducible in the Play mode
- When toggling the visibility of the “BreakingLights“ GameObject (which consists of 3 more Point Lights) off, the shadows of the Point Lights are behaving correctly
- Also reproducible when moving around the Scene with the Orbit View tool in the Scene view
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
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
Resolution Note (fix version 6000.0.1f1):
The user is hitting the limit in the number of shadow casting point lights for the given shadow map atlas size. The bug is that we were not printing a warning about this, so my PR is fixing this. The warning now informs the user how to resolve the issue.