Search Issue Tracker
Fixed in 5.3.1
Votes
0
Found in
5.3.0f1
Issue ID
747804
Regression
Yes
[Editor] Custom inspector UI field changes are not saved
Steps to reproduce:
1. Download and import attached project.
2. Load "scene" scene.
3. Select "Main Camera"
4. Change "My Property Field" value to any you like.
5. Save the scene.
6. Close Unity and open it again, notice that "My Property Field" did not changed.
Expected result: "My Property Field" value change is successfully saved in the scene.
Actual result: "My Property Field" value changes are not saved.
Reproduced: 5.3.0f3, 5.3.0f2, 5.3.0b1
Did not reproduced: 5.2.2f1, 5.1.4f1
Regression starts on: 5.3.0b1
Comments (1)
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
EricSivilog
Jan 02, 2016 15:05
Just wondering if the bug has reappeared in 5.3.1:
http://forum.unity3d.com/threads/oninspectorgui-issues-from-5-2-3-to-5-3-1.377245/