Search Issue Tracker
By Design
Votes
0
Found in
5.3.3f1
Issue ID
774196
Regression
Yes
Custom inspector stopped working after Unity update
To reproduce:
1. Open attached project
2. Open SceneA
3. Change the value of "someValue" with the slider in the custom inspector for MyBehaviour
4. Change to SceneB
5. Notice, that no save dialog pop ups
6. Change back to SceneA
7. notice the value of "someValue" was reset to it's previous value
Regression from 5.2.4p1
Reproducible: 5.4.0b8, 5.3.3p1
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
Add comment