I can’t run my game in standalone mode because I get this error
Can’t save
C:/Users//Documents/Unreal
Projects/Kaori/Content/Characters/UnitBase/Blueprints/BP_KaoriUnit_Base.uasset:
Graph is linked to object(s) in
external map. External Object(s):
/Engine/Transient Try to find the
chain of references to that object
(may take some time)?
every time it tries to save this blueprint. The strange thing is that if I try to run it in editor it works without problems.
Since this is the 3rd time that this has happened I tried to recreate this blueprint from scratch, resulting in the same error. I can’t figure out what exactly is causing the problem.
I had a similar issue and I was trying to Load some settings from a saved file in the Constructor part of the Blueprints. After I moved it to the Graph part it all worked fine.
In my first defect BP I tried to add a dynamic material to the skeleton mesh in the construction script. In my current try the construction script is empty.
That is all there is in this BP.
At first I thought that the skeletonmesh was damaged so i re-parent to defaultPawn → same problem. Maybe the custom enums are causing the problem. After I deleted the Team variable I was (once) able to package my current game to windows (play standalone from the editor still crashed). I readded the variable and reconnected all nodes and the build failed again. So I deleted the variable again but this time the build failed too.
Ok I found the cause of the error but still don’t know why it is causing the error.
In order to get a working BP again I had to:
Reparent my BP (character → actor → character)
Delete the Team variable (custom enum)
cooking → ok
If I now readd the team variable without connecting it to anything the cooking still works. If I then add the “set Team” as seen in s3.png and connect the team variable to the none slot seen in s2.png the cooking fails.
I had a problem similar to this. I found that I was unable to save out my blueprint and received a similar error. I was creating a derived UObject in a C++ class. Such objects are destroyed by the garbage collector which tracks them via the UPROPERTY() tag. I ended up with something similar to this in the class storing a UMyUObject pointer:
private:
UPROPERTY()
UMyUObject* MyObject;
Unfortunately, the problem arises when you have an empty UPROPERTY declaration which is private. When you attempt to save out the map, you’ll find that it throws a wobbler when attempting to reference any private properties not marked transient. You won’t have to have changed the asset for this to happen - just the scope of the variable in the C++ class.
The solution in my case was to mark the property as transient.
One extra thing… When the warning dialog appears, it actually displays a list of privately referenced objects. Engine/Transient is just another private object that is used internally. Engine/Transient won’t cause you a problem on its own. You only see it if your own property is broken.
Don’t know if that’s relevant or related to your problem, but I found this topic whilst searching for a solution to mine and someone else might too.
I have been having this bug for multiple weeks now. Every time I a create a project and start doing stuff in it, the error will eventually pop up the next day or so. No solutions from the web have helped at all. Please fix this, Epic. It renders the Engine as unusable for many people, including me.
