... but it was never saved as an export

So I’ve recently upgraded from 4.18 to 4.21, and now my cook step consistely says literally every single assent was not saved as an export, for example:

LogInit: Display: LogSavePackage: Warning: /Game/Developers//GunTagDev/GunTag_Test imported Serialize:/Game/_GAMEPLAY/GENERIC/GunTag/GunTag_TeamPedastal_BP.GunTag_TeamPedastal_BP_C:Box_GEN_VARIABLE, but it was never saved as an export.

This of course results in 100k warnings in the cook and is effectively making it impossible to find “real” cook warnings.

What does this message mean, and how can I get rid of it?

I will note that no, opening the asset in question (i.e. GunTag_TeamPedastal_BP in this case) and saving it again does not fix the warning. Ugh.

1 Like

Were you ever able to find a solution?

Sadly no. Effectively, I just have to ignore the results of a clean cook. Doing iterative may sometimes reduce the count of warnings, but if I resave anything it comes back until the next iterative cook. :shrug:

Thanks for your reply. If we figure something out on our end, I’ll update this thread.

Check your black list for package. Maybe you forbade some folders for package.

4.24.3, having this for a few assets, including maps.

UATHelper: Packaging (Windows (64-bit)):   LogSavePackage: Warning: /Game/Run/Components/Spawn_System/Blueprints/Character/BP_Respawn_Point imported Serialize:/Engine/EditorMaterials/TargetIconSpawn, but it was never saved as an export.

PackagingResults: Warning: /Game/Run/Components/Spawn_System/Blueprints/Character/BP_Respawn_Point imported Serialize:/Engine/EditorMaterials/TargetIconSpawn, but it was never saved as an export.

Old post but pujtting this here incase someone needs in,

Turn This Of inside Project settings

6 Likes

Thanks, that fixed it for me, good thinking

1 Like

Oh no, page doesn’t exist. Can you post the solution again please?

Just hit this too, please repost solution!

I think I unchecked the “exclude editor content” in project launcher and project settings and it worked.

2 Likes

This worked for me

lehuan5062
I think I unchecked the “exclude editor content” in project launcher and project settings and it worked.

1 Like

sorry for necroing a question from 4 years ago but let this be here for anyone who might come across this in future
in my case the warning was made by assets which had a really long file path.
reducing file path ( either by reducing number of character in their name or moving them higher in folder hierarchy) solved the problem

1 Like

I was also having this issue, came across this thread hoping to find an answer but for me, i worked out that i was referencing a texture in a folder that i had told not the be cooked or looked in… so i just made a copy of the texture some where else and fixed the references and that fixed it for me…

Thank you. I needed this.

1 Like