Download

Is it not safe to move or delete any blueprint related files?

In 4.22.3 I noticed that moving or deleting any files that are related to any blueprint content, especially from the marketplace, even after fixing redirectors, tends to cause a lot of bugs where it causes broken references and other odd things. When I say blueprint related files, I mean anything that a blueprint references to run properly, even a texture, material, or mesh etc. This is making it very difficult to organize files/content properly, does anyone have any advice on this?

@Pine722 I’ve found that you should never delete something if you have to use ‘force delete’. Bascially, if the system says there’s a link, then there is, even if you can’t see it.

Apart from that I’ve had no problems moving anything into any folder.

I’ve noticed that as well so I don’t ever force delete anything, however I’m noticing it even when moving around or deleting things that I didn’t force delete. For instance one folder that holds blueprint related things that have to all do with post processing effects, I moved some of the files & now the post process effect looks completely different than how it should and I had to completely remove and reinstall the folder without moving/deleting anything with it to make it show up properly. Is there a way to figure out what’s going on with it or an alternative safer way to move files?

@Pine722 I’ve never had anything like that. Typically just using the content browser works fine for me. I think the only other thing to watch ( apart from force delete ) is don’t move assets around when you have more than one copy of the project open…

When you move an object in Unreal’s content browser, if any other object refers to the object you just moved, it will create a redirector at the old object’s location that points to the new object. On disk, that redirector will have the same name as the old object.

Let’s say BP_MyBlueprint references OldLocation/S_MyMesh, and I move S_MyMesh to NewLocation/
The old reference looked like this:


BP_MyBlueprint -> OldLocation/S_MyMesh

After the move, it looks like:


BP_MyBlueprint -> OldLocation/S_MyMesh (redirector) -> NewLocation/S_MyMesh

That redirector is left behind to allow you to move objects around even if you’re not able at that moment to update every object that refers to them (for instance because someone else has a referencing object checked out.)

To find redirectors left behind in your content browser, select Filters | Other Filters | Show Redirectors.


You’ll now be able to see your redirectors. To update the referening assets to point to the moved asset in its new location, right-click a redirector and select “Fix Up.”

Any asset that was referring to the file in the old location will be updated to point to the new location, so the redirected reference:


BP_MyBlueprint -> OldLocation/S_MyMesh (redirector) -> NewLocation/S_MyMesh

will be replaced by:


BP_MyBlueprint -> NewLocation/S_MyMesh

You’ll be prompted to re-save any asset that was updated in the fix-up.
You can also right-click a folder to fix up all redirectors in the folder.

It’s a good idea to get into the habit of fixing up your redirectors as soon as you can after you make a move. You don’t want to let your project turn into a rats-nest of redirectors if you can avoid it.

So I’ve enabled the show redirectors filter, and there’s still nothing in those folders in the content browser, but they are there in the file explorer outside the editor. Fixing redirectors on those folders does not do anything. I still can’t delete the folders either. So it seems this is a bug with the editor, I’d assume it’s a bug with the linux version only, perhaps? But if that’s the case what am I supposed to do now since I can’t move/delete etc files without causing huge problems…
I need a way to organize things together so then I can drag and drop them into the scene…
Epic isn’t going to be fixing this for 4.22.3, that is even if they bother to fix it at all…

Thank you for telling me about the show redirectors filter by the way as I did not know it was a thing, although apparently not useful with this bug situation unfortunately…

Because I wanted to confirm if what I thought is true is true, I copied the project folder to the 4.24.0 Preview 2 version of the engine, sure enough when I attempted to move that same folder it also caused issues. Not only was the issue not fixed from 4.22.3, but it’s actually worse in 4.24.0, it actually will crash the entire editor now if you attempt to move the folder…
You can follow another topic of mine which is related to this one, here Can't delete "empty" folders because files are still in them? - Content Creation - Unreal Engine Forums

Below is an update to my post:

Preview 2 crashes when moving folders in the content browser, on Linux. This same folder causes issues when attempting to move it in 4.22.3 as well, when attempting to move it and fix redirectors it leaves “empty” folders there instead that can’t be moved or deleted, where if you look outside the editor in the file explorer you will see files left in those 'empty" folders.

“Exception was “SIGSEGV: unaligned memory access (SIMD vectors?)””


Caught signal

libUE4Editor-Engine.so!UWorld::Tick(ELevelTick, float) [/Engine/Source/Runtime/Engine/Private/LevelTick.cpp:1722]
libUE4Editor-UnrealEd.so!UEditorEngine::Tick(float, bool) [/Engine/Source/Editor/UnrealEd/Private/EditorEngine.cpp:1504]
libUE4Editor-UnrealEd.so!UUnrealEdEngine::Tick(float, bool) [/Engine/Source/Editor/UnrealEd/Private/UnrealEdEngine.cpp:407]
UE4Editor!FEngineLoop::Tick() [/Engine/Source/Runtime/Launch/Private/LaunchEngineLoop.cpp:4479]
UE4Editor!GuardedMain(char16_t const*) [/Engine/Source/Runtime/Launch/Private/Launch.cpp:175]
libUE4Editor-UnixCommonStartup.so!CommonUnixMain(int, char**, int (*)(char16_t const*), void (*)()) [/Engine/Source/Runtime/Unix/UnixCommonStartup/Private/UnixCommonStartup.cpp:242]
libc.so.6!__libc_start_main(+0xf2)
UE4Editor!_start()

part of the log:


 73]LogDirectoryWatcher: Error: inotify_rm_watch cannot remove descriptor 206 for folder '/Content/Maps/Demonstration_sharedassets' (errno = 22, Invalid argument)
 73]LogDirectoryWatcher: Error: inotify_rm_watch cannot remove descriptor 204 for folder '/Content/Maps' (errno = 22, Invalid argument)
 73]LogDirectoryWatcher: Error: inotify_rm_watch cannot remove descriptor 209 for folder '/Content/Particles' (errno = 22, Invalid argument)
 73]LogDirectoryWatcher: Error: inotify_rm_watch cannot remove descriptor 206 for folder '/Content/Maps/Demonstration_sharedassets' (errno = 22, Invalid argument)
 73]LogDirectoryWatcher: Error: inotify_rm_watch cannot remove descriptor 204 for folder '/Content/Maps' (errno = 22, Invalid argument)
 73]LogDirectoryWatcher: Error: inotify_rm_watch cannot remove descriptor 209 for folder '/Content/Particles' (errno = 22, Invalid argument)
 73]LogAudioMixer: Display: Audio Buffer Underrun detected.
 73]LogCore: === Critical error: ===
Unhandled Exception: SIGSEGV: unaligned memory access (SIMD vectors?)

 73]LogCore: Fatal error!

This is still an issue with many marketplace & epic folders, even when testing on Windows in 4.25.4