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
- 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