Packaging Failed (Automation Tool Unable to Run Successfully)
I'm trying to package my project for Windows, but the packaging fails every time. I've tried several different versions of the project with different conditions, but all fail. I'm basically at a loss, though it might be related to the "AutomationTool was unable to run successfully" error. Based the searches I've done, this seems to be an issue a lot of people have, but as far as I can tell there's no clear solution.
I've attached my complete output log for my most recent package attempt, as well as specific error lines I found that might be relevant. If anyone can shed some light on what my issue is, I would greatly appreciate it.
I'm using Version 4.6.1 of the engine. I've tried multiple times to port my project to other versions, but have run into significant issues each time, so I'd like to finish with this version if at all possible.
asked Aug 24 '15 at 08:38 PM in Packaging & Deployment
In order to better assist you, I would like to ask the following questions:
After reviewing your logs, I noticed that the editor is having trouble locating a 'Custom Channel Name = Weapon'; has this been renamed, deleted or moved? You'll need to look through your project to locate this file, or remove the reference where it's being called from within your UI.
I would not worry about the 'Roboto-Italic.ttf' error unless it's also causing your project not to package. If it happens to cause an issue for you, delete the binary, saved and intermediate folders from your project and then restart your computer.
Failed to begin reading directory changes for C:/Users/Chris/Documents/Unreal Projects/Propulsion/Binaries/Win64 was also caught by the packaging process. Did this file get moved, deleted or renamed? If so, could you please locate that file and ensure it's in the correct location? You can also right-click in the Content Browser and 'Fix up redirectors'.
The last error that was seen is that the editor failed to find object 'Object None.SM_SkySphere'. Please verify that this object is still within your project, you may want to delete the object from your project viewport and replace it with a new version of the object. If the file was ever renamed, that could also be the issue that you're running into, so replacing it within the viewport should fix that. I'd also check any blueprint that may be calling this object and check to make sure the names match up.
After you've done the following, please save your project and restart your computer, then try to package again. If you run into any further packaging errors, please upload the logs again and I will take a look at them.
Looking forward to hearing back from you, thanks!
answered Aug 26 '15 at 02:54 PM
Have you tried creating a copy of your project and moving it to 4.8.3? If so, were you able to package with that version of the engine?
So when you package for Mac with the same exact project, you run into no problems? When you say that you copied all your necessary files over, does that mean you've migrated your project? If not, go back into your project and try to migrate it to a new project and see if you run into the same issues.
You should not have any trouble based solely on the project being created on a Mac and moved to Windows. The projects are still compatible.
The binaries folder shows up once you package the game for instance, I've packaged this one project for Android, HTML5 and iOS.
Keep me updated, thanks!
answered Aug 27 '15 at 02:37 PM
Similar problem here and solved it migrating the entire proyect to a new empty one. thanks! :)
answered Jan 22 '18 at 10:01 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here