Scene merge conflicts because of m_RootOrder

Unity Engine
1

Hello,

when changing a scene only marginally by inserting, deleting or moving a game object in hierarchy, the resulting change to the scene file can be enormous. More specific, a lot of lines with “m_RootOrder” get changed due to the single change.

This makes merging scenes complicated. Is this intended? Or is it a known problem already? And should I file a bug report explaining this? Is “scene file mergability” even a design goal for Unity in the first place?

To be honest, merging of scene files was outright impossible in Unity 4.x and probably still is “almost impossible” in Unity 5, but I see a light at the end of the tunnel. It seems that Unity 5 is taking steps to maybe enable this feature in the future some time ahead…?

2 Likes
2

If anyone from Unity is interested, I’ve filed a bug report under 665302

3

Maybe the new scene merger will fix the problem but till then , it seems a big problem.
A little hint , if you post the link to the fogbugz portal , everybody can see every bug-report you ever made. (Not sure if that was your intend)
If you like to post the report for the unity stuff you better post the reference number. (665302 in your case)

1 Like