Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.35f1
2022.3.20f1
2023.2.11f1
2023.3.0b8
Issue ID
UUM-64262
Regression
No
[2D] Part of a Sprite is cut off when the "Mesh Type" value is set to "Tight"
Reproduction steps:
1. Open the attached “BugRepro” project
2. Select the “PG_SC_InfoBar_02_BG” Asset in the Project window
3. Make sure “Mesh Type” is set to “Tight”
4. Observe the “PG_SC_InfoBar_02_BG” GO in the Scene View
Expected result: The Sprite is rendered without any cutouts
Actual result: Part of the Sprite is cut
Reproducible with: 2021.3.35f1, 2022.3.20f1, 2023.2.11f1, 2023.3.0b8
Reproducible on: Windows 10, Ubuntu 22.04
Not reproducible on: No other environment tested
Add comment
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
Resolution Note:
This is expected as the auto mesh generation is a generic approach to generate mesh for Sprites.
In edge cases it is recommend to use the custom outline module in Sprite Editor to fix this issue.