Frametime with in game cap vs RTS cap is night and day?
Posted: 14 Jul 2019, 04:33
Testing Fortnite here with ULMB on at 120 hz.
Vsync off in both in game and nvidia
I tested Fortnite with RTS set to 0 for both scanline and framerate cap and instead I capped Fortnite to 120 FPS using in game counter and here are my results:
Run 1: https://imgur.com/Z78tBQK
Run 2: https://imgur.com/o8VLssf
Then I set Fortnite FPS to unlimited and set RTS to 120 and set scanline to 0 and only did for 1 run:
https://imgur.com/5FacWGt
Finally, I kept Fortnite at unlimited, set RTS to 0 for framerate and set scanline to -50 and only did 1 run:
https://imgur.com/vj7gqZA
Can anyone please explain the difference for me? Why the hell is my frametime all over the place when I am using an in game lock?! Not only is it all over the place, it never went under 9.6 MS and my spikes were 35 MS+
RTS cap on the other hand, not only was my frametime flat much more compared to runs 1 and 2 using the in game limiter, BUT my spikes were not more than 25 MS at max but mostly 20 MS and below and my frametime was usually at 8.3 MS
RTS scanline is more or less the same compared to the RTS framerate lock (I would argue the framerate lock is possibly even slightly more smooth than the scanline?) but one of them eliminates the tear and the other doesn't so its okay, but again both graphs are night and day compared to in game cap. So what gives? Why does my frametime is not only flat but also averages less and the spikes are also much less compared to an in game cap?
I ran the test in playground from the same location so I can keep things consistent and did no hard reboots to the PC.
Vsync off in both in game and nvidia
I tested Fortnite with RTS set to 0 for both scanline and framerate cap and instead I capped Fortnite to 120 FPS using in game counter and here are my results:
Run 1: https://imgur.com/Z78tBQK
Run 2: https://imgur.com/o8VLssf
Then I set Fortnite FPS to unlimited and set RTS to 120 and set scanline to 0 and only did for 1 run:
https://imgur.com/5FacWGt
Finally, I kept Fortnite at unlimited, set RTS to 0 for framerate and set scanline to -50 and only did 1 run:
https://imgur.com/vj7gqZA
Can anyone please explain the difference for me? Why the hell is my frametime all over the place when I am using an in game lock?! Not only is it all over the place, it never went under 9.6 MS and my spikes were 35 MS+
RTS cap on the other hand, not only was my frametime flat much more compared to runs 1 and 2 using the in game limiter, BUT my spikes were not more than 25 MS at max but mostly 20 MS and below and my frametime was usually at 8.3 MS
RTS scanline is more or less the same compared to the RTS framerate lock (I would argue the framerate lock is possibly even slightly more smooth than the scanline?) but one of them eliminates the tear and the other doesn't so its okay, but again both graphs are night and day compared to in game cap. So what gives? Why does my frametime is not only flat but also averages less and the spikes are also much less compared to an in game cap?
I ran the test in playground from the same location so I can keep things consistent and did no hard reboots to the PC.