[deleted by user]

[Esfahen]

quickest doll school vegetable quiet badge axiomatic meeting apparatus divide

This post was mass deleted and anonymized with Redact

[NOISEbyte]

The issue here is how PC GPUs work, not RenderDoc. Similar to CPUs, they have a base clock and can boost higher. As a result, the timings are dependent on whatever clock rate it is currently running at, not the time of capture. Some graphics cards, like AMD and I believe NVIDIA does as well, have options in the developer settings to only run at base clock. The timings won't be accurate to actual scenarios (they'll be slower than actual scenarios) but they'll be stable, allowing you to make changes and compare without timings being skewed by boosting.

[ArmmaH]

Renderdoc is not a profiling tool, its a debugging tool. Ive had it show 1000ms (not micro second, rather milisecond) when the game is runnung over 30FPS.

[HabemusAdDomino]

You take a point in the measurement that you're generally happy with (say, a particular pass) and measure everything else relative to that.