Search Issue Tracker
Fixed in 0.6.0-preview.24
Votes
0
Found in [Package]
0.5.1-preview.11
Issue ID
1218733
Regression
No
[ECS] Locking the Inspector of an Entity from Entity Debugger while in Play Mode throws exceptions after exiting Play Mode
How to reproduce:
1. Open attached project "InspectorLock.zip" and scene "SampleScene"
2. Enter Play Mode
3. In Entity Debugger window, select any entity and lock the Inspector window
4. Exit Play Mode
Expected result: No exceptions are thrown
Actual result: "NullReferenceException: Object reference not set to an instance of an object" exceptions are thrown
Reproducible with: 2019.3.5f1, 2020.1.0b1, 2020.2.0a2
Could not test with: 2017.4, 2018.4 (no ECS support)
Reproducible with package versions: 0.3.0-preview.4, 0.5.1-preview.11
Note:
Unlocking the Inspector after exiting Play Mode stops the exceptions from being thrown
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 0.6.0-preview.24):
Fixed package available from Unity version 2019.3.0f1 and up.