Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2018.4.9f1
2019.4
2020.2
2021.1
2021.1.0a9
Issue ID
1299185
Regression
Yes
Dragging a Prefab into the Scene view and undoing the action still shows the scene as dirty
How to reproduce:
1. Create a new Unity project
2. In the Project window create a new Prefab
3. Drag and drop the prefab to the Scene view
4. Take a look at the Scene name in the Hierarchy
5. Undo your action (CTRL+Z)
6. Take a look at the Scene name in the Hierarchy
Expected result: After the undo Scene is shown as unmodified
Actual result: After the undo Scene is shown as modified
Reproducible with: 2018.4.9f1, 2018.4.30f1, 2019.4.16f1, 2020.1.17f1, 2020.2.0f1, 2021.1.0a10
Not reproducible with: 2018.4.0f1, 2018.4.8f1
Note:
- Dragging the Prefab to the Hierarchy makes the Scene Dirty and undoing that makes the Scene not Dirty successfully
- Prefab is mentioned for reproduction purposes, the issue occurs with Models, that create a GameObject in the Hierarchy
- If the Scene is modified it is indicated by the " * " at the end of its name in Hierarchy
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
- ACES Tonemapping causes banding artifacts and negative values in ColorGradingLUT when HDR is enabled and "High Dynamic Range" Grading mode is selected while Android Platform is used
- Android Player freezes when an Audio Source is playing and an incoming call is picked up and then hung up and the Audio Source is started again
- Green success icon is poorly visible in the light Unity theme
- Incorrect input into the Input Field when using Microsoft IME Japanese
- Multiplayer role "ClientAndServer" is displayed without the spaces in the "Play Mode Scenarios" window
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a5
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0b11
Resolution Note (fix version 2020.3):
Fixed in 2020.3.4f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.26f1