Cannot start Graphics Debugger

Developer Tools Nsight Visual Studio Edition
1

Hi nVidia,

I have some trouble starting the Graphics Debugger on Windows 8, GTX 770, VS 2012. The error is not very helpful, so I have no idea as to what to do.

An example of the error on a sample project:

Any ideas?

Thanks,
Alexei Mihalchuk

2

Hello Alexei,

That doesn’t look good. Which version of Nsight?
Let’s try to get some logs from you. Could you do the following:

  1. Close Visual Studio and the Nexus (or Nsight) Monitor
  2. Go to %AppData%\NVIDIA Corporation\Nsight\Vsip\1.0\Logs and %AppData%\NVIDIA Corporation\Nsight\Monitor\1.0\Logs and delete any existing files, do this on both machines (host and target)
  3. Edit Nvda.Diagnostics.nlog as follows
  4. For the host/client machine, it will be: For 32-bit OS: Program Files\NVIDIA Corporation\Nsight Visual Studio Edition \Host\Common\Configurations For 64-bit OS: Program Files (x86)\NVIDIA Corporation\Nsight Visual Studio Edition \Host\Common\Configurations
  5. For the target/server machine, it will be: For 32-bit OS: Program Files\NVIDIA Corporation\Nsight Visual Studio Edition \Monitor\Common\Configurations For 64-bit OS: Program Files (x86)\NVIDIA Corporation\Nsight Visual Studio Edition \Monitor\Common\Configurations
  6. Go to the last logger at the bottom of the file:
  7. Change the minlevel attribute value from "Error" to "Trace"
  8. Save file
  9. Reproduce the problem, and send the generated logs: %AppData%\NVIDIA Corporation\Nsight\Vsip\1.0\Logs and %AppData%\NVIDIA Corporation\Nsight\Monitor\1.0\Logs

Send this the logs to: devtools-support at nvidia dot com

3

Hi,

It doesn’t look like it is able to launch the application ‘C:\Users\Alexei\Documents\Visual Studio 2012\Projects\War\War\bin\x64\Debug\War.exe’. (we will fix the problem of Nsight not reporting this in the UI correctly).
Does the application run outside of Nsight without a problem? Do you need to pass in arguments to the application? If so, please right click on the Startup project, select “Nsight User Properties” and type in the arguments in the “command line arguments” field.

If none of that works, would you be able to share this exe (or sources) with its dependencies to reproduce in house?

Thanks

4

Hmm, the problem is not with the path. The confusing error appears if a 64-bit .NET process is launched. Switching to 32-bit mode works.

Thanks for your time,
Alexei Mihalchuk