Search Issue Tracker
By Design
Votes
0
Found in
2017.4.2f2
Issue ID
1032434
Regression
No
Instantiating a prefab in a scene with InstantiatePrefab does not set scene dirty
Reproduction steps:
1. Download user's project and open in Unity
2. Open scene "P1"
3. Select "Obj1" in Hierarchy
4. Press "Clone Right" in Inspector of "Obj1"
Expected: new prefab is added in the "P1" and the scene is set to dirty
Actual: new prefab is added in the "P1" and the scene is not set to dirty
Reproduced on: 2017.1.3p4; 2017.2.3f1; 2017.4.3f1; 2018.1.0f2; 2018.2.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment