Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
1381357
Regression
No
[PLM] GPU and CPU Lightmappers produce inconsistent results
Steps to reproduce:
1. Open the attached repro project
2. Bake each of the four scenes under Assets/Scenes
3. Observe the different outputs (seen below as well)
Reproduces with 2020.3.22f1, 2021.2.0a14, 2022.1.0a14, 2022.1.0a15, 2022.1.0a16
Reproduced on Windows (DX11)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (2022.1.X):
The Light Probe Sample Multiplier behaves differently between the CPU and GPU, meaning that better and more similar results will be obtained with higher LPSM values. This difference is therefore marked as 'by Design'.