I accept and forgive a bit of leeway, but for 120fps COD and a lot of these 60fps console games, they need more than 'a bit of leeway' in order to fit within their frame rate bracket.
A lot of console games run a pretty flawless 60fps, and other only target 60fps.
And I think it's important that the difference is understood.
I just randomly sampled the
linked video. It's consistently at 120 fps, only occasionally dipping to 110 (one sample out of 6, in the water area). XBSX was more variably, and XBSS all over the place, suggesting my random sampling is indicative. COD on PS5 is clearly 120 Hz. We can qualify that even as 'solid', unless I happened by chance to skip all the points where the framerate nosedived.
Yep. the DF video is also mostly a stable 120 with moments of dropping towards 110.
There is no definition of 'targeting' and 'achieving'. 100% faultless framerate basically doesn't happen unless your game in undemanding. For everything these machines were designed for, 99% of the time at a framerate is easily "runs at xxx fps'. Games that spend half their time below that are 'targeting xxx fps'. Those that get closer more of the time...there is no definition and it's not worth arguing over unless that really is essential to the debate at hand.
For the sake of moving this conversation forwards, I concur with DF who state this is a "genuine 120 Hz take on Warzone" and decree that a 120 fps game is what COD is managing on PS5, and we can call any game on PS5 Pro running as much of the time at 120 fps with the same ballpark spread of framerate to also be "120 fps."
Anyone wanting to use a specific all-the-time 120 fps standard should clarify it "locked 120 fps" or "100% 120 fps".
Let's move on and get back to talking about PS5 Pro, not MS's games quality or what definition to use for framerate or light transport definitions for trying to decide if PS5 is white or blue...