I have just migrated to 4.12 and run into a very annoying behavior change. Since I didn’t find anything in the release notes about it, I assume it’s a bug.
So here is the problem I’m facing:
Before 4.12, I could drag and drop a folder from the explorer to the content browser of UE and all that folder was imported in the project with the corresponding folder structure. For example, in the explorer, if I had:
folder0
folder1
folder1.1
Asset1
Asset2
folder2
Asset3
and in the content browser, I created a folder Test and drag and drop folder0 to Test in the content browser, the result in content browser was:
Am I missing something here or is it a bug?
Is there a way to get back to the behavior of previous versions when importing folders (maybe an option somewhere)? I have hundreds of assets to import for which I really need to keep the folder structure and I can’t imagine having to redo the whole structure by hand.
Migrating folders is always a pain and problematic. (At least in my experience.) Generally any importing and exporting with folders breaks/changes somewhere for some reason, generally the only way i have solved it.
By keeping its exact file/folder structure, is when i have a “level” that contains everything you want migrated over. So all you do it migrate the level over, which brings everything contained within that “level” over aswell.
While retaining the EXACT way it was in the original form, with no additions or changes, otherwise when i migrate folders or any that is neat and orginised the way i want it. The structure breaks every time, which is a great pain to me.
So i suggest (if possible) to create a level that contains EVERYTHING that you want carried over (They don’t even need to be placed properly, just make sure everything is referenced within the level.
Bascially a parent (the level) - child [the folder structure(s)] relationship, so it will bring everything you want over.)
Or it could simply be because you are ‘draging and droping’, are you not migrating the ‘official’ way? Which is to right click, and select “migrate” maybe it could work.
Thanks for your answer, but I’m not sure it applies to what I describe. I’m not talking about migrating stuff between projects but of importing assets (textures and fbx mostly) stored on my harddrive to a project.
Your answer though gives me an idea for a workaround: I will create a project in 4.10 or 4.11, import my stuff and then migrate it to my 4.12 project. If it works, it will still be a workaround and I still think that this behavior is probably a side effect of another change made to the drag and drop to content browser functionality.
I was able to reproduce the issue following the repro steps you have provided above and have entered the following bug report: UE-32155. Once this issue has been resolved, we will notify you with an update to this post.
So, there is still no way to keep the folder structure when importing files from the explorer into the project? Because that’s what I need to do. And the editor just puts everything in the root folder where I dropped the folders.