Search Issue Tracker
Fixed in 2017.1.X
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
- FP32 is used for a temporary when compiling a shader for GLES or Vulkan
- The highlight that was created with Highlighter.Highlight does not disappear when the window is closed with the element
- [URP] CommandBuffer warnings thrown while debugging Depth Overlays with Post-processing enabled in Rendering Debugger
- An Unhandled exception is thrown in the Editor.log and Console window when trying to build AssetBundles
- InterlockedExchange function throws an error when using floats as arguments
cp_sn
Mar 29, 2017 21:26
is there any version out with this fixed?