Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0a6
2018.2.14f1
Issue ID
1098033
Regression
Yes
Changing an existing array type from "string" to "Color" turns some of the array color pickers to an unchangeable black color
How to reproduce:
1. Open the user-submitted project ("PixelPerfect.zip")
2. In the Hierarchy Window click on the "ReadyToReproduceBug" game object and observe its Inspector Window
3. Open the attached "ChangeStringArrayToColorArray" Script
4. Change the "string" array to a "Color" array in line 7 and save the script
5. Focus back on the Editor and observe the "ReadyToReproduceBug" object's Inspector Window
6. Try changing the colors of all 3 arrays
Expected result: The string array is changed to a color array with no issue
Actual result: Some of the newly changed color arrays get "corrupted" to an unchangeable black color which persists between Editor restarts
Reproduced in: 2019.1.0a8, 2018.3.0b9, 2018.2.16f1, 2018.1.9f2, 2018.1.0a6
Not reproducible in: 2018.1.0a5, 2017.4.15f1
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
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
Resolution Note (2019.1.X):
The colors are not unchangeable, they are just overexposed/underexposed. These can be changed if you got to RGB float input mode(0-1.0), scroll the fields all the way to the right and switch back to 0-255 mode. Fixing this would limit the functionality where used can set the color values deliberately