The stable grouping for new added assets

[hiroki-o]

Original report by Jihyun Oh (Bitbucket: [John OH](https://bitbucket.org/John OH), ).

---

I got this issue from a customer. But, I think it may common issue for live services.

I am trying to use ‘Group By Size’ node. But, There is an inefficient case when I use it. I wonder you have a plan to improve it.

Images below show cases that generated AssetBundles are modified heavily when new assets are added into Group By Size filter. When an asset named BACK1.psd is added, the asset influence with existing assets as randomly ordered. And, Results are changed heavily. Then, I have to live patch so many bundle files. What I want to do is that BACK1.psd will be placed after existing assets.

If there are features or ways to change sorting order as recently added assets, BACK1.psd will be placed in the end. So, bundle_0~bundle_5 will not modified, and, BACK1.psd will be added into bundle_6 or new bundle_7. Then, I can have live patch for updated files only.

If you add features to support this situation, I can use ABGT on my project. Please check it.

[hiroki-o]

Original comment by Hiroki Omae (Bitbucket: [Hiroki Omae](https://bitbucket.org/Hiroki Omae), ).

---

Stable grouping on Group By Size is now supported on dev branch. Please try this and see if it solves your problem.

By checking "Freeze group on build", Group By Size will remember group configuration when last build is performed. You can import and export group setting and edit manually if needed.

Also, the group setting is automatically exported inside Cache folder on build.