Search Issue Tracker
Fixed
Votes
0
Found in
Issue ID
474781
Regression
No
Check for overlapping triangles in the unwrap when importing the mesh
Since the lightmapper can give quite unexpected results when the triangles in the unwrap are overlapping or are outside of the [0;1]x[0;1] range we should validate that, so that the user knows where does the weirdness come from.
We already check if the UVs are outside of the [0;1]x[0;1] range and emit a warning, also Beast skips triangles that are entirely outside of that range (see case 442606).
When importing second UVs we should check for overlapping triangles and if there are any, we should visualize the problem for the user, so that it's easier for him to fix it in his 3D app of choice.
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