Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
5.5.0p4
Issue ID
886007
Regression
No
New instance of a prefab appears in a Hierarchy, after you undo "Add component" and then change any value of a prefab
To reproduce:
1. Create a new project.
2. Create empty object.
3. Make it a prefab.
4. Select Prefab instance in Hierarchy.
5. Add Animator Component (or any other component).
6. Apply to prefab.
7. Press ctrl+z
8. Change any value in Transform.
9. Apply to prefab.
Actual result: a new instance of a prefab appears in Hierarchy. (sometimes when it appears it becomes disabled)
Expected result:you have the same number of prefab instances in Hierarchy.
Reproducible: 5.3.7p1, 5.4.4p4, 5.5.2p1, 5.6.0b10, 2017.1.0a2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment