adding aftermath debugging and fixing forward plus
This commit is contained in:
@@ -0,0 +1,22 @@
|
||||
Nsight Aftermath is primarily a development tool and is intended to be used
|
||||
with minimal side effects to the user application. Despite this, there may be
|
||||
overhead when it is enabled resulting in performance degradation. The
|
||||
application should only fully enable Nsight Aftermath when in an application
|
||||
controlled 'diagnostics mode', e.g. enabled after the user has experienced a
|
||||
GPU crash and exhaustive data collection is required.
|
||||
|
||||
Your users should also be able to easily disable Nsight Aftermath in situations
|
||||
where performance is critical, such as when benchmarking or during competitive
|
||||
play.
|
||||
|
||||
To override the behavior of applications that do not follow the above guidelines
|
||||
a user may force off all Aftermath functionality in the application:
|
||||
|
||||
on Windows, set a Windows registry key:
|
||||
HKEY_CURRENT_USER\Software\NVIDIA Corporation\Nsight Aftermath\ForceOff=1
|
||||
|
||||
on Linux, set an environment variable:
|
||||
export NV_AFTERMATH_FORCE_OFF=1
|
||||
|
||||
For questions regarding these guidelines or Nsight Aftermath in general, please
|
||||
email NsightAftermath@nvidia.com
|
||||
Reference in New Issue
Block a user