Open samizzo opened 7 years ago
Same. Visual Studio 2017 with Nsight installed...no-go. Uninstalled Nsight...good-to-go.
Interestingly, I just installed the latest patch of VS2017 (15.2 26430.16) and NShader stopped working. I uninstalled/reinstalled NShader and still no-go and it wasn't even showing up in Fonts and Colors anymore, despite VS reporting that it was installed and enabled. I tried disabling/re-enabling, restarting VS, and none of that worked.
So, I decided to give up on NShader, reinstall Nsight, and NShader started working again! :O
NShader seems to be the best solution still for GLSL in VS2017, so here's to hoping it lasts!
I have Visual Studio 2015 (with Nsight) and Visual Studio 2017. NShader just working on Visual Studio 2017. When using Visual Studio 2015 (with Nsight) to open the GLSL file, it’s just a normal text editor. But on my other computer only Visual Studio 2015 (with Nsight), NShader can work.