After update of OS to Windows 10 from Windows 8.1 Nsight doesn’t work anymore. I used 4.5 before at Win 8.1 and everything goes fine, so after update of OS I also have update for Nsight to 4.7, because I see there Windows 10 support in description. But unfortunately it doesn’t work.
It runs but hangs during frame capture. It is started work after I complete “clean installation” of the latest Nvidia Driver.
The previous GPU driver was installed during Windows update (8.1 → 10), and Nsight doesn’t starts with it.
I use it to debug OpenGL 4.3, but after app launch (all widgets with stats works), it is hang on frame capture.
I tried to use Nsight with DX11 and it is works. Then I tried it with an another OpenGL samples (NeHe lesson №4) and it is hanging during launching again.
Yes of course I already tried. Also with “clean” driver installation, and with reboot after every step. Nothing helps :(
I think need to clarify - I use an notebook with Optimus. As I know Nsight a long time didn’t support Optimus, so looks like it is again a problem with Win 10. Also it (Nsight and the same app) works without any issues on a Desktop PC at work.
If your machine is Optimus machine, I think you still can use Nsight:
- disable iGPU in BIOS, if you don’t have one
- connect a monitor to your external display port which generally assigned to dGPU, and run Nsight and your sample on that monitor
Run Nsight on Optimus machine needs some trick work, but you still can jump over it, I think.
Let us focus on Nsight 5.0, since it’s the latest release.
I just checked the dmp files, seems it shows the same root cause. could you please try these?
do you config the working directory of nsight properly?
do you call ExitProcess() somewhere in your codes?
the crash callstack shows your project.exe just call ‘user32!MessageBoxW’ and lead to the crash, could you just comment it out somewhere in your codes?
for more detail investigation, could you share us your run-able sample, and we can see more
The dmp of Bloom show different crash callstack as your previous one. Seems the Bloom with Nsight on your machine just run to some unexpected path, and I am 100% sure the Bloom with Nsight works as expected in my Win10 box.
Could you try on a clean Win10 box?
on the other hand, could you try to replace ‘$(LocalDebuggerWorkingDirectory)’ to some real path which matches your sample’s requirement?
Could you try on a clean Win10 box?
Actually when I tried Nsight first time Win10 was clean :) Clean as possible after the 8.1 → 10 update.
Unfortunately I have no any PC for such experiments. And anyway it’s not a proper solution.
replace ‘$(LocalDebuggerWorkingDirectory)’
The same result. Crash after SwapBuffers(). As I see path absolutely not related to the problem. Because - app running properly, all this Nsight stuff like a fps counter and loading graph also displayed properly, and sample looks good, so - all data is available.
But when we press “capture” - app will crash.
I just got a repro locally which is exactly the same as yours. Seems that’s due to your laptop is using Microsoft Hybrid Graphics [similar to Nvidia Optimus], Nsight don’t support such kind of iGPU&dGPU combination right now.
Thank you for information. I see Microsoft Hybrid Graphics new feature which appeared in Win 10.
Do you plan to support Microsoft Hybrid Graphics in future?
Hello, I have the same problem.
I am on Windows 10 x64, with two GeForce 560 TIs in SLI (also tried without SLI) and trying to debug an OpenGL 4.4 app in Visual Studio 2015 with NSight 5.0 RC1. My driver is 355.98.
The HUD overlay is not there when i run “Graphics Debugging”. I recently updated from Windows 7 x64, in which the same NSight version was working properly.
The HUD overlay is not there when i run “Graphics Debugging”
I seen the same issue in Win 7 on my desktop PC. but HUD appeared after I changed Nsight options (in Graphics section): “Force present” to true and “Frame Profiler” to enable.
“Force present” should be set in case you are coding for some message driven rendering sample, like CAD software, it will not refresh the window until you do some I/O in it, on the other hand, game software will keep rendering no matter you touch it or not.
Hello.
I am having the same issue when capturing the frame with win 10 laptop and my colleague who have a win 7 laptop doesn’t have this problem.
I’m anxiously waiting for the support for this =D