Frame Debugger automatically connects, nearly instantly.
GPU Trace never finds the process. Just “Searching for attachable processes…” over and over.
Default port range works for Frame Debugger.
Tried a custom port range that confirmed works for Frame Debugger.
I haven’t been able to find any port ranges that work for GPU Trace.
Annoyingly I can use GPU Trace as expected with other applications.
I can’t provide a minimal example, so I understand I probably won’t get much help with this.
I want to use GPU Trace because I’m experiencing some really insane and confusing rendering glitches, so maybe that’s related?
Perhaps someone who knows more about what Nsight is looking for when scanning for viable processes has some ideas.
GeForce RTX 4070 Ti SUPER
566.36 | WHQL
Nsight Graphics 2024.3.0.24333
Windows 11 23H2
D3D12
Access to GPU performance counters is allowed.
Alright, I tried to create a minimal example application and it appears the D3D12 Agility SDK is causing this.
I’m using the latest stable release, 614.
I’m using an ID3D12SDKConfiguration1 to create an ID3D12DeviceFactory.
Then I use the ID3D12DeviceFactory to create my ID3D12Device, as described in the Independent Devices specs.
I guess GPU Trace doesn’t support this method for enabling the Agility SDK.
Sorry if this was mentioned somewhere and I missed it.
Hope I’m missing something, or this gets supported some day.
I can’t do it the normal way and export the D3D12SDKVersion/D3D12SDKPath symbols, since I’m using .NET, and .NET is still unable to export symbols like this.
Thank you for using Nsight Graphics and providing your feedback. We are sorry for any inconvenience you have encountered. It seems you have already created a minimal example, and could you please provide your simple example that would allow us to reproduce the issue? This will help us in investigating and resolving the problem more efficiently.