Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.5.0b3
Issue ID
831466
Regression
No
Replacing scene on disk with another scene does not make dirty original scene instance in Scene Manager
Steps to reproduce:
1. Open attached project. (or create new one with two scenes, can be empty, no diff)
2. Open both scenes in additive.
3. Make some changes to second one.
4. Save the second scene onto the first one (replace).
Expected result: First scene should be marked as dirty. (or HandleOpenScenesChangeOnDisk should be called with reload scene dialog)
Actual result: Both scenes point to same asset, they look different in hierarchy and both are not dirty.
Note: Scene manager contains two instances of same scene asset, which is invalid according to SceneSet::IsValid and SceneManagerSetup::IsValid, opening same scene twice is also not possible.
Reproduced on: 5.5.0b3, 5.4.0f1
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 when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Add comment