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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment