Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
0
Found in
2020.1
Issue ID
1198078
Regression
No
[GI - Lightmapper] Invalid texels are not treated the same way in CPU and GPU lightmapper
Invalid texels are not treated the same way in CPU and GPU lightmapper:
When a ray (launched by lightmapper baking) hit a backface we increment a invalid texel counter. In the compositing stage we then try to fix invalid texels.
The bug is that we do not have the same behavior between CPU and GPU lightmappers.
From what I saw in the attached repro project:
-GPULM tries to filter invalid texels with neighboors valid ones hence the distorted shadow.
-CPULM doesn't seem to do anything with it.
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
Add comment