Novuake :
bystander :
Virtu MVP does not increase actual FPS. Virtu MVP is a technique to reduce latency by attempting to shrink the time between a rendered frame and how long it takes to be displayed. If the call to render a frame is too soon, it will not render the frame, even though a FPS counter will count that call as a rendered frame. It does this in order to sync up the frames rendering and when it is displayed better than normal. It however artificially increases FPS counters.
Interesting...
Source maybe? If you don't mind... I would like to read more on what FPS counters are not effected by this.
All FPS counters that I'm aware of are affected by this, unless it is one of these that count displayed FPS with a DVI capture card described here:
http://www.pcper.com/reviews/Graphics-Cards/Frame-Rating-New-Graphics-Performance-Metric
(this is an article talking about crossfire issues, but the same type of card would give accurate FPS readings).
This explains what Lucid Virtu MVP actually does:
http://www.anandtech.com/show/5728/intel-z77-panther-point-chipset-and-motherboard-preview-asrock-asus-gigabyte-msi-ecs-and-biostar/2
http://www.futuremark.com/pressreleases/60555
I believe the first link there tells you how it intercepts frames and does not render them because they would just sit in the frame buffer. It does this to get more up today information, and render the frame much closer to the refresh time of the monitor. This process inflates FPS counters.
It does sound like Futuremark is currently working with Lucid to come up with a way to correctly count the FPS. That said, the technology has latency improvements which make a game more responsive, though I've heard a number of issues with it as well, such as not working well with SLI/CF, if at all.
Facebook
Twitter
Instagram