Hi, this is a bug i’ve been ignoring on and off for a while now, i’ve been trying to fix it for days now and i’m wasting so much time. My game needs to be released for a playable build on steam before the next 4 days. Can anyone help me fix this problem when I package?? After 2-3 seconds of clicking package project i get the error.
- I’ve tried packaging other projects fine, only this project does not work.
- I’ve tried updating… causes issues.
- I’ve tried re-install ue4 and visual studio.
I’ll attach the log full of errors.
[link text][1]
113010-uat_log.txt (7.65 KB)
error says you have a duplicate key input. if its blueprint then could be duplicate trigger event that conflicts with itself. you can right click on blueprint boxes and find references to look for duplicates. could also be some object named the exact same as some other object.
ok your new log file is loaded with compiler errors. did you try to package before compiling? open a blueprint and hit the compile button and it should give you a list of any errors at the bottom with links to each specific error
Thank you i managed to fix it by changing my project to a new clean fresh project with only blueprints and removing all C++ from it.[link text][1] BUT… i’m getting a new error when packaging… ill attach the error log… please help.
113171-uat_log.txt (4.88 MB)
Any blueprint? I’ve tried several and they all compile correctly. ALSO everything is blueprint.
Yes i have actually. I’m still having trouble.
Anyone know what i can do to fix all these errors?
Anyone know what i can do to fix all these errors?
Did you try any of the suggestions that I provided previously?
Yes. nothing worked, i get
UE4Editor-Cmd: [2016.11.11-02.40.48:033][ 0]LogInit:Display: Failure - 853 error(s), 16267 warning(s)
everytime.
Also i managed to first the first error i had (the same key error) by deleteing the .target file. But the new error i receive is an unknown cook error and the under it, is
UE4Editor-Cmd: LogInit:Display: Failure - 853 error(s), 16267 warning(s)
I managed to fix the issue by making a new project and tracking the errors down one by one. I’d move a folder from assets one by one to the new project until i recieved the errors and i would work around it.