I’ve attempted to research the issue though I was unable to find any hits. How should I go about correcting this?
OS: Windows 7, 64bit
Engine version: 4.0.2
VS was installed after UE4’s complete installation.
I’ve installed various other versions of VS throughout time though they were uninstalled prior to installing UE4 and VS Exprs. 2013.
No conflicts noted during installation.
huh… that’s actually what it was set to by default, but I changed it to the above because that’s what I thought your answer below indicated. Anyway, now I changed it back to “C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools”, and the option is still grayed out
Ah, no, I meant that the following should be a valid path (for VS2013 Express anyway):
So to resolve that out:
“C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7/…/IDE/WDExpress.exe”
And to collapse it down:
“C:\Program Files (x86)\Microsoft Visual Studio 12.0\IDE\WDExpress.exe”
Which is correct
Are you building from source? If you look in the UE4 source there will be file called VSAccessorModule.cpp, and inside that is a function called CanRunVisualStudio. I believe (hope) that is the function that controls the enabled state of that menu item.
Could you see what it’s returning in your case? Thanks.
I only have the header file (VSAccessorModule.h) - I’m not building from source, I just downloaded “UnrealEngineInstaller-1.0.0-2039063” and installed Unreal Engine through the Launcher. On my Mac it worked fine to just download and install that way. I guess I’ll try building from source and see if that makes a difference. Thanks for all your help man
Yes, the path is accessible. I found the VSAccessor module you mentioned though unfortunately I’ve not had much time to familiarize myself with the language enough to debug for a result. Is there an alternative to further investigating this?
The reason it wasn’t working for me is because the environment variable was pointing to “…\Microsoft Visual Studio 12.0\Common7/tools/”, though the directory does exist, the executable simply isn’t there.
Why it was pointing there to begin with is beyond me, but that was my findings.
I set the environment variable to point toward “”…\Microsoft Visual Studio 12.0\Common7/IDE/" as Jamie suggested and it now works as intended.
That really should be pointing to the Tools folder, it will work where you have it but may break other things inside Visual Studio that try and access things from within that folder.
It will go one level up from wherever that environment variable points to, then down into IDE, so having it set to “Microsoft Visual Studio 12.0\Common7/IDE/” becomes “Microsoft Visual Studio 12.0\Common7/IDE/…/IDE”, which resolves to “Microsoft Visual Studio 12.0\Common7/IDE/”.
By that logic “Microsoft Visual Studio 12.0\Common7/Tools/” becomes “Microsoft Visual Studio 12.0\Common7/Tools/…/IDE” which also resolves to “Microsoft Visual Studio 12.0\Common7/IDE/”.
Note that you need to restart Visual Studio after changing an environment variable for the changes to have any effect.
For me it didn’t work, because for some reason my Visual Studio 2013 Express instalation didn’t make a WDExpress.exe, but a VSWinExpress.exe application. Copying and renaming proved that it isn’t VSWinExpress.exe what I’m looking for.