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
- 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
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment