Cooking broken 4.12

Hi,

i am running build on pretty bad machine (works as build server of some sort). It has duo core processor and everytime i try to cook project it just hangs up.

It does not use any resources and according to visual studio its main thread is just waiting.
Packaging work fine on my 8-core

I tried this fix. UE 4.11 Hangs Cooking on Macbook Pro - Programming & Scripting - Unreal Engine Forums
It did work on 4.11 but on 4.12 it does not help at all :frowning:link text

I am attaching Dxdiag and this is snippet of logs

CommandUtils.Run: Run: Took 2,2341283s to run UnrealBuildTool.exe, ExitCode=0
CommandUtils.Run: Run: C:\UnrealEngine\Engine\Binaries\DotNET\UnrealBuildTool.exe Murnatan Win64 Development -Project=C:\Programy\Murnatan-code\Murnatan.uproject  C:\Programy\Murnatan-code\Murnatan.uproject  -remoteini="C:\Programy\Murnatan-code" -noxge -generatemanifest -NoHotReloadFromIDE -ignorejunk
UnrealBuildTool: Performing full C++ include scan (building a new target)
CommandUtils.Run: Run: Took 3,4411968s to run UnrealBuildTool.exe, ExitCode=0
CommandUtils.Run: Run: C:\UnrealEngine\Engine\Binaries\DotNET\UnrealBuildTool.exe Murnatan Win64 Development -Project=C:\Programy\Murnatan-code\Murnatan.uproject  C:\Programy\Murnatan-code\Murnatan.uproject  -remoteini="C:\Programy\Murnatan-code" -noxge -NoHotReloadFromIDE -ignorejunk
UnrealBuildTool: Creating makefile for Murnatan (UnrealBuildTool.exe is newer)
UnrealBuildTool: Target is up to date
CommandUtils.Run: Run: Took 7,7904454s to run UnrealBuildTool.exe, ExitCode=0
CommandUtils.Run: Run: C:\UnrealEngine\Engine\Binaries\DotNET\UnrealBuildTool.exe MurnatanServer Win64 Development -Project=C:\Programy\Murnatan-code\Murnatan.uproject  C:\Programy\Murnatan-code\Murnatan.uproject  -remoteini="C:\Programy\Murnatan-code" -noxge -generatemanifest -NoHotReloadFromIDE -ignorejunk
UnrealBuildTool: Performing full C++ include scan (building a new target)
CommandUtils.Run: Run: Took 3,3881935s to run UnrealBuildTool.exe, ExitCode=0
CommandUtils.Run: Run: C:\UnrealEngine\Engine\Binaries\DotNET\UnrealBuildTool.exe MurnatanServer Win64 Development -Project=C:\Programy\Murnatan-code\Murnatan.uproject  C:\Programy\Murnatan-code\Murnatan.uproject  -remoteini="C:\Programy\Murnatan-code" -noxge -NoHotReloadFromIDE -ignorejunk
UnrealBuildTool: Creating makefile for MurnatanServer (UnrealBuildTool.exe is newer)
UnrealBuildTool: Target is up to date
CommandUtils.Run: Run: Took 7,34242s to run UnrealBuildTool.exe, ExitCode=0
CommandUtils.Run: Run: C:\UnrealEngine\Engine\Binaries\DotNET\UnrealBuildTool.exe BootstrapPackagedGame Win64 Shipping   -noxge -generatemanifest -NoHotReloadFromIDE -ignorejunk
CommandUtils.Run: Run: Took 1,3160764s to run UnrealBuildTool.exe, ExitCode=0
CommandUtils.Run: Run: C:\UnrealEngine\Engine\Binaries\DotNET\UnrealBuildTool.exe BootstrapPackagedGame Win64 Shipping   -noxge -NoHotReloadFromIDE -ignorejunk
UnrealBuildTool: Creating makefile for BootstrapPackagedGame (UnrealBuildTool.exe is newer)
UnrealBuildTool: Target is up to date
CommandUtils.Run: Run: Took 1,5110868s to run UnrealBuildTool.exe, ExitCode=0
Project.Build: ********** BUILD COMMAND COMPLETED **********
Project.Cook: ********** COOK COMMAND STARTED **********
CommandUtils.RunCommandlet: Running UE4Editor Cook for project C:\Programy\Murnatan-code\Murnatan.uproject
CommandUtils.RunCommandlet: Commandlet log file is C:\UnrealEngine\Engine\Programs\AutomationTool\Saved\Cook-2016.08.05-12.39.59.txt
CommandUtils.Run: Run: C:\UnrealEngine\Engine\Binaries\Win64\UE4Editor-Cmd.exe C:\Programy\Murnatan-code\Murnatan.uproject -run=Cook  -TargetPlatform=WindowsNoEditor+WindowsServer -fileopenlog -unversioned -abslog=C:\UnrealEngine\Engine\Programs\AutomationTool\Saved\Cook-2016.08.05-12.39.59.txt -stdout -FORCELOGFLUSH -CrashForUAT -unattended
UE4Editor-Cmd:
UE4Editor-Cmd: LogInit:Display: Running engine for game: Murnatan

Hello,

Does this occur when cooking a clean, blank project, or only on your specific project?

Hi i did some more testing and this is an issue when i try to package game whille specific plugin is enabled, so the duo core fix still works.

So thats solved i quess for now and i will try to contant developer of plugin for further examination.

Thanks