OS: Windows 10 Home
GC: RTX 3060 Laptop (Driver Version: 555.85)
API: Fails on DX11 (I also thought I had tried DX12 but as I will learn later, was actually not.)
Nsight Graphics: 2024.1.1.0 (build 34212950) (public-release)
CPU: 11th Gen Intel(R) Core™ i7-11800H @ 2.30GHz 2.30 GHz
Unity: verified on both Unity LTS versions: 2022.3 and 2023.2.6
Hello, it seems the GPU Trace Profiler is unable to find and attach to Unity Builds. I have tried both manual and automatic attachment. In the later, Nsight Graphics is unable to locate the build I launched from Nsight earlier. I have also tried using the command line however it again cannot attach to the build and outputs the same logs:
I have been able to run the GPU Trace Profiler to work on some C++ applications I had so I can verify that its not broken on my computer. Lastly, have tried a couple different Unity projects running on different Unity versions, they all fail to run the GPU Trace Profiler.
Let me know if there is anything more I can give, thank you.
Thank you for using Nsight Graphics and providing your feedback. Are your Unity samples launched from Nsight Graphics directly or launched through some Unity launcher? Can you take some try that kill all Unity related process in taskmgr and do another launch from Nsight Graphics?
These are complete standalone builds (.exe) from Unity and were launched from Nsight’s GUI. Another interesting thing is the Frame Debugger works with these builds, it just seems to be the GPU Trace Profiler.
Not sure if this helps but the only observable different I see between running the build normally and with Nsight are the child process.
Number 1 is launched with Nsight. Number 2 is without.
That’s weird, what’s your app’s Graphics API? GPUTrace only support D3D12, OpenGL and Vulkan. If your app uses other Graphics API, then Nsight Graphics will not support that.
Looks like that did the trick! I had to force Unity to use D12 in the options. I thought I was in D12. For my tests I would test the default (D12) and force Unity to use only D11. Looks like this was not the case.
