← All resources

Profiling the GPU in Unity Editor

Blog Beginner

Jan Mróz

Proposed by Jan Mróz

Visit resource ↗

Description

Profiling the GPU in Unity Editor is Jan Mróz's tutorial attaching Nvidia Nsight Graphics to the Unity Editor on Windows so GPU work can be captured without rebuilding players. Prerequisites include DX11 or DX12 enabled, administrator Nsight launches for hardware counters, and killing stray Unity Hub processes before attach.

He documents launching Unity with -projectPath and -force-d3d11 or -force-d3d12, selecting Game view swap chains, capturing with F11 in Frame Debugger versus GPU Trace Profiler, enabling shader debug symbols for DX12 pipeline inspection, and iterating material changes while Nsight stays injected.

Beginner technical artists on NVIDIA GPUs who already read the GPU profiling basics article will save build time with this workflow. Using a mid-tier GPU matching minimum spec is recommended so bottlenecks remain visible.

The post is free on proceduralpixels.com with troubleshooting for overlays, missing counters, and flaky attach scenarios.

Editor-attached Nsight profiling is widely recommended in Unity optimization circles to shorten shader iteration loops.