Open topic with navigation

In NVIDIA® Nsight™ Visual Studio Edition, the host is the term for the computer that is running Visual Studio, where your application is being built and debugged. After you install NVIDIA Nsight on your computer, you will see a new menu called Nsight on your Visual Studio taskbar.

Feel free to explore the various options on this menu. The items that are critical for debugging will be discussed in further detail in later topics.

Nsight Host Settings

After installing NVIDIA Nsight on the host machine, open Visual Studio and go to Nsight > Options to configure your settings.

1. On the General page, configure some of the basic options such as timeouts, whether to enable secure connections, and which port NVIDIA Nsight should use to connect to the target machine.
   Note that the default port setting is 8000. The port number on both the host and target machines must match in order for a successful connection to occur. (See Target Basics for more information.)
   
2. On the Analysis page, you can configure several analysis options such as CUDA kernel trace mode, default activity type and timeline axis mode, as well as a default report directory.
   
3. On the CUDA page, you can configure several options for both the CUDA Debugger as well as the CUDA Memory Checker.
   
4. On the Debugger page, configure some basic display options for NVIDIA Nsight.
   
5. On the Graphics page, you will find the following options:
   

Frame Debugging

• Force Present/SwapBuffer calls on the target to repaint the window — If this option has been set to True, the frame replay will automatically invalidate the window of the target application for every Present/SwapBuffer call.

Shader Debugging:

• Default Register Format — This option allows you to select the default interpretation of the raw values in general purpose assembly registers. If set to float, register components will be shown as float in the Watch window, and also interpreted as float in both breakpoint conditions and expressions. If set to int, the same register components will be shown as signed integers, and also used as such in both breakpoint conditions and expressions. It is also possible to control the interpretation of register data on a per-register basis, using the $f, $i, and $ui postfixes. For example, r5$ui is the interpretation of r5 as a uint4 vector.
• Force Assembly Debugging — This option is only available when debugging a Direct3D application. If set to true, the shader debugger will fall back to assembly debugging, even if source debug information is available.
• Preferred remote shader debugging mode — With this option, you can choose whether to prefer full hardware debugging or replay-based debugging on remote targets. When a breakpoint is hit, replay-based debugging frees the GPU to draw the desktop or run other application code. Full hardware debugging halts the GPU when a breakpoint is hit; no other tasks may run, but the debugger may run faster and may provide deeper insight of the hardware state.
• Shader debugging preference — This option selects how heavily shaders will be instrumented for debugging. The options available are: 
  • Full Debugging Experience — Supports all features, but may result in slow debugging speed.
  • Limited Debugging Experience — May provide better debugging speed at the cost of not reporting information about sympathetic shader threads.
  • Minimal Debugging Experience — The fastest setting, but also has the most restrictions. No information about sympathetic shader threads will be reported, and breakpoints set in other shaders while already debugging a shader may not be hit before a completely resume. Also, no render target, geometry, or compute buffer previews will be available in the Graphics Focus Picker.
  • Disabled — Completely disables all shader debugging features, including pixel history.
• Show disassembly if source does not exist — With this option, if no source can be found for the given shader, then disassembly will be shown instead. You can choose one of three options here: Ask, Always show, or Never show.
• Use compressed symbol information — Using compressed symbol information reduces the memory used by the Nsight Monitor, but can slow down debugging performance.
  

6. On the Updates page, select whether or not you want NVIDIA Nsight to automatically search for updates upon startup.
   
   
   
   

Click OK when you are finished configuring your options for NVIDIA Nsight.

Configuring NVIDIA Nsight on the Host Machine

After NVIDIA Nsight has been installed on the host machine, it will need to be configured. To do this:

1. Open your project in Visual Studio.
2. On the Solution Explorer menu, click the Nsight User Properties icon. (As an alternative, you can also go to the Project menu > Nsight User Properties.)
   
   
3. This will open the NVIDIA Nsight User Settings dialog box.
   
   
   On the default Launch page, you configure the appropriate actions and options to be used when you begin debugging your project.
   
4. For Launch external program, enter the file path to the application that is being debugged.
5. For applications that are launched by another application (such as a Steam app or a proprietary launcher app), you should check the Application is a launcher checkbox.
6. The Launch Options section allows you to configure the name of the target machine, any command line arguments needed, and set the working directory.
   The default setting for the Connection name field is localhost; however, unless you are using a local debugging configuration, you'll need to enter the remote computer's name.
   
   Note that you can also opt to use the Nsight Connections toolbar to specify the name of the computer that should be used for running the target application.
   

   

7. Click the Synchronization page.
   
   
   
   From here, you can choose which file extensions to include or exclude for synchronization purposes.
   If you're debugging a large application, you'll want to turn off synchronization to prevent performance problems.
   

   When using file synchronization, all file paths are relative to localhost. When file synchronization is turned off, the file path is relative to the target machine (which could be localhost as well, depending on your settings.)

8. Click the Shader Compilation page.
   
   
   
   This page allows you to specify include paths for compiling the shaders in your application.

of

NVIDIA GameWorks Documentation Rev. 1.0.150630 ©2015. NVIDIA Corporation. All Rights Reserved.