I’m not exactly sure where to put this, I’m coming from the Beta so I did have that installed on my pc previously and have a project built with it.
I can not start new C++ projects from the Editor, only Blueprint projects. I have installed several versions of Visual Studio. I thought VS Ultimate 2013 may have been the problem so I installed the Express version, but same issues.
I took a project file from a new BluePrint project created from the Editor and put it in my old project and tried to generate the Visual Studio files. Here is the console output that I got, after the launcher ran and said syncing.
Setting up Rocket project files…
The system cannot find the path specified.
Discovering modules, targets and source code for project…
Binding IntelliSense data… 100%
Writing project files… 0%
UnrealBuildTool Exception: ERROR: SetEnvironmentVariablesFromBatchFile: BatchFil
e D:\VS2013Preview\Common7\Tools../…/VC/bin/x86_amd64/vcvarsx86_amd64.bat does
not exist!
GenerateProjectFiles ERROR: UnrealBuildTool was unable to generate project files
.
Press any key to continue . . .
Thanks for the link to your thread. I don’t think that can work for me because I wasn’t compiling the engine. I was just trying to use the build the launcher pulled down. Unless it’s by intention that you can’t make C++ projects from that build, but I don’t understand why the options for creating C++ projects would be in the Editor then.
I found and fixed the issue. My environmental variable VS120COMNTOOLS was pointing to a folder called VS2013Preview … I think it was left over from the Release Candidate I had installed for VS 2013 last year. I corrected the Environmental Variable to point to C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools
I can now create new C++ projects from the Editor.
can you explain it more detailed, for a noob like me, because it seems that i have the same problem, it starts to compile c++ project files and then i get this error : UnrealBuildTool was unable to generate project files
There is another thread, that linked too. There is a code change needed if you are using a non-Express version of Visual Studio.
I had previously installed the pre-release of Visual Studio 2013 and in my Win7 Environmental Variables, it was set wrong.
From your start menu, right click computer, select properties.
Select Advanced Settings.
Click Environment Variables.
Scroll down near the bottom of System variables and select Edit on VS120COMNTOOLS, look at the path it’s pointing to, then look in explorer to see if that is actually pointing to the correct Visual Studio folder.