It seems that when you upgrade to a new engine version all of your collections reset. This is particularly bad because UE4 Doesn’t abstract between the way folders are presented in the editor and where they are on disk so the folder structure is extremely brittle and prone to causing problems if you reorganize anything post-facto.
Collections are an acceptable stand-in for this but having them reset on engine upgrade doesn’t seem like intended behaviour.
Hey Hyperloop,
Thanks for noticing this Collections issue within the Editor. I have submitted a report referenced as: UE-18319. If you’d like to check on this bug in the future, please feel free to reply back here and mention UE-18319.
If you have any further questions, please let us know! Have a wonderful day!
Hi Hyperloop,
This issue was caused by the project copy step failing to copy the Saved directory (which is where local collections are stored - shared and private collections would not have been affected as these are stored in the Content directory). This has now been fixed, and will be part of the 4.9 release.
If you still have the old versions of your project, you can find your local collections in the Saved/Collections folder - feel free to copy this to your new projects, and sorry for the inconvenience.
Thanks,
.
That is very helpful, thank you .