Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Why do you think I've included 1% low and minimum FPS data in my videos? It'll be included in the 4K native video too with RT enabled.You said game runs very well, but then the frametime did not look smooth which was intriguing
You said game runs very well, but then the frametime did not look smooth which was intriguing
Here's a completely flat frame time graph from a great video with a 12900K and a 6950 XT overclocked, getting worse 0.1%, minimum and average FPS than my 5800X3D and my 6950 XT setup, which had a frame time graph that is not always flat, especially in cut scenes.Why do you think I've included 1% low and minimum FPS data in my videos? It'll be included in the 4K native video too with RT enabled.
@TNA I figured out what was causing the (false) spikes in the frame time overlay, my custom overlay. Oddly, it only affected a few games, Spiderman, Far Cry 6, Days gone and a few others. Other games like COD, Dying Light 2, Red Dead Redemption 2 were unaffected. I rebuilt it from scratch and now its back to a flat line in all games.Here's a completely flat frame time graph from a great video with a 12900K and a 6950 XT overclocked, getting worse 0.1%, minimum and average FPS than my 5800X3D and my 6950 XT setup, which had a frame time graph that is not always flat, especially in cut scenes.
What's the moral of the story I hear you ask? Always include the 0.1% and minimum FPS on your overlay because they will show any issues with frame pacing and VRAM saturation. A frame time graph is clearly not enough on its own.
4K Very High Settings + FSR2.
4K Very High Settings No FSR2.
Game is comfortably using 12GB at 4K too.
Suspect the modded version using dlss files will look/work better overall than the official integration. Reminds me, I need to do another play through and choose different scenarios to my first playthrough.
Hope to see some comparisons, I'm not flush enough to get Dying Light 2 yet otherwise I'd check for myself.
Currently on sale
Sadly still a no go even at 30 quid, The place I worked at shutdown so I have to budget very carefully until I'm financially stable again.
Suspect the modded version using dlss files will look/work better overall than the official integration. Reminds me, I need to do another play through and choose different scenarios to my first playthrough.
Be handy as I loaded the game up with mods including the fsr mod but haven't played it yet.Hope to see some comparisons, I'm not flush enough to get Dying Light 2 yet otherwise I'd check for myself.
Here is a side by side comparison. IQ looks similar, but DLSS is around 6-7 FPS (it fluctuates) faster in this screenshot.Hope to see some comparisons, I'm not flush enough to get Dying Light 2 yet otherwise I'd check for myself.
Uhmm naaa.Here's a completely flat frame time graph from a great video with a 12900K and a 6950 XT overclocked, getting worse 0.1%, minimum and average FPS than my 5800X3D and my 6950 XT setup, which had a frame time graph that is not always flat, especially in cut scenes.
What's the moral of the story I hear you ask? Always include the 0.1% and minimum FPS on your overlay because they will show any issues with frame pacing and VRAM saturation. A frame time graph is clearly not enough on its own.
4K Very High Settings + FSR2.
4K Very High Settings No FSR2.
Game is comfortably using 12GB at 4K too.
Yup, my post was completely unrelated to stuttering caused by VRAM usage. It turned out to be an incorrect setting in my overlay which was causing false spikes. I redid it from scratch and the problem was solved.Uhmm naaa.
Vram saturation looks like this:
The opposite of stutter.
Did not see your later post, my bad, helps to distinguish what Vram capping out looks like though.Yup, my post was completely unrelated to stuttering caused by VRAM usage. It turned out to be an incorrect setting in my overlay which was causing false spikes. I redid it from scratch and the problem was solved.
Yeah the comment about VRAM usage was just what I saw. I have cards with 16GB and 24GB so 12GB usage was not a problem regardless.Did not see your later post, my bad, helps to distinguish what Vram capping out looks like though.