Search Issue Tracker
By Design
Votes
1
Found in
2018.1.0b10
2018.1.0b13
Issue ID
1021816
Regression
No
Faulty overlapping lightmap UV warnings with non-overlapping UV2 channel UVs
Issue:
Unity posts warning messages to the console about UV Overlap even though my models do not have overlaps in their UVs.
Resolution:
This is most likely the intended behaviour of Unity. The "overlap" that Unity is referring to is not "chart overlap in UV space". Instead, it is the "chart bilinear neighbourhood overlap in lightmap space". In other words, Unity detects an overlap whenever texels in two lightmap charts are sufficiently close to each other to affect each other's bilinear sample values. In such cases colors from one chart may "bleed" into another.
Because this distinction is so subtle, we wrote a docs page about this:
https://docs.unity3d.com/Documentation/Manual/ProgressiveLightmapper-UVOverlap.html
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment