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.3
Issue ID
1145500
Regression
No
Light probe discrepancies between CPU PLM and GPU PLM
Steps to reproduce:
1. Download SponzaLegacy project
2. Make sure that light probe gizmos are enabled
3. Bake the lighting using CPU PLM and take note of the light probe appearance
4. Now bake the lighting using GPU PLM
5. Notice that light probes look different
Notes:
- Reproduces on all versions of Unity since GPU PLM was introduced
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
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
Resolution Note:
Probe discrepancies should be addressed by the upcoming probe sample count, and GPU and CPU PLM sampling unification PRs.