Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0f2
Issue ID
1086774
Regression
No
Having a lot of textures with unique "Packing tag" results in a performance drop
Reproduction steps:
1. Open "testLoad123.zip" project
2. Open the Profiler window
3. Enter Play mode
4. After a few seconds notice a big Spike ("Loading.AwakeFromLoad" takes ~1000ms)
5. Exit Play mode
6. In the Project window right click on "Atlas2" -> "AtlasPackingTag" -> "Remove"
7. Enter Play mode
4. After a few seconds notice a small Spike ("Loading.AwakeFromLoad" takes ~200ms)
Expected Result: Having a lot of textures with unique "Packing tag" doesn't result in such a huge performance drop
Actual Result: Having a lot of textures with unique "Packing tag" results in a performance drop
Reproduced with: 2019.1.0a12, 2019.1.0a8, 2018.3.0b9, 2018.2.15f1, 2018.1.9f2, 2017.4.14f1
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (2018.2.X):
Packing sprites based on Packing Tags will incur an overhead of loading additional data when entering Play-mode (happens only in Editor).
This is to be expected as each sprite has to look up and load render data from the cache.
To avoid such overhead please use the newer Sprite-Atlas Asset instead.