Search Issue Tracker
Duplicate
Votes
0
Found in
2018.1.0b7
2018.1.0f2
Issue ID
1035491
Regression
Yes
Scriptable object inspector auto unlocks when entering play mode
How to reproduce:
1. Create empty Unity project
2. Create ScriptableObject script with at least one public field and make it creatable from the menu
3. Create ScriptableObject
4. Lock it in the inspector
5. Make sure game window is checked maximize on play
6. Enter play mode
7. Pause the game
8. Inspector is unlocked
Expected result: Inspector should remain locked all the time
Actual result: Inspector became unlocked after entering the play mode
Regression first introduced in: 2018.1.0b7
Reproducible with: 2018.3.0a1, 2018.2.0b4, 2018.1.0f2,
Not reproducible with: 2017.4.3f1, 2017.3.2f1, 2017.2.2p2, 2017.1.4f1
Note:
Bug similar to 1031140 but it can be reproduced with different versions
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
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
- [Android] Virtual device crashes with "Scudo ERROR: invalid chunk state when deallocating address" error in Firebase Test Lab when Optimized Frame Pacing is enabled
- Particle System does not resume when its Culling Mode is set to "Pause" or "Pause and Catch-up," and particle position simulate in world space
- "Custom Render Queue" field cannot be set above "2000" when changing it in the Inspector window using Debug mode
This is a duplicate of issue #1031140