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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 2020.2):
Fixed in 2021.1.0a1