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
- [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