From 0977952bde30bf0a0d31a93d8dacb9b952df64b8 Mon Sep 17 00:00:00 2001 From: Bartosz Taudul Date: Thu, 9 Jul 2020 00:21:21 +0200 Subject: [PATCH] Update manual. --- manual/tracy.tex | 2 ++ 1 file changed, 2 insertions(+) diff --git a/manual/tracy.tex b/manual/tracy.tex index ec04eaa1..6acc448a 100644 --- a/manual/tracy.tex +++ b/manual/tracy.tex @@ -1231,6 +1231,8 @@ The macro \texttt{TracyD3D12NewFrame(ctx)} is used to mark a new frame, and shou Note that due to artifacts from dynamic frequency scaling, GPU profiling may be slightly inaccurate. To counter this, \texttt{ID3D12Device::SetStablePowerState()} can be used to enable accurate profiling, at the expense of some performance. If the machine is not in developer mode, the device will be removed upon calling. Do not use this in shipping code. +Direct3D 12 contexts are always calibrated. + \subsubsection{OpenCL} OpenCL support is achieved by including the \texttt{tracy/TracyOpenCL.hpp} header file. Tracing OpenCL requires the creation of a Tracy OpenCL context using the macro \texttt{TracyCLContext(context, device)}, which will return an instance of \texttt{TracyCLCtx} object that must be used when creating zones. The specified \texttt{device} must be part of the \texttt{context}. Cleanup is performed using the \texttt{TracyCLDestroy(ctx)} macro. Although not common, it is possible to create multiple OpenCL contexts for the same application.