DOCS Back to framegain.dev
Pro

Benchmark

Measure a before-and-after result in Play In Editor after investigating a Framegain finding.

The benchmark is the runtime evidence layer. It belongs after the scan has identified a candidate and after you have made a controlled change.

#Run in PIE

The documented Pro benchmark runs only in Play In Editor (PIE). Capture the same scenario before and after the change so the comparison answers one question.

#Compare the result

Use the measured frame-time result to judge the change. A scan estimate can explain why a candidate was selected, but it cannot prove what the running game did.

#Keep the comparison fair

Use the same map, camera, target, and relevant runtime conditions for both runs. Record anything that changed besides the fix.

Important

PIE is a measurement context, not a guarantee of every shipping-build result. Validate important decisions on the target hardware and build configuration as well.

FRAMEGAIN DOCS

Search documentation

Type to search across 16 pages.