Hello Everyone,
I’m creating a Package for my game which’ll release as a Patch. However I’m receiving an error in my code when using Windows PowerShell. (it’s below)
**************** COOK COMMAND STARTED **********
ERROR: Missing C:\Users\meers\Documents\Attempt 4\UnrealEngine\Engine\Binaries\Win64\UE4Editor-Cmd executable. Needs to be built first.
(see C:\Users\meers\Documents\Attempt 4\UnrealEngine\Engine\Programs\AutomationTool\Saved\Logs\Log.txt for full exception trace)
AutomationTool exiting with ExitCode=1 (Error_Unknown)
BUILD FAILED******
I followed the path and opened up the UE4Editor-Cmd.exe and it opens up fine. Has anyone come across this issue before or know how to resolve it? If so, can you please help?
Thank You Kindly.
Hmm, maybe you are running the command from the wrong directory? In the past I have had the bulid batch files behave weirdly with relative paths.
It seems strange that the UE4 exe binaries would be in your Documents folder (it is installed by default to C:\ProgramFiles) unless you are using a source engine build or changed where the engine gets installed. Try running the command from C: or from the Engine directory.
Ah yes sorry, I forgot to mention, this version of UE4 is for a specific console development and is built from source.
(I asked this same question on a forum just for development on that system but I haven’t received any replies)
Also the reason I’m running the command from the Batch Files folder from within the Source Engine Directory is because I’m following a guide that instructs so. This is literally the final step so it’s frustrating why it’s bringing up this error.
Ya that should be the correct place to run it from.
One issue I have encountered is that the path name is too long which causes things to break, so I usually put my engine source builds as close to the root as possible. I am not sure if that is an issue here; You would likely get a different error, and I seem to recall seeing somewhere that the path name length issue had been resolved.
Ya I could try moving the engine to C:/Program Files and see if that works.
Did you manage to find a solution for this?