What's new
- F3 opens a Performance window in the editor, and an overlay over a game run from a project.
- It shows frame times, CPU time for each system (scripts, physics, animation, audio, UI), GPU time for each render pass, and the process's CPU, memory and threads.
- GPU times come from timer queries that are never waited on, so measuring does not slow the frame down.
--stats-log FILEwrites every sample to a CSV file, one row per number, so a run before an optimisation can be compared with one after it.- For function-by-function timings, a build with profiling on connects to the Tracy profiler.
An exported game has no overlay and no profiler: a finished game carries no debug tools. See Performance.