Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2022.3.49f1
6000.0.23f1
Issue ID
UUM-83709
Regression
No
Spot Light with 'Box' Shape stops working when it collides with Mesh
Reproduction steps:
1. Open the attached “IN-85612.zip” project
2. Open the “Title Screen Temple” Scene
3. Select the “Light” GameObject from the Hierarchy
4. Move its position on the X axis towards and away from the Mesh
Expected result: Light works when inside or collided with the Mesh
Actual result: Light stops working after it collides
Reproducible with: 2022.3.49f1, 6000.0.23f1
Couldn’t test with: 2021.3.44f1 (Lights did not work at all after downgrading)
Reproducible on: Windows 11
Not reproducible on: macOS 13 (M1)
Notes:
- Does not reproduce when ‘Cone’ or ‘Pyramid’ Shape is selected in the Light Component
- Could not reproduce on a new project
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
In the Spot Light (Temple Window object) settings, Emission's Range is 3.19, and Shadows' Near Plane is 5.57. If the Near Plane is set smaller than the Range, the light will render even when it collides with the mesh.
Resolution Note (6000.0.X):
In the Spot Light (Temple Window object) settings, Emission's Range is 3.19, and Shadows' Near Plane is 5.57. If the Near Plane is set smaller than the Range, the light will render even when it collides with the mesh.