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
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- [Linux] Numeric field value stops increasing when cursor reaches the edge of the monitor while dragging
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- "Add Component" button overlaps the Volume component UI when creating a new Volume Profile in a wide Inspector on high-DPI scaling
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Resolution Note:
Probe discrepancies should be addressed by the upcoming probe sample count, and GPU and CPU PLM sampling unification PRs.