Profiling of systems in an SLI configuration is not supported.

Nsight Graphics Pro requires a network connection to debug applications. This limitation will be addressed in a future release.

Linux users: Applications that launch child processes are not fully supported in Nsight Graphics Pro. This will be improved in a future version.

Serialized projects can fail to compile if range names contain newline characters. This will be handled in a future release. (54263)

The draw call count in the Range Profiler may be larger than the number of draw calls submitted at the API level. This can be caused by the driver optimizing the submitted workload. This will be updated in a future version. (51956)

Under certain conditions, the Range Profiler pane may be disabled and display one of the following messages.

Hardware signals are not supported in this configuration

This message could be due to one of the following reasons:

1. You are running Nsight Graphics Pro with a Kepler or lower GPU.

2. You are using a defunct or non-NVIDIA GPU.

3. You are attempting to profile a debug build of the project.

No hardware signals found for this API/GPU combination

This message is likely to occur when you are running Nsight Graphics Pro on a non-MSHybrid laptop. (55730)

Nsight Graphics Pro C++ serialization attempts to pick a reasonable default Windows SDK given the content of the capture. On Visual Studio 2015 and later, the SDK may be easily selected as the Target Platform Version property. (53984)

When calculating the histogram for array or cube map resources, the tool only takes into account face 0. As a work around, if you click on a different face, the histogram will be recalculated for that face. In a future version, this will be fixed to take into account all faces. (34403)

If you experience a TDR on either your host or target system, it is recommended that you reboot your machine before trying to restart the debugging session. (22986)

Since the frame scrubber only allows navigation to actions, there may be times when you select a revision for a resource that is not on or near an action. In this case, an earlier revision is selected that is on/near the selected action. This limitation will be addressed in a future version, when the scrubber allows for navigating to any event, not just actions. (26229)

The Frame Scrubber view does not support the nvtxRangeBegin and nvtxRangeEnd functions, only nvtxRangePush and nvtxRangePop. (21499)

Forcing the target application to close through the task manager while in the Frame Debugger may crash the target application.

Windows DPI scaling is not respected in mixed-DPI scenarios with multiple monitors (always keys off main monitor).

Paths with non-UTF8 characters are not supported as a document save location.

Using names that are generated by glGen* is advised for performance and correctness. Under normal operation, if an application uses a mix of generated and non-generated names (e.g. via a middleware product), there is the possibility of conflicts/aliases between names. When running an application under Nsight, Nsight will create its own resources that use names generated by the driver, further increasing the likelihood of conflicts. The recommended approach is to always use names that are generated by the driver via glGen*. (30578)

The Pixel value in the tables for the OpenGL profiler represent shaded pixels (i.e., fragments that ran the fragment shader). If color writes are disabled and the fragment shader doesn't write Z, this value may be 0, even though the depth value for a fragment may be written. (22061)

If you are connected to your target using VNC and attempting to debug an OpenGL program, make sure to disable any "Hook" or "Mirror" driver option in the VNC server settings. (20686)

Nsight Graphics Pro may not work correctly unless double buffering is enabled by the application, since GLUT or other toolkits may skip the SwapBuffer calls for a single buffered window. (24590)

When running Vulkan applications, you need to leave some memory available for Nsight Graphics Pro to use as staging areas on the GPU. If you get an out of memory warning on the host, this is a hint that you are hitting this problem.

Vulkan support known limitations include:

• OpenGL interop is not supported (e.g., glDrawVulkanImageNV).

• There is no HUD.

• Shader editing is not yet supported.

• Native shaders are unavailable.

When running a C++ Capture of some large Vulkan applications on Linux, an error may be reported of "Too many resident pages". This can be worked around by adjusting the MAX_RESIDENT_PAGES constant in Helpers.cpp.

GPU debug and profiling tools will not run with "regular" user accounts due to device permissions. In order to use these tools, users must either:

1. Have the administrator add the user's account to the debug group.
2. Execute the tool as root, or with the sudo command.