Search Issue Tracker
Fixed in Unity 2017.1
Votes
1
Found in
5.5.0p3
Issue ID
874301
Regression
Yes
Locking the Inspector on subscene objects causes their disappearance and "Failed to unpersist" errors
How to reproduce:
1. Open attached project "874301-repro.zip"
2. Open "Test" scene
3. Add additional scene "Test2"
4. Enter play mode
5. Select game object "Cube" in "Test2"
6. Lock Inspector
7. Exit play mode
Expected behavior: Game object "Cube" stays in the same place and no errors occur in the Console
Actual behavior: Game object "Cube" has disappeared from Hierarchy. "Failed to unpersist" errors in the Console
Reproducible: 5.5.1p1, 5.6.0b5
Not reproducible: 5.3.7p3, 5.4.4p2
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
- Unity crash in SerializedFile::ReadMetadata<false> when AssetBundle. LoadFromMemory() is called
- ProceduralMaterial.ClearCache() on "Do Nothing" Substance triggers RebuildTextures
- Setting "Default Behavior Mode" to "2D" breaks HDR rendering
- Crash in GdipCreateBitmapFromStream when calling System.Drawing.Bitmap constructor
- DLL files are not excluded during building for standalone platform, even though they are selected to be excluded
cp_sn
Mar 29, 2017 21:26
is there any version out with this fixed?