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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment