I find Nsight 3.2.1 in Visual Studio 2012 nearly unusable to debug longer shaders as it slows my computer down so bad that it is almost impossible to work. Everything is very fine until I set a breakpoint in a shader. From now on my quad-core machine runs on 100%: 75% my app and devenv.exe around 25%. It slows down so bad, the mouse-cursor freezes regularly, switching to other applications takes seconds - this means its REALLY serious…
Ok after I’ve set the breakpoint after serveral seconds (!) it hits and then I can step through the program. When I hit F11 for next step i have to wait at least 10 seconds for the cursor to move to the next instruction, this is impossible. The same behaviour is during scrolling through the shader and inspecting values of variables by moving the mouse-cursor over it.
I’ve seen the youtube-video which introduced debugging opengl in nsight 3.2 with visual studio 2012 and i was really excited about the possibility to debug shaders because I have long sought for such a possibility but as it seems the debugging performance on my machine is far from the one shown in the youtube-video. I’ve got a quite performant machine: Core i5 4x3.4GHZ, 16GB RAM, GeForce GTX 770 4GB RAM and newest drivers so this should be not the problem.
I think NSight would be the most useful tool to develop a serious OpenGL application but with this shader-debugging performance it is nearly unusable, but I don’t have any idea for what reason.
Anyone experienced the same problem? Any help really appreciated!