I’ve seen this error getting thrown before when someone had child actor BP’s. Do you have any in your build?
Hello all,
Got trouble opening my project.
It started yesterday, had crashes at opening, I hunted down the blueprint files to find out which one was causing the trouble. After finding the bad file, I rolled back to an older version of it from the backup folder. Finally I could open it.
Been working on it yesterday, recreating what I have lost except the part that i suspect to be the cause of the crashes.
Was working all fine, yesterday evening I saved and close.
Today I try to open my project again, and got crashes again.
What i did yesterday in that blueprint was different to what i suspect was making the crashes occurring the first time.
Yet, again I can’t open and might need to roll back once more … making any progression on my project impossible.
I have been looking at the log, hoping to find a clue, but today same as yesterday : no clue for me.
here some log info :
MachineId:
EpicAccountId:
That a good clue, because one of the work I have redone yesterday is that my character player do get a child actor (component) at some point … gonna try a new project with just that and see.
Added a child actor to third person character for test, save, quit, start, it open without problem. I guess it might be a bit more that just the child actor. Perhaps the way I attached it in my project (on collision) …
Wondering why it work so well once the function is built, yesterday. But then can’t open the project the next day.
Since it’s potentially a child actor. Can you temporarily delete the BP that the parent tries to spawn as a child actor? See if the project loads.
Have rolled back again the character blueprint file (the one adding the child to itself)
Could load.
Adding one feature at the time, saving, closing, opening again.
Found the guilty function.
Add child actor component.
It’s fired by a custom event, but nothing in my project ever fire that event. So just having the node ACAC seems to make the project crash at loading.
Is there any way I can add a child actor without the fear of corrupting my file ?
After few test :
Add actor child component alone (not connected, not configured) = ok
Add actor child component alone (not connected, configured) = can’t open project
Add actor child component alone (not connected, configured with another empty actor) = ok
So the child I was using was making the mess once it was a child component.
Since I only need it for visual purpose, I created a clone of that actor with an empty graph event.
Something in it was making a mess at loading time (event tho it was working well in the editor before closing it)
I guess problem is solved for me. Thanks HighlySpammable for your insight.