Profiling with Tracy

Use Tracy for a timeline of native zones, threads and optionally memory allocations. It is neither the built-in C# profiler tab nor a switch in a normal editor installation.

Prepare and capture

1. Use a separate build with profiler=tracy and profiler_path pointing to Tracy sources: a directory containing public/TracyClient.cpp, or public itself. Configuration aborts without this path.
2. Match the Tracy viewer to its client. Project settings cannot repair a protocol mismatch.
3. Start the viewer and instrumented application, connect to the correct process and capture a short reproducible interval: a level load or several comparable frames.
4. Save the capture with build identity, scenario and settings. Compare durations of matching zones rather than average FPS alone.

Additional options

profiler_track_memory enables allocation instrumentation; profiler_record_on_demand enables on-demand recording. profiler_sample_callstack is platform-limited: configuration permits Windows, Linux/BSD and Android. These modes change overhead; enable only what you need.

If zones are absent, verify the instrumented executable and viewer connection. A long zone can include waiting on another thread: inspect adjacent threads before attributing it to computation. Neither a Tracy build nor viewer connection was executed during this review.