Search Issue Tracker
Fixed
Fixed in 6000.1.9f1, 6000.2.0b7, 6000.3.0a1, 7000.0.0a35
Votes
9
Found in
6000.1.1f1
6000.2.0a10
Issue ID
UUM-104391
Regression
Yes
Lights are being culled and appear pixelated when the "Main Light" property is disabled and Forward+ or Deferred+ Rendering Paths are used
Reproduction steps:
1. Open the attached “IN-99511.zip” project
2. Open the “SampleScene”
3. In the Scene view, zoom into the Light and move around
4. Observe the Light
Expected result: The Light is not cut off/culled and is normal quality
Actual result: The Light is cut/culled in certain places and is rendered very pixelated
Reproducible with: 6000.1.0a9 (381446a47f4e), 6000.1.1f1, 6000.2.0a10
Not reproducible with: 2022.3.62f1, 6000.0.48f1, 6000.1.0a8
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Affects both Point and Spot lights
- Could not observe the culling/cutting of in the Game view or the Player, but the pixelation is present both in the Game view and the Player
- Does not reproduce with Forward or Deferred Rendering Paths
- The “Main Light” property is located on the “PC_RPAsset” asset, under Lighting tab
Comments (3)
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
Krivodeling
Jun 11, 2025 16:55
I have to switch to Unreal because of this bug.
dispatch_starlost
Jun 05, 2025 23:38
This bug is stopping us from shipping a product update, we'll have to roll back to an earlier version just for this bug
CELL9
May 13, 2025 16:48
I have the culling bug since upgrading my project from 6000.0.32f1 to 6000.1.2f1. In my case, having one point light in the scene, and looking directly at it in game view and rotating the camera causes it to turn off and on in certain angles, the lower the cameras near clipping plane, the worse it gets. Increasing it to >=1, or changing to forward rendering path fixes it, but that is not an acceptable solution.