Assertion failed : Indirection function

Development Programming & Scripting Blueprint
,
1

So, I have been working on a project over a month now. But this error start to occur out of no where since a week ago. Whenever I would make any change to the character BP it would crash the whole engine with error stating :

Assertion failed: Indirection.Function->GetReturnProperty() [File:D:\build++UE5\Sync\Engine\Source\Runtime\Engine\Private\PropertyAccess.cpp]
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
kernel32
ntdll

I am uncertain, but about the same time my harddrive died on me. So could it be trying to fetch some dependency from the dead drive? I did try making a new BP character but it would occur again that is why I am assuming it is looking for something in that non-existing drive.
I would like bit clarification before I start working on another fresh project as a fix, Cuz I have literally put in too much work here.
Let me know fif anyone found any solution to this.

2

Hey!
For me the problem was in “Predict distance function” in Animation BP. When I deleted it - error has gone! Hope it will help.

One guy from the internet with the same problem said this:

“In my experience, this sometimes happens if the engine gets itself out of order when starting the game, and tries to link the layers from an anim blueprint to the main one before the main one is loaded. I’m not sure if there’s a simple way to validate if an anim instance is loaded, but if there is, checking that before linking layers in the characterBP should fix the issue, it hasn’t been a prominent issue for me, so I haven’t looked into it yet, so the best I can do is tell you the direction I plan on looking if I encounter the issue again. What version of the engine are you using? I believe I encountered this issue in 5.1, but I think I haven’t run into it in 5.2+, switching versions could resolve the issue, but I could just be lucky and the bug might still be in 5.2+.”

3

Alright after smashing my head around for ages, figured out it happens due to thread-safe variables being used for general purpose graph functions. I.e., using same variables for thread-safe functions and non-threadsafe functions.