Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.6.4f1
Issue ID
973253
Regression
No
Entering a value >100 in Crunch Compressor Quality and hitting Apply right away temporarily spikes CPU usage
Steps to reproduce:
0. Switch platform to Android
1. Import the attached image (or any other square image) into a project
2. Set Texture Type to Sprite in Import Settings
3. Enable Use Crunch Compression
4. Enter some high value like 4096 in the field next to Compressor Quality
5. Hit Apply without clicking anywhere else
6. Compare the load time to the same action being performed with a number that is within the 0...100 range.
Note: I am attaching a user-submitted video. Testing it out on office computers resulted in a nearly negligible difference.
Expected result: the value doesn't get processed
Actual result: Unity seems to process the value if the user hits Apply while still in the field
Reproduced on: 5.6.4f1, 2017.0, 2018.1.0a4
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