Search Issue Tracker
Won't Fix
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
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.