Performance Capture

Performance Capture

Performance Capture records presented-frame timing for a running game and summarizes repeatable performance characteristics.

Results can include average FPS, 1% lows, frame-time percentiles, and large frame-time spikes. A capture is evidence from one scenario; compare runs made with the same location, settings, duration, and behavior.

Windows

Windows capture uses the bundled PresentMon provider. Close unrelated capture or monitoring tools if they compete for the same presentation data.

Linux

Linux capture uses MangoHud. The selected game must be launched with the MangoHud logging and control configuration shown by GameAtlas.

Before capturing:

1. Install MangoHud and confirm its overlay can attach to the game.
2. Apply the GameAtlas launch options in the game's Linux Performance section.
3. Fully exit and relaunch the game after changing launch options.
4. Reach a repeatable gameplay scene.
5. Start the capture from GameAtlas and keep the game actively rendering until finalization completes.

GameAtlas minimizes when capture begins. At the end of the timer, MangoHud may need additional time to stop logging and finish writing the CSV. Do not close the game during that finalization period.

Raw captures are stored locally in the GameAtlas performance-capture data directory.

Troubleshooting

MangoHud is not detected

• Confirm the game was completely relaunched after applying the command.
• Confirm the command includes MangoHud and the output/control configuration supplied by GameAtlas.
• Verify MangoHud attaches to the actual render process rather than only a launcher.
• Use Diagnostics Center or Runtime Dependency Doctor to check the installation.

Capture reaches zero and waits

Keep the game foregrounded and actively rendering while MangoHud finalizes. GameAtlas waits for a finished capture file rather than treating the timer alone as success.

No capture file appears

• Verify the output folder in the launch configuration.
• Check that the game and MangoHud can write to it.
• Remove conflicting custom MangoHud options temporarily.
• Fully exit the game before retrying.

Comparing results

Use the same game version, graphics settings, resolution, location, duration, frame limit, and background workload. A difference between unmatched scenarios is not a reliable optimization result.

See Performance Diagnostics and Linux.