This release introduces a redesigned overlay that renders as an independent window rather than drawing into the application’s back buffer.
Added additional hotkeys for triggering a benchmark
FrameView now accurately reports the frame generation multiplier when NVIDIA Smooth Motion is active
Improved FPS Reporting: FPS now correctly counts dropped and zero-display presents; this change allows the FPS metric to more accurately characterize the experience, as it will better report on stutter, 1% lows, 10% highs, etc. Please note, this means average FPS may, in some cases, read as slightly higher than before.
Known Issues:
The new overlay introduced in FrameView 1.9 requires Multi-Plane Overlay (MPO) support — this can introduce incompatibilities in some cases. Please note, even when the overlay is inactive, benchmarks can still be accurately captured. The legacy injection-based overlay remains available, and can be enabled by editing the “settings.ini” file in FrameVIew’s installation folder. Simply set EnableOverlay=True and EnableFVOverlay=False.
On systems where MPO is unavailable or disabled, enabling the overlay may force the game out of iFlip and increase presentation latency. One way to verify if a game has exited iFlip is if the“I” tag fails to appear in the new overlay, but does appear with the legacy overlay.
MPO and some display technologies are incompatible, such as Nvidia Image Scaling (NIS) and Dynamic Super Resolution (DSR).
Some OpenGL/VK applications use a legacy fullscreen flip that is incompatible with the new overlay. These applications take ownership of the screen, preventing the new overlay from showing up.
Mode tags F (fullscreen) and W (windowed) do not work on the new overlay architecture.
Scanout Color Bar is currently incompatible with the new overlay.
FrameView overlay is not available with Battlefield 6 anticheat.
