Download Nvidia FrameView App Download | TechSpot

FrameView can capture data from all major APIs and virtually all games thanks to support for DirectX 9, 10, 11 and 12, OpenGL, Vulkan and Universal Windows Platform (UWP) applications.

It has a minimal, light impact on performance while benchmarking, its integrated overlay allows you to view performance and statistics during gameplay. It is also vendor agnostic – enabling the collection of detailed, comparative data. One exception: AMD’s GPU power consumption API reports a value between chip power and card current, rather than the true values.

In short, if you want to see or collect real-time GPU performance and power data in games, FrameView delivers more of it with a higher degree of accuracy than many other tools and methods, making it the best app for benchmarking.

Characteristics

Reliable performance and power data

Detailed metrics are presented in real-time with a configurable overlay, and reported to a log file for hands-on analysis, utilizing PresentMon for analytics.

Extensive app and API compatibility

Unlike other measurement options, FrameView works with a wide range of graphics cards, all major graphics APIs and Universal Windows Platform (UWP) apps. In addition, it enables real-time current measurement through APIs, recording chip and board current* without the need for special physical equipment, while capturing detailed performance information.

FrameView in depth

If you want to know more about the metrics FrameView measures and why they are important to your gaming experience, keep reading.

Performance testing

All performance monitoring applications use system resources, which affects the recorded results. With our army of expert engineers, we have managed to reduce the cost of statistics tracking and recording, giving you more accurate results.

Our configurable overlay displays several performance metrics:

• Rendered frame rate: FrameView will measure and report timestamps at the beginning of the graphics pipeline. This metric indicates the smoothness of the animation delivered to the GPU
• Displayed frame rate: FrameView will measure and report timestamps at the end of the graphics pipeline. This calculation provides an indicator of what the user actually sees displayed on the screen
• 90th, 95th, and 99th percentile frame rates: Reviewers typically use 99th percentile calculations to determine whether a game’s minimum frame rate or frame time is close to average.
• If the 99th percentile frame rates are close to average, the game is smooth and consistent. If they aren’t, the game’s frame rate is likely inconsistent, resulting in micro-stuttering during gameplay, negatively impacting your experience
• Render current wait time: Render current wait time is the time from when present was called on the render thread until present was actually completed by the GPU. This measurement includes driver latency, how long the command was queued waiting for the GPU to render, and the actual GPU rendering time. Render delay can help determine how responsive a game can feel to an end user.

Pressing the reference hotkey assigned in the settings begins data capture for the predefined number of seconds, saving these and other statistics to file. To maximize performance, the overlay is hidden while the reference is being executed.

What is new

• FSR 3 Frame Generation is now supported with all metrics including PC Latency and FPS.
• Introducing “Scanout Color Bar”, a feature that makes it easy to detect round frames, frames that appear for an infinitesimal amount of time and artificially increase the FPS counter without actively contributing to smoothness. Just turn the feature on and a color bar will appear on the left side of the screen, changing color with each new frame displayed. Using a capture card (recommended) or high-speed camera with V-Sync Off / G-SYNC Off, you can visually tell when these round frames appear for only an infinitesimal amount of time, providing no visual benefit to the player.
• Note: Scanout Color Bar has some performance overhead, and as a result may negatively impact performance. We recommend turning it off during benchmarking.
• We are introducing the “10% high FPS” metric in the benchmark summary and summary files. 10% high is the average of the 10% fastest frame times, converted to FPS. 10% high FPS can be a quick way to tell if the player is seeing round frames, as round frames will express as a very high 10% high FPS compared to the average (eg: 1000 FPS)

To protect our users, we would like to share information about an issue we have discovered:

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