Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a3
2019.3.0b7
2020.1
Issue ID
1193288
Regression
Yes
GameObject's value field does not get colored in light blue in the Inspector window when an object is dragged onto it
How to reproduce:
1. Open the attached 'project-1193288.zip' project
2. In the Hierarchy window select 'Cube'
3. Drag the 'New Physic Material' material from Project window onto Cube's Box Collider's Material field
Expected result: field is colored in light blue
Actual result: field is not colored in light blue (field's borders are highlighted)
Reproducible with: 2019.3.0a3, 2019.3.0b9, 2020.1.0a11
Not reproducible with: 2017.4.33f1, 2018.4.12f1, 2019.2.11f1, 2019.3.0a1, 2019.3.0a2
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.1):
Fixed the styling issue, where the control does not get filled with blue color when an entity is dragged onto it.
Fixed in 2020.1.0a21
Resolution Note (fix version 2019.3):
Fixed in 2019.3.5f1