Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2021.2.X
Votes
0
Found in
2019.4
2021.2
Issue ID
1337226
Regression
No
[LightProbes] Corruption in Probe baking when lightmap UVs are not provided.
Gif showing the problem.
https://imgur.com/W19AYv7.gif
1) Open the sample scene
2) Generate lighting
3) Goto lightmap debug scene mode (its easier to view the problem here)
4) See probes are not white despite strong sun lighting
5) Select Assets/Meshes/box01 import settings
6) Click Generate Lightmap UVs
7) Click Apply
8) Generate lighting
9) Observe that lightprobes are now correctly lit
Observed: Lightprobes are not correctly lit when contributing meshes do not have lightmapping UVs
Expected: Lightprobes are correctly lit with contributing meshes regardless of UVs
Notes: Reproduces on CPU and GPU Lightmappers.
Seen in 2021.2.0a18
Found by @julien while working on APV: see thread here: https://unity.slack.com/archives/C06TQ5M4J/p1621266271376200
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment