Search Issue Tracker
Won't Fix
Votes
1
Found in
5.4.0b18
Issue ID
801797
Regression
No
Scene is instantly marked dirty when opened if any object is affected by both a ContentSizeFitter and VerticalLayoutGroup
How to reproduce:
1. Open the attached project
2. Drag the two scenes into the Hierarchy "temp" and "temp2"
3. Select the green box and enable the ContentSizeFitter, so that it resizes itself vertically based its contents. ("Canvas" > "Example Prefab" > "GameObjWithProblem")
4. Hit Ctrl+S to save the scene
5. Right click on the "temp" scene again then click GameObject > Create Empty and save the scene
6. Hit Delete to destroy the created GameObject and save the scene again
7. Right click on the "temp" scene in the Hierarchy tab then click Unload Scene to unload it
8. Right click it again then click Load Scene to reload it.
9. Notice that the scene WAS instantly marked dirty! This will now happen every time the scene is reopened
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
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
- [VFX] Missing Expand Toggle with Output Slot
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
guyno
Aug 08, 2018 07:34
Still an issue in 2017.4.8f1
Cathero
Jul 02, 2018 11:21
This is indeed very annoying (still in 2018.1), for the reasons mentioned in the previous comments...
NEVER-SETTLE
May 13, 2018 16:01
Same issue on 2018.1, extremely annoying
problemecium
Mar 18, 2018 04:21
Confirmed still not fixed in 2017.3.1f3. I agree that this move makes little sense.
It also causes an issue wherein the Undo functionality is broken, as every time I attempt to Undo something, the RectTransform involved updates itself again, so that the last action available to Undo is always "Undo Driving RectTransform."
Could someone please re-evaluate this issue and the decision to never try to fix it?
BCook99
Sep 26, 2017 00:55
This is affecting us, too in 5.6.2. I don't understand why this is a Won't Fix. Probably the analyst at Unity doesn't use source control so they don't know that it causes spamming of large scene file being marked as changed. This is apparently OK behavior?