Search Issue Tracker
Fixed
Votes
0
Found in
5.4.0b2
Issue ID
762692
Regression
No
After Moving Component Up or Down scene is not marked as Dirty
To reproduce the issue follow the steps:
1. Create a GameObject and attach a couple of components
2. Notice that the scene is dirty (denoted by the '*' next to the scene name in the Hierarchy window)
3. Save the scene. Notice that the '*' goes away
4. Right-click a component and choose the 'Move Up' or 'Move Down' option
5. The scene is not marked as dirty
Expected scene is marked as dirty (remind you to the save scene) because part of the object was changed.
Reproduced in 5.4.0b2, 5.4.0b1, 5.3.1p3, 5.2.2p1, 5.1.2p4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory usage rises when switching scenes with GRD enabled and a loaded texture in URP
- [Quality Hackweek] Terrain Brush Size value is not serialized after deselecting the terrain when using the first instance of multiple Inspectors
- "NullReferenceException" is thrown when setting a long string in TMP with "Atlas Population Mode" set to "Dynamic" and "Multi Atlas Textures" enabled
- TextMeshPro text is misaligned when alignment is set via script
- A DX11 shader error is thrown when compiling shaders for platforms without DX11 support
Add comment