Search Issue Tracker
By Design
Votes
0
Found in
2021.2
2021.2.12f1
2022.1
2022.2
Issue ID
1407538
Regression
No
GameObject light limits are affected by non-effective Light Layer
How to reproduce:
1. Open the user's attached project
2. Open scene Scenes/BreakLightLayers
3. In the Hierarchy window, double-click the GameObject "Sphere (1)"
4. Observe the four Spheres with reflecting red Point Lights in the Scene view
5. In the Hierarchy window, select the GameObject "DirectionalLightOnLightLayerNothing"
6. In the Inspector view, enable the GameObject by checking the box next to its name
7. Observe the same Spheres in the Scene view
Expected result: red Point Lights continue to reflect on the Spheres
Actual result: red Point Lights no longer reflect on the Spheres
Reproducible with: 12.1.5 (2021.2.14f1), 13.1.6 (2022.1.0b10), 14.0.0 (2022.2.0a7)
Could not test with: 7.7.1 (2019.4.36f1), 10.8.1 (Light Layers not available)
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
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
- Crash on invalid_parameter_internal when starting Standalone Profiler
Resolution Note (2022.2.X):
This is known limitation in forward rendering path with light layers. This will be solved in the future with Forward+.