Search Issue Tracker
Not Reproducible
Votes
0
Found in
2022.1.0a1
Issue ID
1352156
Regression
Yes
Not uploading texture to the 3D API / GPU during importing has regressed StreamingTests.TextureLoad test in performance
Introduced in https://ono.unity3d.com/unity/unity/pull-request/127662/_/dcc/textureimporter/no-gpu-upload
Tests affected:
StreamingTests.TextureLoad
Platforms affected:
Mac Editor
Graph: https://observer.ds.unity3d.com/19f48415dedd517ed2248fc4cc785ed5773bc867
To run locally:
perl utr.pl --suite=performance-playmode --testproject=Loading --testfilter=StreamingTests.TextureLoad --platform=Editor
To run in Katana:
https://katana.ds.unity3d.com/projects/Unity/builders/proj0-Test%20Performance%20PlayModeTests%20-%20MacEditor?unity_branch=trunk
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