FrameView 1.5 Release Notes

Below is a list of the following changes in the FrameView 1.5 release.

  • FSR 3 Frame Generation is now supported with all metrics, including PC Latency and FPS.
  • Introducing the “Scanout Color Bar”, a feature that makes it easy to detect runt frames, frames that appear for an infinitesimal amount of time and artificially increase the FPS counter without actively contributing to smoothness. Simply toggle the feature on, and a color bar will appear on the left side of the screen, which changes color with each new displayed frame. Using a capture card (recommended) or high speed camera with V-Sync Off / G-SYNC Off, you can visually see when these runt frames appear for only an infinitesimal amount of time, providing no visual benefit to the gamer.
    Note: Scanout Color Bar has some performance overhead, and as a result can negatively impact performance. We recommend turning it off during benchmarks.
  • Introducing the “10% High FPS” metric in the benchmarked summary and summary files. 10% High averages the top 10% fastest frametimes, converted to FPS. 10% High FPS can be a fast way to determine if the gamer is seeing runt frames as runt frames will express as a very high 10% High FPS relative to their average (ex: 1000 FPS)

To help protect our users, we would like to share information around an issue we’ve discovered:

  • If the user changes certain game settings during an active benchmark (example: turning “frame generation” from “on” to “off”), it can cause FrameView to record a unique benchmark session at the time the setting was adjusted. For users, this means a single benchmark can result in two entries in the locally stored summary file, and the end of the benchmark summary in the overlay will exclusively reflect the game’s behavior after the setting change. Our recommendation is to always adjust settings before running a benchmark.

To download FrameView, or for more information including the user guide, please go to