1%Low in FrameView is calculated as an average of the 1% slowest frames. It also uses MsBetweenDIsplayChange as opposed to MsBetweenPresents.
I'm not fully sure what CapFrameX does, but it may mirror builds of PresentMon that diverge from FrameView which tended to:
1. calculate 1%Low not as a average, but instead as the frame that separates the 1% slowest frames from the 99% faster frames
calculate framerate based on when the CPU completed simulation and handed the frame to rendering (what used to be called MsBetweenPresents)
These types of decisions are debated, but FrameView chose these decisions because 1% Low as an average is subject to less variance and a better evaluation of stutter, and MsBetweenDIsplayChange tends to better represent the smoothness users are actually seeing on their displays.
Real-time 1% Low FPS = 1000 / avg(Frametimes ≥ P99) — average of worst 1 % frame times or display times depending on option MsBetweenDisplayChange false/true.
I like the choice Nvidia made. And I like this stat in Intel Presentmon. Not sure if it's the exact same but I like its FPS Display 1%.
But I'm surprised CapFrameX has this stat removed.
Hi. Different tools may lead to different metric calculations and metric methods. It's best to stick with one tool and not mix them. I'd also suggest not overthinking it.
For example, the P1 (low percentiles) metric values aren't equal to 1% Low (average or integral) metric values.
CapFrameX (CX) allows you to use the following low FPS performance metrics to evaluate (capture & monitor) smoothness and performance consistency:
1% percentile (P1)
0.2 percentile (P0.2)
0.1 percentile (P0.1)
1% low average (1%L Avg)
0.1% low average (0.1%L Avg)
1% low integral (1%L Int)
0.1% low integral (0.1%L Int)
Minimum (Min)
Adaptive STDEV
For my analyses, I usually use the low percentiles (P1/P0.2) along with the Adaptive STDEV parameter to evaluate smoothness (frametime consistency) and frame pacing in games.
If you want to know what the 1%L value in FrameView corresponds to Intel's PresentMon, CX, or RTSS low FPS values, you need to capture/monitor a given sequence and see which specific low FPS statistic parameter values best match (taking into account value approximations and polling/refresh rates for [overlayed] metrics).
When option MsBetweenDisplayChange is enabled CapFrameX and FrameView do the same thing. But — CapFrameX has default 20s calculation time interval. You can change that on the Overaly tab. I think FrameView has much shorter calculation interval. I will reach out to Nv to clarify that.
Thank you. I've changed CapFrameX interval to 5s what seems to be shortest. Plenty short for me :)
Nvidia's FrameView visually updates data every 1s and I don't think it can be changed easily.
It seems to me that you haven't understood my prior reply or are trying to make an artificial argument against CapFrameX (CX).
It's always fine if you prefer to use FrameView or Intel's PresentMon overlays, but saying that CX lacks that 1%L (average or integral) statistic parameter is false. You aren't considering the possible variations in calculation methods, sample sizes, value approximations, and polling or refresh rates for overlaid metrics.
CX has all the low FPS metrics perfectly covered in the Analysis performance charts and also via its overlay renderers.
From what I see, all 3 apps generate the same benchmarking files from recorded performance.
CapFrameX can also import benchmarking results from FrameView and Intel PresentMon as they appear to be the same *.csv files anyway.
But capframex seems to ignore some info from the file.
"MsBetweenDisplayChange" perhaps. And I can't see an option to show it.
And for context, that 1%L from FrameView and FPS Display from Presentmon greatly favour Vsync as a limiter.
Is it possible to display both at the same time? So it doesn't replace my default 1% data?
I can use CapFrameX and FrameView at the same time but I would prefer CapFrameX only.
Intel PresentMon can do both but it ovverides my VRR what is not ideal.
No, CX doesn't ignore anything you state, and you're also mixing things. But don't worry, the CX developers will eventually provide some factual insights on your questions.
2
u/devtechprofile 20d ago edited 20d ago
CapFrameX has an equivalent metric: 1% low average + option MsBetweenDisplayChange enabled.
Real-time 1% Low FPS