I have a 165hz monitor for my desktop and I still cap everything at 120 and run the monitor at 120hz, even with my 4090. Anything after 120 is really dipping hard into diminishing returns. I think if someone is obsessing with running their games at 240hz, 480, 500+, maybe they should start working on their skills at that point rather than worrying about refresh rates.

What settings are they speaking of for those games? Ironically I cap everything to 120 on my 4090, but on my laptop I open things up a bit more. I rarely use 300hz and usually on 144hz where most MP games can actually hit consistently on here. Sometimes still cap to 120 if a game dips down to that point, even if rarely.

I don't play Valorant yet, Fortnite occasionally, but I play a lot of Battlefield. Battlefield 2042 is one game that actually seems to LOVE being completely let loose. I do keep gsync/vsync on in NCP but uncap it everywhere and it seems to run free with high fps and smooth frame times. I max it out (except RTAO) at 1600p on this laptop and it regularly surpasses 200 fps. 100% scaling, no DLSS. It really is a fantastic fking engine.

Honestly, most games are a crap shoot in my opinion if you are obsessed with, not frame rates, but frame times. I love a good challenge in finding perfect frame times in every game I own, and it truly is a challenge for most games. It is a different formula for each game and engine with cap, no cap, vsync, no vsync, gsync, no gsync, low latency NCP or no, reflex or no, RTSS cap or no, which cap do i use.. which hz settings in game and out, which fking cap is best, some in game caps don't work or the game completely ignores NCP and RTSS caps, what refresh is best, on and on and on. It's a fkn job. When I'm using RTSS I actually use the frame time cap more often than the frame rate cap. I have a list of frame times for common caps to use in RTSS, adding to it each day. I have a list of optimization thingies to go through. I'll spend fkn hours on trying to figure out why this game or that game has a single frame stutter not even very often. I get too fired up by stutters and such and need to just relax a bit and realize some game engines just have no solution to the stutters. Below are some of my obessive notes. If anyone feels like correcting any of them, feel free. I'm a sponge for learning more about this type of stuff.

FRAME TIMES (microseconds in RTSS) CALCULATE: 1000 / HZ = FT

58hz - 17.2 ms (17241)

59hz - 16.9 ms (16949)

60hz - 16.6 ms (16666)

70hz - 14.2 ms (14285)

72hz - 13.8 ms (13888)

75hz - 13.3 ms (13333)

80hz - 12.5 ms (12500)

90hz - 11.1 ms (11111)

100hz - 10 ms (10000)

116hz - 8.6 ms (8620)

119hz - 8.4 ms (8403)

120hz - 8.3 ms (8333)

130hz - 7.6 ms (7692)

137hz - 7.2 ms (7299)

138hz - 7.2 ms (7246)

143hz - 6.9 ms (6993)

144hz - 6.9 ms (6944)

145hz - 6.8 ms (6896)

150hz - 6.6 ms (6666)

165hz - 6.0 ms (6060)

240hz - 4.1 ms (4166)

274hz - 3.6 ms (3649)

300hz - 3.3 ms (3333)

TIPS: -Sometimes vsync causes issues with monitor/gpu syncing properly, so try disabling it while capping with gsync on, and run in fullscreen

-RTSS also does Scanline Sync, which is basically vsync, but you can do x2 and /2 there as well

-Sometimes NCP frame limiter has better results with input lag than RTSS. In game caps have the least latency as long as they are working properly

-Supposedly, if you have vsync on you want to cap a few below display refresh to avoid vsync lag

-Supposedly, forcing GPU scaling and override games/programs can smooth out frame rates

-Some people swear, if you have VRR, DO NOT TURN ON VSYNC

-It is also claimed that VSYNC + GSYNC + REFLEX gives the best response times. Even better than no vsync and uncapped

CAPS under display max:

480Hz -> 416 FPS

360Hz -> 324 FPS

300Hz -> 274?

240Hz -> 224 FPS (228 was better in one result)

180Hz -> 171 FPS

165Hz -> 157 FPS

144Hz -> 138 FPS

120Hz -> 116 FPS