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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment