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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment