I’m using the latest NVIDIA Nsight Graphics to debug a Steam game. When I launch Steam through Nsight, the game’s launcher starts first and then spawns the actual game process. Nsight injects its DLL into both processes, causing a crash. I disabled “Automatically Connect” to manually attach later, but Nsight still auto-injects. How do I make it inject only into the main game executable? Maybe it would be a good idea to add a blacklist tab so that the program definitely doesn’t inject into certain processes.
Hi @mangekou313131,
Thanks for the feedback.
Automatically Connect controls automatic attachment, not process injection. Nsight Graphics is an in-process debugger, so the launcher process hierarchy must be injected for the game process to appear on the Attach tab.
For Steam:
- Fully exit Steam and related game processes.
- Select Steam as the application executable and set
Automatically ConnecttoNo. - Launch Steam and the game through Nsight Graphics.
- Attach to the game executable from the Attach tab.
Some games use anti-cheat or anti-tamper protection that may block injection or debugging. Could you share the exact Nsight Graphics version, launcher and game executable names, which process crashes, and any relevant Output Messages?
Thanks,
An