Launch Game says it cannot find compiler

When trying to launch any Custom Game, i get the following error in the Logs:

LogPlayLevel:Display: BuildCommand.Execute: ERROR: BUILD FAILED
LogPlayLevel:Display: Program.Main: ERROR: AutomationTool terminated with exception:
LogPlayLevel:Display: Program.Main: ERROR: Exception in AutomationTool: You are attempting to compile on a machine that does not have a supported compiler!
LogPlayLevel:Display: Stacktrace:    bei AutomationTool.UE4Build.Build(BuildAgenda Agenda, Nullable`1 InDeleteBuildProducts, Boolean InUpdateVersionFiles, Boolean InForceNoXGE, Boolean InForceNonUnity, Boolean InForceUnity)
LogPlayLevel:Display:    bei Project.Build(BuildCommand Command, ProjectParams Params, Int32 WorkingCL)
LogPlayLevel:Display:    bei BuildCookRun.DoBuildCookRun(ProjectParams Params)
LogPlayLevel:Display:    bei BuildCommand.Execute()
LogPlayLevel:Display:    bei AutomationTool.Automation.Execute(List`1 CommandsToExecute, CaselessDictionary`1 Commands)
LogPlayLevel:Display:    bei AutomationTool.Automation.Process(String[] CommandLine)
LogPlayLevel:Display:    bei AutomationTool.Program.MainProc(Object Param)
LogPlayLevel:Display:    bei AutomationTool.InternalUtils.RunSingleInstance(MainProc Main, Object Param)
LogPlayLevel:Display:    bei AutomationTool.Program.Main()
LogPlayLevel:Display: Program.Main: ERROR: You are attempting to compile on a machine that does not have a supported compiler!
LogPlayLevel:Display: copying UAT log files...
LogPlayLevel:Display: RunUAT.bat ERROR: AutomationTool was unable to run successfully.
LogPlayLevel:Display: BUILD FAILED

Funny enough, Sample projects can be launched without any problem, so this must be some path issue with my custom projects; any hint on where i can look to resolve this?

Hello indygoof,

looking at this part, “You are attempting to compile on a machine that does not have a supported compiler!” which would indicate that you need Visual Studios 2013. Can you confirm for me that you have VS2013?

-Max B.

Hi,

jep, i got VS 2013 Express installed. Actually, i’m starting the Editor from VS most of the time.

As already stated, the Samples launch without a problem, the problem exists with just any custom projects that i got.

Cheers,

Same problem for me. I have VS2013 and build project. But I can not package it.

i’ve got same problem, any solution?

LogPlayLevel:Display: Program.Main: ERROR: Exception in AutomationTool: You are attempting to compile on a machine that does not have a supported compiler!

For me problem was in non-latin characters in path “C:\Users\AppData\Roaming”. I recreate user with latin name and all works.

Still happens with 4.1.1; Also tried reinstalling VS 2013 Express. Checked the Environment Variables if something was messed up (Though, VS can actually be found by the Editor, so that should not be a problem).

Also, when trying to launch the Editor NOT from VS directly, but by starting it from the Desktop Link it tells me that my Game-Module is not up-to-date. Though, i recompiled it multiple times with 4.1.1, also did a whole cleanup, regenerated Project Files.

Additionally, since this may help you in finding the cause, whenever i add code to the project through the Editor (aka, whenever i regenerate my project files), the Include- and Library- Paths in VS are reset to empty, and i always have to manually set them to inherit for it to compile again.

Cheers,

@indygoof & @Daijobu

We apologize for the lack of follow up on this issue. Do you have any update on it? Is the problem still occurring for you, or were you able to find a solution?

Definitely please let us know if you were never able to get the editor to run, and we will be glad to discuss our options with you.

We are marking this as “resolved” for tracking purposes, until we hear back from you.

Thanks

The editor did actually run all the time, and playing inside the editor was no problem as well.
I only had a problem when trying to launch the game or package it.

Though, after my SSD crashed horribly i needed to reinstall everything from scratch, and since then, everything is working correctly. I guess this had something to do with the system paths not being setup correctly or read correctly for some reason.

Cheers,

I’m currently having the same problem, I have visual studio 2013 professional installed and I don’t have the case of non latin character.

So I got this recently as well, But I managed to track down what the actual issue is for me. That being with setting up the .Net vars:

Snippet from my log:

MainFrameActions: Packaging (Windows): WindowsHostPlatform.SetFrameworkVars: Setting .Net Framework environment variables.
MainFrameActions: Packaging (Windows): WindowsHostPlatform.SetFrameworkVars: Supports64bitExecutables=True
MainFrameActions: Packaging (Windows): WindowsHostPlatform.SetFrameworkVars: WindowsPlatform.CompilerVisualStudio2013
MainFrameActions: Packaging (Windows): WindowsHostPlatform.SetFrameworkVars: WindowsSDKDir=C:\Program Files (x86)\Windows Kits\8.1\
MainFrameActions: Packaging (Windows): WindowsHostPlatform.SetFrameworkVars: BaseVSToolPath=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools
MainFrameActions: Packaging (Windows): WindowsHostPlatform.SetFrameworkVars: Setting VS environment variables via C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\..\..\VC\bin\x86_amd64\vcvarsx86_amd64.bat.
MainFrameActions: Packaging (Windows): InternalUtils.SafeDeleteFile: SafeDeleteFile C:\Users\evan\AppData\Local\Temp\HarvestEnvVars.txt
MainFrameActions: Packaging (Windows): InternalUtils.SafeFileExists: SafeFileExists C:\Users\evan\AppData\Local\Temp\HarvestEnvVars.bat=True
MainFrameActions: Packaging (Windows): CommandUtils.Run: Run: C:\Users\evan\AppData\Local\Temp\HarvestEnvVars.bat 
MainFrameActions: Packaging (Windows): HarvestEnvVars: 
MainFrameActions: Packaging (Windows): HarvestEnvVars: D:\Perforce\evan_Evan-PC\Submerged_Main\Engine\Binaries\DotNET>call "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\..\..\VC\bin\x86_amd64\vcvarsx86_amd64.bat" 
MainFrameActions: Packaging (Windows): HarvestEnvVars: ERROR: Cannot determine the location of the VS Common Tools folder.
MainFrameActions: Packaging (Windows): HarvestEnvVars: 
MainFrameActions: Packaging (Windows): HarvestEnvVars: D:\Perforce\evan_Evan-PC\Submerged_Main\Engine\Binaries\DotNET>set  1>"C:\Users\evan\AppData\Local\Temp\HarvestEnvVars.txt" 
MainFrameActions: Packaging (Windows): CommandUtils.Run: Run: Took 0.665038s to run HarvestEnvVars.bat
MainFrameActions: Packaging (Windows): CommandUtils.SetEnvVar: SetEnvVar FrameworkDir=
MainFrameActions: Packaging (Windows): CommandEnvironment.SetupBuildEnvironment: SetFrameworkVars failed. Assuming no compilation capability.
MainFrameActions: Packaging (Windows): CommandEnvironment.SetupBuildEnvironment: CompilationEvironment.HasCapabilityToCompile=False
MainFrameActions: Packaging (Windows): CommandEnvironment.SetupBuildEnvironment: CompilationEvironment.MsBuildExe=
MainFrameActions: Packaging (Windows): CommandEnvironment.SetupBuildEnvironment: CompilationEvironment.MsDevExe=

This line specifically is of interest:

MainFrameActions: Packaging (Windows): HarvestEnvVars: ERROR: Cannot determine the location of the VS Common Tools folder.

It then flicks “HasCapabilityToCompile” to false, and refuses to package.

One solution seems to be HERE, however It doesn’t seem to work for me. (System32 is already in my PATH var)

Hopefully this helps to fix the issue. (If it’s the same issue everyone else is seeing.)

It would also explain why @indygoof’s worked after re-installing his system.

Cheers.

EDIT: I, like @DrunkCompiler don’t have the latin character issue.

EDIT 2: This solution worked for me. ( Was directly underneath the previous answer. XD ) Hope this helps someone.
Below is what I ended up with in the vcvars bat, feel free to edit:

:: NOTE: these have been added manually!
@SET WindowsSdkDir=C:\Program Files (x86)\Windows Kits\8.1\
@SET WindowsSDK_ExecutablePath_x86=C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\
@SET WindowsSDK_ExecutablePath_x64=C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\x64\
@SET VS120COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\
@SET VSINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 12.0\
@SET VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\
@SET FSHARPINSTALLDIR=C:\Program Files (x86)\Microsoft SDKs\F#\3.1\Framework\v4.0\
@SET FrameworkDir32=C:\Windows\Microsoft.NET\Framework\
@SET FrameworkVersion32=v4.0.30319
@SET FrameworkDir64=C:\Windows\Microsoft.NET\Framework64
@SET FrameworkVersion64=v4.0.30319
@SET Framework40Version=v4.0

:: @call :GetVSCommonToolsDir
:: @if "%VS120COMNTOOLS%"=="" goto error_no_VS120COMNTOOLSDIR
:: 
:: @call "%VS120COMNTOOLS%VCVarsQueryRegistry.bat" 32bit 64bit