Search Issue Tracker
By Design
Votes
0
Found in
5.3.4f1
Issue ID
786900
Regression
Yes
DestroyImmediate doesn't mark scene as dirty
Steps to reproduce:
1. Open attached project
2. Open scene "Scenes/TransparencyBugScene"
3. In top menu, open "Ninjetc Tools > PixelDestruction > New Terrain" menu
4. Select the bottom option "!!! Delete Existing World !!!"
5. Save the scene but not as new scene
6. Re-open scene - notice that deletion of objects isn't saved
Workaround: Instead of DestroyImmediate, use Undo.DestroyObjectImmediate
Not reproducible: 5.2.4f1, 5.3.0a3
Reproduced with: 5.3.0a4, 5.3.4p2, 5.4.0b14
Regression introduced in: 5.3.0a4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
Add comment