This seems to be a issue with 4.18 it could of been there with 4.17 but I’m unsure, moving folders in 4.18 result in materials not being able to find textures and meshes not being able to find there materials, moving assets without there folders seems to work just fine.
1 Like
Hello,
We’ve recently made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.
Thanks
I thought it was just me, this is driving me crazy! I purchased a helicopter and then it created a project. I merged the folder to my project and it took me 4 hours remapping all of the textures to the materials, what a pain in the butt. Also if you just move a folder in your project it does the same thing.
A couple of things to consider; you can’t move files outside of the UE4 Content Browser without messing up references, that has been true since UE4 first came out. Always use the Content Browser to move files within a project, and use the “Migrate” function (found in the right click menu when selecting a folder, and the “Asset Actions”->“Migrate” for individual assets) to move content from one project to another.
Once you have moved content it is always a good idea to immediately right click the “Content” folder in the Content Browser and select “Fix up Redirectors in Folder”. This will make the changes permanent by removing temporary redirectors containing asset references that are created during the move process.
asset files within the editor mate… and yes you can move files outside the editor aslong as your moving everything that is referenced, but this isn’t the point or subject we are talking about, the editor sometimes has issues moving textures and materials, redirectors are not made because viewing the reference viewer paths are not updates, which is why “Fix up Redirectors in Folder” doesn’t work, I haven’t had time to put together a debug project to demo this yet.
Yeah I’m still getting this issue 4.19 does it aswell, i work around it by just moving the files rather than the folders.
Good information, I will try that!
This is defiantly a problem.
Well in that case it definitely should not be happening. I use 4.19.2 and have no issues moving folders with assets around, not sure what’s going on there, that’s really bizarre. Only time I have run into that issue is migrating assets from an earlier version into the project.
Before moving it, try opening the asset up to make sure it is in memory, then move the folder. The engine seems to load assets on an as needed basis now, maybe they aren’t loaded properly. Sorry I’m not much help here, but that’s all I can come up with at the moment.
I’ve just destroyed a project moving all bought assets in a dedicated folder. (4.20.1)
Git is a life-saver.
this confirms my suspicions. I keep not setting up source control because I’ll work like a mad man in bursts. makes no sense that this happens when there’s ‘fix redirections’ and ‘validate assets in folder’ in the ■■■■ context menu.
whats totally appalling is that I moved entire folders into a higher level folder. Adding one folder to the path should not cause such serious problems like this. Isn’t this just basic file system stuff here? Not like I’m scattering assets all over the place, literally just dragging one folder into another folder. I’m on UE4 4.21 and it’s still a major issue.
Eveything seems to be working now on 4.21.1
Just make sure when you Migrate from one project to another only move it to the Content folder and then after the Migration you can then move it to whatever folder you want.
This is STILL an issue. Just lost hours of work from this danged bug.
I buy assets on the store, start moving them, validating AND fixing redirections as I go along…
Went to load a map and now I’m getting all kinds of “The asset is probably corrupt” or whatever the error is… Something as simple as moving files should NOT be this broken…
1 Like
2022 still broken UE4.27.2
Was finally able to move 60 UserWidgets at once without the hellish “failed to load outer” error deleting contained UWidgets.
From my documentation:
- The “Failed to load outer for…” is common with widgets and can delete the contents of entire UserWidgets if you continue to use them. Stop working, close the editor and clear the following cache folders:
–\AppData\Local\UnrealEngine\Common\DerivedDataCache
–\AppData\Local\UnrealEngine\Version\DerivedDataCache
–\Project\DerivedDataCache\
The next time you restart the project it will take some time to start, but this error should be gone.
*Update This is not a general fix for moving assets though. Some things like SoftObjectPtrs set in the Project Settings will still break and references made in skeletal animations are still likely to break. It’s a fragile system no matter how you move things.
Yep its still bugged, just move it by asset which is more work but a lot safer.
2 Likes