Packaging a Windows game from Editor built from sources produces an UE4Game.exe placed in [project dir]\WindowsNoEditor\Engine\Binaries\Win64 folder which application is raises a Message window (image attached) then quits.
Renaming the UE4Game.exe to TappyChicken.exe gets the project run properly.
Hi sch5,
Have you attempted re-downloading the project to see if it was a corrupted or missing file? Further does this only happen with or does it happen with other projects as well?
Thank you!
I’ll make that change, we are trying to make each question easy for users to find. Thank you for your feedback!
Hi sch5,
While I could not reproduce your bug, I am putting in a bug report with this post attached to it so we can address this issue. Thank you and have a great day!
This was a bug with the source build in 4.0, and only manifests when packaging a content-only project.
The version of the editor that we ship through the launcher is compiled using the UE_ROCKET define, which adds -Rocket to the editor’s command line. We use this parameter to control behaviors that are common to people who aren’t building the editor themselves, and accidentally lumped support for packaging of content-only projects into this category.
We’ll have it fixed in the next release.
Thanks for the answer, I was having the same problem and asked it a few days ago hereanswers.unrealengine.com/questions/22527/editor-build-from-sources-packaging-does-not-yield.html
Cheers,
You should just be able to grab the latest Engine/Source/Programs/AutomationTool/Win/WinPlatform.Automation.cs file from the master branch.
Oh, nice to know!
I had a look in the whole C++ code base, searching for the ‘UE_ROCKET’, then for ‘IsRocket()’…
So, many thanks for your answer.
I made a small backport patch for it there, in case anyone else need it for 4.0.x :
https://github.com/EpicGames/UnrealEngine/pull/50