Search Issue Tracker
Fixed
Fixed in 6000.5.0a6
Votes
0
Found in
6000.3.4f1
6000.4.0b4
6000.5.0a4
Issue ID
UUM-132095
Regression
Yes
Artifacts are present on Sprite Atlas Sprites when Binlinear or Trilinear filtering is used
How to reproduce:
- Open the “Atlas_Bug.zip“ project
- Open the “SampleScene“
- Enter Play Mode
- Observe the Game view
Actual result: Artifacting, or at least artifacted bleeding, can be seen to the left of the Sprite
Expected result: No artifacts are seen to the left of the Sprite
Reproducible in: 6000.1.0a9 (0115cb901a32), 6000.3.4f1, 6000.4.0b4, 6000.5.0a4
Not reproducible in: 6000.0.65f1, 6000.1.0a8
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
Notes:
- Though the artifact matches the pattern size of the leftern sprite, the artifact itself is not of the expected shape (dotted) and is just a straight line. Unless the bleeding is expected, the bleeding should not be artifacted either (should look dotted)
- Only reproducible in Play Mode
- Increasing the Atlas padding to 4 or 8 removes the artifact, but with a padding of 2, this should not reproduce either
- Not reproducible with ‘Point’ Filter Mode
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