Search Issue Tracker
By Design
Votes
0
Found in
5.1.3f1
Issue ID
722935
Regression
No
[Sprites] Spite.Create() takes more time if rect is 33x33 compared to 31x31
Reproduction steps:
1. Open attached project
2. Open "TestScene" scene
3. Open test.cs and uncomment "areaOfSliceInTextureToDraw = new Rect(0,0,33,33);"
4. Save test.cs
5. Play/Run "TestScene" scene (Notice how much time it took to process)
6. Open test.cs and uncomment "areaOfSliceInTextureToDraw = new Rect(0,0,31,31);"
7. Save test.cs
8. Play/Run "TestScene" scene (Notice how much time it took to process)
Note: For a 31x31 rec it will take 0 ms per Sprite to process and 0 ms for 25 Sprites. For 33x33/32x32 it will take 14.48 ms per Sprite to process and 362 ms for 25 Sprites. And for other rects under 31x31 it will take 0 ms.
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
Add comment