Cooking fails sometimes without changing anything

Development Platform & Builds
, , ,
1

Hello,
when cooking our game it usually requires to run the cooking command 2-3 times before it successfully cooks the game. Also, the amount of warnings changes with each time we are cooking the game. How can i find out why exactly it fails ? When it runs through successful i’ll receive the following warnings which i don’t know how to fix.

LogText:Warning: Saving FText “PLACEHOLDER” which has been initialized from FString at cook time resave of source package FBufferArchive

  • Resaving does NOT fix the issue. Tried it multiple times and the warning keeps coming back.

LogBlueprint:Warning: USimpleConstructionScript::FixupRootNodeParentReferences() - Couldn’t find inherited parent component ‘1PMesh’ for ‘StaticMesh’ in BlueprintGeneratedClass ‘REINST_BP_Pistol_C_375’ (it may have been removed)

  • How do i fix this ?

I usually have to try cooking the game for 3-4 times until it will finally run through. I switched to cooking it from commandline using a .bat file because i thought it might be an issue with the editor but the result is the same. The batch file will not cook the game until i at least tried 3-4 times. Sometimes it cooks it right away on the first attempt but normally it is rather between the 3 to 4 times range.

I’m using 4.12.5 and i cannot update to 4.13 yet as i’m using the LE Standard Lib. from the Marketplace. The author submitted the update but it has not been confirmed by Epic yet so the latest version on the store front is still 4.12.

2

,

Please delete your Intermediate and Saved folders from your project folder. Once you’ve done that, open the project back up in the editor and try to package. If it fails, please upload the output error logs as a .txt file with your next response. Hopefully with those logs we can narrow down what’s going on within your project.

Thanks!

3

Hi ,
problem went away without doing that. Not sure why but since a few days it cooks on the first try again. I think it’s UMG related as all i did was adding a new UI element to our project and adding it to our root UMG widget. I guess this can be closed now, not possible to figure this out.

4

Thanks for giving an update. If you notice specific steps are causing the issue, please report it to us for further testing.

Thanks!