I keep getting the error above when I try to package my little game into something I can send to people. I’m really new to UE4, is this a fixable error? Also, I keep getting tons of the following error in my output log:
[2016.01.21-00.00.15:400][ 0]LogUObjectGlobals:Warning: Failed to load '/Game/ExampleContent/Blueprints/Meshes/SM_Button': Can't find file '/Game/ExampleContent/Blueprints/Meshes/SM_Button'
[2016.01.21-00.00.15:400][ 0]LogLinker:Warning: Can’t find file for asset ‘/Game/ExampleContent/Blueprints/Meshes/SM_Button’ while loading NULL.
How can I fix these as well? Thanks! I had to zip the content log, it was 6.7 MB and it seems the forum won’t let me upload something that large
Please delete your DerivedDataCache, Intermediate and Saved folder from your project. I would also double check your files that the output logs are saying the editor cannot find. Once you’ve gone through these files and made sure they’re there, try to package again and provide me with the new logs.
I was actually able to fix that particular error by deleting the /content/contentexamples/animationdemo folder in Windows Explorer. The error always came up when it got to that folder during the packaging, so it must have been causing the problem. Deleting it from within UE4 also crashed the program, so it had to be done from Windows.
Now, it’s giving me a different error:
002Program.Main: ERROR: AutomationTool terminated with exception:
002Program.Main: ERROR: Exception in AutomationScripts.Automation: Cook failed.
Does that have something to do with the build configuration?
So when I deleted that same folder, I now cannot cook or package my project. It too gives errors like this. I believe that you deleting that specific folder ‘AnimationDemo’ has actually caused more trouble.
Could you restore that folder and just simply delete the DerivedDataCache (if you have one), Saved and Intermediate folder? Once you’ve done that, could you please try again and let me know what your new logs say.
We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.