Search Issue Tracker
Fixed
Fixed in 6000.4.0f1, 6000.5.0a6
Under Consideration for 6000.3.X
Votes
0
Found in
6000.3.2f1
6000.4.0b2
6000.5.0a3
Issue ID
UUM-130958
Regression
Yes
Artifacts appear on Sprites when generating a Sprite Atlas with Padding set to 2
How to reproduce:
1. Open the attached “IN-128162” project
2. Open the “SampleScene”
3. In the “AtlasTest” folder, select the “MenuUI” asset
4. In the Inspector, change the “Padding” field to 2 and click “Apply”
5. Observe the Scene/Game view
Actual result: There are artifacts on the Sprite
Expected result: No artifacts are visible on the Sprite
Reproducible with: 6000.3.2f1, 6000.4.0a1, 6000.4.0b2, 6000.5.0a3
Not reproducible with: 6000.0.64f1, 6000.3.0a6
Reproducible on: macOS 26.1 (M1 Pro)
Not reproducible on: No other environments tested
Notes:
- Once the issue has been reproduced, the issue will persist if the project is downgraded to an older version and requires generating the Sprite Atlas again. This can be done by changing “Padding” to 4, generating the atlas, changing over the setting back to 2 and generating once more
- The issue reproduces with “Padding” set to 2, other options do not produce artifacts
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
- 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
Resolution Note:
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.5.0a6):
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.4.0f1):
Fixed in 6000.4.0f1