Open topic with navigation

The NVIDIA Nsight Frame Debugger provides the ability for both real-time and capture-based application analysis. In real time, the Performance Dashboard shows a heads-up display (HUD) on the application being debugged, which includes real time performance data from both the GPU and CPU.

Once a capture is performed, you can navigate through draw events with the Frame Scrubber, see pipeline states in the API Inspector, inspect render targets and textures in the Resources View, and display profiler information with the scene broken down according to API performance markers. (Many of these features are similar to NVIDIA's PerfHUD software, which may be familiar to you.)

Launch the Frame Debugger:

1. Open your project in Visual Studio.
2. Build the project.
3. If you are using remote debugging, make sure the Nsight Monitor is running on the target machine. (The target machine can be either the localhost or a remote machine; however, in a local debugging configuration, the Nsight Monitor will start automatically.)

   For more information on configuring your target and host machines, see Target and Host Setup.

4. From the Nsight menu, select Start Graphics Debugging to launch your target application. (Wait for the application to finish loading and start. The target application must be running before you can start using the Frame Debugger.)
5. From the Nsight menu, select Pause and Capture Frame. In Visual Studio, a number of views will open. On the target application, the HUD will appear with the toolbar and scrubber.

Note for OpenGL frame debugging: If you encounter debug GLSL compiler issues, the best way to work around it is to disable the shader debugger. To do so, see setting your Shader Debugger preferences. Note that this will disable all shader debugging features, including pixel history.

Common Frame Debugger Features

There are three buttons that are common across several frame debugger views.

• The Clone button makes a copy of the current view, so that you can compare different parts of the API Inspector (or other cloned views) for the current action.
• The Lock button freezes the current view so that changing the current event does not update this view. This is helpful when trying to compare the same state on two different actions.
• The Show Event Info button toggles on and off the details of the draw call that has been selected on the frame scrubber.

of

Open topic with navigation