Tracy Profiler 0.10

For a more detailed change list, see https://github.com/wolfpld/tracy/blob/v0.10/NEWS.

System power usage

Under Linux, Tracy will now report how much power the system is using. The specifics of what is measured depends on what the hardware is capable of reporting.

Error markers removal

Zone error markers (red regions and error bars) have been removed to be consistent with how all other profiling events are displayed.

Major overhaul of how timeline items are processed in GUI

See https://wolf.nereid.pl/posts/how-tracy-faster/ if you are interested in more details.

Global configuration settings dialog

You can find it in the profiler's about menu (the wrench icon in the welcome dialog).

Trace description or filename is now displayed on the window title bar

History of viewed symbols

You can go back to previously displayed symbols in the symbol view. Currently the history granularity is at the symbol level.

Improvements in csvexport

You can now export messages and thread identifiers of zones.

GPU tracing improvements

Vulkan contexts can now use the VK_EXT_host_query_reset extension and Vulkan symbols can be dynamically loaded. The D3D11 and D3D12 instrumentation has been rewritten.

Support for running under rr

If you need to run a profiled application under the rr debugger, you can now use the TRACY_PATCHABLE_NOPSLEDS to make the instrumentation more efficient.

Custom program name support

You can now use the TracySetProgramName() macro to set a custom program name to be sent by the client. You may find this useful if you need to run the same executable in different roles, e.g. one executable would identify itself as a game server, the other as a game client, and so on.