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.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Some issues about connecting or attaching to games | 1 | 2978 | February 14, 2019 | |
| NSight Graphics does not detect the game | 1 | 211 | December 22, 2025 | |
| Nsight Graphics 2021.5.1 not connecting | 5 | 507 | August 29, 2024 | |
| Nsight Graphics - no processes in 'Attach' tab | 6 | 3213 | May 21, 2018 | |
| A little tip for Nsight Graphics Frame Debugger | 0 | 773 | March 10, 2024 | |
| I can't connect although the PID match up? | 0 | 830 | December 2, 2021 | |
| Nsight Graphics not working with Vulkan API | 1 | 815 | February 6, 2020 | |
| Attach graphics debugger to running process | 1 | 2400 | January 9, 2017 | |
| NSight is stuck in searching for attachable process | 3 | 254 | January 5, 2026 | |
| Latest Nsight Graphics (2018.5.1.18263) doesn't launch nor shows processes (Linux) (Solved) | 16 | 3253 | October 26, 2018 |