Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.4
2019.4.1f1
2020.2
Issue ID
1271277
Regression
No
[PLM] Overlapping spotlights are not baked
How to reproduce:
1. Open "Test2019.zip" project and SampleScene
2. Select the second "Spot light" GameObject in the Hierarchy window
3. Toggle it on and off
4. Notice, how it is rendered as a realtime light
Notes:
- Reproducible with: 2018.4.26f1, 2019.4.9f1, 2020.1.3f1, 2020.2.0a21
- Affects CPU PLM, GPU PLM, and Enlighten
- Reproduces on all render pipelines
- Clearing baked data and rebaking yields the same result
- Only spotlights are affected; they need to have identical settings and share the same transform coordinate for the issue to reproduce
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
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [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
Resolution Note (2020.2.X):
This issue requires a larger refactor and development will be scheduled as part of our regular sprints.