Visual Studio will use DXC.EXE automatically when Shader Model 6 is selected for the HLSL Property Page configuration. For Shader Model 6, you use DXC.EXE instead, which is documented in Using dxc.exe and dxcompiler.dll. Has anyone encountered this problem? Are there any known solutions? Please feel free to ask for more information.Įdit: I forgot to add, I'm using Unity 3.5.6 and Windows 8 64 bit.This topic covers the FXC.EXE compiler used for Shader Models 2 through 5.1.

Before I switched to Windows 8, I've used VS 2012 express with Unity in Windows 7 without encountering this behavior. I can simply open the solution once and navigate to exceptions manually, but that is a bit annoying. The real problem is that the same thing happens if I want to open a script from Unity's console, attempting to navigate to an error message results in unloaded solution and a new VS2012 launched. But, even after doing that, double-clicks in project view still result in a new VS2012 being launched and solution not being loaded. If I open the solution file from explorer or click Assets > Sync MonoDevelop Project it loads the solution succesfully. This results in code-suggestions not working properly and each double-click in project view launching a new VS2012. When using Visual Studio 2012 Express with Unity in Windows 8, there is a problem I encountered:ĭouble-clicking a script in Unity's project view opens it in VS2012 without loading the solution. Greetings, fellow Unity developers! My google skills have failed me so I'm here to ask a question.

Vs2012