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
- Dynamic Clipping works poorly with large scenes / terrains with the pivot point is near
- [UWP] Deploying wrong architecture through device portal ends up running a different app
- [MacOS] Standalone build contains .meta files inside native plugin bundles
- Progressive lightmapper leaks memory upon subsequent scene switches and bakes
- [AssetBundle] "The referenced script (Unknown) on this Behaviour is missing!" errors when loading object from Asset Bundle
Resolution Note (fix version ):
Probe discrepancies should be addressed by the upcoming probe sample count, and GPU and CPU PLM sampling unification PRs.