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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Add comment