Search Issue Tracker
Fixed
Fixed in 2022.3.12f1, 2023.1.13f1, 2023.2.0b7, 2023.3.0a1
Votes
0
Found in
2021.3.27f1
2022.3.3f1
2023.1.1f1
2023.2.0a21
2023.3.0a1
Issue ID
UUM-40810
Regression
No
LightLayer is not working as expected when additional lights are set on "Per Vertex"
Reproduction steps:
1. Open attached project "Light Layers.zip"
2. Open Assets > Scene > SampleScene
3. Select Assets > Settings > UniversalRP-HighQuality.asset
4. In the Inspector right click “Lighting” and select “Show Additional Properties”
5. Enable “Use Rendering Layers”
6. Switch Lighting > Additional Light > “Per Vertex” to “Per Pixel”
7. Observe Scene view
8. Switch back “Per Pixel” to “Per Vertex”
9. Observe Scene view
Expected result: “Stud Frame” is not illuminated
Actual result: “Stud Frame” is illuminated
Reproduced with: 2021.3.27f1, 2022.3.3f1, 2023.1.1f1, 2023.2.0a21
Reproducible on: macOS 13.3.1 (Intel), macOS 13.0 (M1)
Note: Also reproduced in Player
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment