Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2017.4
2020.1.0a25
2020.2
Issue ID
1226069
Regression
No
"<multi>" string appears in the "Aniso Level" slider's value input field, in the Inspector, with multiple textures selected
How to reproduce:
1. Open the attached project (1226069.zip)
2. In the Project window go to the Textures directory and select all textures
3. In the Inspector window enable the "Fadeout Mip Maps" option under the "Advanced" dropdown
4. Select the "Aniso Level" value input field
5. Press Ctrl+Z to undo
6. Press anywhere on the "Aniso Level" value slider
Expected result: The "Aniso Level" value input field displays a numeric value
Actual result: The "Aniso Level" value input field displays "<multi>"
Reproducible with: 2017.4.38f1, 2018.4.19f1, 2019.3.6f1, 2020.1.0b2, 2020.2.0a3
Notes:
1. Deselecting the "Aniso Level" value input field or applying any changes made to the textures sets the value to a number
2. Tested on Windows 10, Windows 7, Linux(KDE Neon 5.18) PC's and a Mac
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
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Resolution Note (fix version 2020.2):
Fixed in 2021.1.0a1