Below is a list of the following changes in the FrameView 1.7 release.
Customizable Overlay:
FrameView has new options for adapting the overlay to your liking! For the first time, FrameView will let you customize which metrics are reported in the overlay by selecting between various presets. You can even adjust font size, add a black background to the overlay to improve readability, and toggle on and off mode tags like “Full Screen Status”, “Tearing”, and “Vsync”.
High Frame Rate Support
Improved accuracy with FPS calculation in situations where games have very high Frame Rates (800+ FPS)
Bug Fixes
Fixed a memory leak during extended monitoring sessions with NVIDIA Reflex-enabled games
Fixed a bug related to rare circumstances where VSync, GSync and DLSS Frame Generation could misreport data
CSV files are now properly saved even if a game closes while FrameView is still recording a benchmark
Improved reliability of “exclude list”
General improvements to stability and compatibility
Game-Specific Bug Fixes
The Finals: Fixed a crash when closing FrameView while the game is running
Arc Raiders: Added support for this title’s anti-cheat, enabling overlays to properly show up
Starfield: Improved consistency and accuracy of PCL
Black Myth Wukong: Fixed an issue where Black Myth Wukong could occasionally misreport latency with DLSS Frame Generation
Battlefield 6: FrameView overlay now properly appears
Known Issues
When playing Counter-strike 2 in “Exclusive Full Screen” mode and running FrameView, the Windows User Account Control window (UAC) pop-up can cause the game to minimize and stop functioning
While running Counter-strike 2, if you close FrameView and relaunch it, FrameView can become unresponsive until Counter-strike 2 is shut down
FrameView currently does not support GPU stats when running an external GPU