When I launch an application for graphics debugging I don’t get the Nsight window in Visual Studio 2012. I can capture, sometimes, but I can’t inspect the call or do anything in the VS side. It also fails to capture sometimes with the message “FrameDebugger: FrameDebugger failed to initialize”.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Debugging an app with NSight Visual Studio edition | 3 | 2418 | November 25, 2013 | |
| FrameDebugging failed initialization | 4 | 1632 | September 21, 2015 | |
| "Pause and Capture" not working | 9 | 3326 | April 10, 2014 | |
| Nsight 5.4 can't capture frame anymore | 13 | 2566 | December 7, 2017 | |
| Nsight debugger crashes my graphics application on startup | 9 | 2778 | January 18, 2018 | |
| Graphics Debugging problems / crashes. | 2 | 1404 | March 11, 2013 | |
| Nsight 5.4 on Visual Studio 2017 hangs when launching the debugger | 17 | 3873 | December 19, 2017 | |
| OpenGL debugging not working | 1 | 1191 | March 30, 2015 | |
| App crash on Frame Capture - How to nail it down? | 4 | 2113 | August 13, 2019 | |
| NSight 5.1 in VS 2012 crashes during frame capture | 3 | 1325 | December 22, 2016 |