Below is a list of the following changes in the FrameView 1.6.10930.35470227 release.
- All FPS metrics (Average FPS, 1% Low FPS, etc.) are now calculated based on MsBetweenDisplayChange, which is measured from when a frame is displayed on the screen to when the next frame is displayed on the screen
- Previously, FrameView FPS metrics were calculated based on MsBetweenPresents, which is the time between two application present calls
- MsBetweenDisplayChange better reflects what gamers see on screen, and better reflects the gaming experience
- Users can still find older MsBetweenPresents-based metrics in the log file (columns MinimumPresentFPS, MaximumPresentFPS, 1%LowPresentFPS, and 0.1%LowPresentFPS)
- Support for DLSS 4 and Reflex Frame Warp has been added for all metrics, including frametimes, FPS, PC Latency, and 1% Lows
- Added PCL support for Vulkan titles (ex: Indiana Jones and the Great Circle) and RTX Remix mods
- FrameView’s codebase has been upgraded from PresentMon 1.4 to now leverage PresentMon 2.2
Bug Fixes
- General improvements to compatibility
- Fixed a bug that could cause CPU/GPU metrics to freeze in the overlay
- Solved a rare memory leak issue when FrameView ran for exceptionally long sessions
To download FrameView, or for more information including the user guide, please go to https://www.nvidia.com/ja-jp/geforce/technologies/frameview/.