In the realm of PC gaming performance, the allure of a single metric, “Average Frames Per Second (FPS),” can often overshadow the broader narrative of gameplay experience. While a high average FPS may appear impressive, players familiar with the dissonance of stutters and hitches know that consistency is just as crucial as raw framerate. This is where the importance of comprehensive benchmarking comes into play, emphasizing not only average FPS but also the more telling metrics of 1% low and 0.1% low average FPS. These figures illuminate how frequently and severely a system dips below optimal performance during actual gameplay, providing a clearer picture of a game’s smoothness and responsiveness.
CapFrameX has emerged as a favored tool among PC gaming enthusiasts and reviewers for capturing and analyzing in-depth performance data. Rather than relying solely on basic FPS counters, CapFrameX records raw frametimes and translates them into meaningful performance metrics. This allows users to analyze, compare, and optimize their gaming experiences with precision. In the following sections, we will guide you through the process of setting up CapFrameX, running consistent benchmarks, interpreting results, and presenting findings that genuinely reflect real-world performance.
What CapFrameX Actually Measures
When utilizing CapFrameX for benchmarking, users gain access to per-frame data, transforming it into metrics that reveal not just how fast a game runs, but how smooth and consistent it feels. CapFrameX captures frametimes—the duration required to render each frame—and converts these into traditional framerates. The relationship between frametimes and framerates is inversely proportional, meaning that lower frametimes correspond to higher framerates and vice versa. This raw data provides a far more accurate analysis of performance than simple overlay FPS counters, which may obscure potential stutters and hitches.
From the captured frametimes, CapFrameX generates several key metrics that highlight different aspects of performance. Among these, three metrics stand out as particularly valuable for measuring gaming performance:
- Average FPS: This standard metric represents the overall framerate averaged across the capture session. While useful as a headline figure, it does not fully convey the stability of the gaming experience.
- 1% low average FPS: This metric indicates the average of the worst 1% of framerates, offering a more representative picture of the worst sustained performance. A high 1% low average FPS relative to the average FPS typically suggests a smoother and more consistent experience.
- 0.1% low average FPS: This metric reflects the average of the worst 0.1% of framerates, highlighting the performance level that players rarely drop below. It is particularly useful for identifying rare but severe dips that may not be apparent in averages.
CapFrameX’s use of these percentile-based metrics, derived from actual frametime sorting and conversion, is why it has garnered a loyal following within the PC gaming community. It provides insights into both speed (average FPS) and smoothness (1% and 0.1% low average FPS), allowing for a comprehensive assessment of gaming performance.
Preparing Your System for Benchmarking
Benchmarking is not merely about running a tool and recording numbers; it requires a consistent and controlled system environment to ensure that results accurately reflect real performance. To achieve this, several essential steps should be taken before capturing any benchmark runs.
Updating Your UEFI BIOS, Operating System, and Drivers
Before initiating benchmark runs with CapFrameX, ensure that your motherboard’s UEFI BIOS, operating system, and drivers are fully updated. An outdated software environment can lead to performance anomalies, instability, and inconsistent benchmark results, including erroneous frame timing. For graphics drivers, using a tool like Wagnardsoft’s Display Driver Uninstaller to cleanly uninstall them before reinstalling can significantly minimize potential issues.
Clearing the Benchmarking Environment
To reduce interference and resource contention:
- Close unnecessary applications and processes: Programs such as web browsers, cloud sync apps, chat/voice applications, and any background utilities not needed during testing can consume valuable hardware resources.
- Disable overlays and recording features: Features from tools like Discord, Steam, and NVIDIA can add overhead or interact unpredictably with frame capture. The exception is the Rivatuner Statistics Server overlay, which will be discussed later.
- Temporarily pause antivirus scans: If you trust the benchmark software, pausing real-time scanning can prevent slowdowns during game load and execution.
- Ensure V-Sync is set to “OFF”: This can be done in your GPU vendor’s settings or the game’s settings.
- Disable latency-reducing technologies: Features like NVIDIA Reflex Low Latency and AMD Anti-Lag can act as framerate limiters and compromise frametime consistency.
Configuring Power and Performance Settings
To prevent your system from throttling:
- In Windows Power Settings, switch to either High Performance or Balanced power plans to minimize power throttling features.
- If using a laptop, plug in the power adapter and disable battery-saving features during benchmark runs.
- Set your GPU to run at maximum performance: This can be done through your GPU’s graphics driver software.
Monitoring Temperatures and Stability
Thermal throttling can skew benchmark results by reducing CPU/GPU clocks under load. Before benchmarking:
- Utilize hardware monitoring tools like MSI Afterburner or HWiNFO to ensure CPU/GPU temperatures remain within safe ranges.
- If your system is unstable due to aggressive overclocks or tuning profiles, consider reverting to stock settings for stable baseline benchmark results.
Maximizing Consistency
To achieve consistent benchmark results, ensure that every run is conducted under the same conditions:
- Use the exact same graphics settings for every capture.
- Avoid changes to system state during runs by temporarily disabling your internet connection.
- Perform multiple benchmark runs and average the data to minimize variance.
By following these preparatory steps, you create a controlled environment where benchmark differences reflect genuine changes in your system or game settings, rather than background tasks or inconsistent loads. Once your machine is stable, you will be better equipped to capture meaningful performance data with CapFrameX.
Installing and Setting Up CapFrameX
Setting up CapFrameX is a straightforward process, and following a clear setup guide ensures reliable captures and meaningful results. Here’s a step-by-step walkthrough for installing and configuring CapFrameX:
1. Downloading CapFrameX
Visit the CapFrameX GitHub Releases page to download the latest beta build, choosing between the installer or portable version from the Assets section:
Note that CapFrameX requires .NET Framework 9 or higher on Windows 10/11 to function properly.
2. Optional but Recommended: Installing RTSS for Displaying Performance Metrics Overlay
CapFrameX utilizes the open-source Intel PresentMon backend for capturing frametimes. To display performance data in-game, it is advisable to install the latest version of Rivatuner Statistics Server (RTSS), available at:
3. First-Time Launch and Setup
Upon launching CapFrameX for the first time, it may create necessary configuration and benchmark capture folders. Allow it to initialize and then close it to set up the folder structure.
To configure the capture folder, click on the vertically aligned Observed directory button in CapFrameX’s UI. You can either note the default directory for benchmark captures or change it to a preferred location.
4. Setting Up Capture Options
CapFrameX allows users to control capture timings, delays, hotkeys, and sound cues, all vital for establishing repeatable benchmarks:
- Capture hotkey: Set a keyboard hotkey combination to start or stop benchmark captures.
- Capture time [s]: Set this to 0 for unlimited capture time or specify a duration for fixed-length runs.
- Capture delay [s]: Choose a delay before capture starts, or set it to 0 for immediate capture.
- Hotkey sound: Enable a sound cue for capture start and end times.
CapFrameX also features a composite function called Run history and aggregation, which allows for multiple benchmark runs to be recorded back-to-back, providing a more statistically meaningful data set.
5. Testing Whether Your CapFrameX Setup Works
With CapFrameX and RTSS installed and running:
- Run a quick capture: Launch a game and use your capture hotkey to log a segment of gameplay.
- Verify the existence of the capture: Check the Captures section in CapFrameX’s UI to confirm your saved capture appears.
- Adjust your settings if needed: If captures aren’t appearing correctly, revisit your hotkey settings.
6. Tips
- To reset CapFrameX’s settings or overlay configuration profiles, delete its configuration folder located at
%APPDATA%CapFrameXConfiguration. - Keep CapFrameX updated by downloading newer releases from the GitHub Releases page.
- If you encounter a “Multiple processes detected” message, close the offending game process or add it to CapFrameX’s Process ignore list.
With CapFrameX installed and configured, you are ready to begin benchmarking your favorite games!
How to Capture Benchmark Runs with CapFrameX
Capturing consistent benchmark runs is essential for meaningful performance analysis. CapFrameX records frametimes, allowing you to derive metrics like Average FPS, 1% low average FPS, and 0.1% low average FPS. This process requires proper capture initiation and termination, along with a focus on consistent scenes.
1. Launching CapFrameX and Your Game
- Open CapFrameX and ensure it runs in the background.
- Start your game and load into a scene suitable for benchmarking, ensuring it is repeatable.
- Check for the CapFrameX overlay to confirm proper setup.
2. Start the Capture
- In CapFrameX’s Capture tab, verify your capture hotkey.
- Press your capture hotkey when the game is ready to begin logging frametimes.
3. Stop the Capture
- Once you complete the benchmark segment, stop the capture using the hotkey again.
- View the completed capture in the Captures section of the CapFrameX UI.
4. Do Multiple Benchmark Runs
For reliable results, capture multiple runs of the same scene, ideally at least three. This practice reduces run-to-run variance and enhances the accuracy of your statistics.
Analyzing Your Benchmarks in CapFrameX
After capturing benchmark runs with CapFrameX, the true value lies in interpreting the data to understand your game’s performance. CapFrameX provides two powerful views for this purpose: the Analysis tab for individual captures and the Comparison tab for side-by-side evaluations.
The Analysis Tab
The Analysis tab allows for detailed scrutiny of a single benchmark run, featuring graphs and statistics that help visualize performance profiles.
- Frametime graphs: Display the time taken for each frame to render, with smoother gameplay indicated by flatter lines.
- FPS graphs: Convert frametimes into FPS values, plotting these over time.
- Percentile and metric summary: Provide metrics such as average FPS and low-percentile FPS values.
- Sensor data (optional): Display CPU/GPU temperatures, loads, clocks, and power values alongside performance graphs.
The Comparison Tab
The Comparison tab enables evaluation of multiple benchmark captures together, facilitating comparisons across different graphics settings, hardware setups, or driver versions.
To use the Comparison tab, drag and drop captures from the Captures list into the Comparisons list. You can select the type of chart to view, choose performance metrics, and customize titles for clarity.
Common Benchmarking Pitfalls and How to Avoid Them
Even with a robust tool like CapFrameX, misleading results can arise from improper setup and execution. Here are common mistakes and advice for avoiding them:
Running Benchmarks with Inconsistent Scenes
Capturing data from different gameplay segments can lead to dramatic variations in framerates. Always benchmark in the same, repeatable scene.
Ignoring Frametime Variance
Many overlook the importance of frametime consistency. High average FPS with erratic frametimes can result in a choppy experience. Always consider all three performance metrics when analyzing benchmarks.
Not Preparing Your System Properly
Background applications and services can skew results. Minimize interference by running benchmarks with only essential applications open.
Skipping Multiple Runs
Running only one capture is rarely representative. Utilize CapFrameX’s run history and aggregation features for more accurate results.
Accidentally Comparing Different Game or System Settings
Ensure that benchmarks are conducted under the same graphics settings, operating system builds, and driver versions to minimize variables.
Overlooking System Limits and Bottlenecks
Benchmark numbers may not reflect GPU performance alone. Be aware of potential CPU or memory bottlenecks that can affect results.
Forgetting to Warm Up the Game
Benchmarking immediately after launching a game can capture unusual spikes. Conduct warm-up runs for more representative results.
Not Enabling MsBetweenDisplayChange When Benchmarking with Frame Generation Enabled
When using Frame Generation technologies, enable the “MsBetweenDisplayChange” method in CapFrameX options for accurate measurements.
Benchmarking transcends merely achieving high FPS; it encompasses understanding the consistency and smoothness of frame delivery during real gameplay. Tools like CapFrameX, with their support for detailed metrics, are essential for anyone serious about performance analysis. By preparing your system, executing consistent benchmarks, and interpreting detailed outputs, you can make informed hardware decisions and optimize settings for improved performance.
