G-SYNC and RTSS

[Anonymous893125]

and also if theres a game thats locked to 60 fps do i need to lock it myself to 60 or will it already being locked to 60 be enough,

and another thing if i got v sync enabled in nvcp and g sync ect and the game has no built in v sync option to toggle on or off what to do then ? just keep v sync on ?

[jorimt]

in RTSS if i got one fps limit in global set to lets say 80, then in RTSS for a program do the two overlap ?

Limiters can overlap and potentially cause conflicting behavior if set too closely to each other, say within 5 frames, especially between two external limiters (say stacking NVCP MFR with RTSS).

I.E. one set to 80, and another set to 100 should be fine, whereas one set to 80, and another set to 82 is not as recommended, generally. The limiter with the lowest value will be the one that activates whenever the framerate reaches it.

and also if theres a game thats locked to 60 fps do i need to lock it myself to 60 or will it already being locked to 60 be enough,

If the game is internally hard-locked to 60 FPS, there's typically no reason to use an external limiter on top of that unless the internal limit has noticeably poor frametime performance (stutter/jitter).

if i got v sync enabled in nvcp and g sync ect and the game has no built in v sync option to toggle on or off what to do then ? just keep v sync on ?

Short answer? Yes; NVCP V-SYNC + in-game V-SYNC = same flag enabled at the driver level, thus you can't really enable V-SYNC "twice."

The only reason disabling in-game V-SYNC with G-SYNC is generally recommended is because the in-game V-SYNC option may engage other behaviors unrelated to V-SYNC that may or may not be beneficial to G-SYNC operation.

[Anonymous893125]

ok so for the first part if ive got two program fps limits in rtss they wont overlap right ?

[jorimt]

ok so for the first part if ive got two program fps limits in rtss they wont overlap right ?

RTSS counts as a single limiter. It has a global profile that you can apply an FPS limit to, and per app profiles that you can add to override its global limit. E.g. You cannot limit the same game "twice" with RTSS.

In other words, if you set the "Framerate limit" under "Global" in RTSS to 120, and then set it to 80 under "Deathloop.exe," the Deathloop profile will override the "Global" profile and use the 80 instead of the 120 limit for that game, and if you remove the limit in the Deathloop profile (aka "0"), it will fall back to the global limit (if set).

[Anonymous893125]

ok thank you, how about if i got a game with no vsync option in game then enable v sync in nvcp but v sync has no effect what would i do in that scenario ?

[Anonymous893125]

and what about if i had in rtss one program profile set to 80 and another program set to 81 would the two overlap then ? or not as its per program ? only thing that would be at danger of overlapping would be global and program right ?

[jorimt]

ok thank you, how about if i got a game with no vsync option in game then enable v sync in nvcp but v sync has no effect what would i do in that scenario ?

There would be nothing you can do, you'd just have to use G-SYNC on + V-SYNC off + FPS limit. But the game not having a V-SYNC option and NVCP V-SYNC not working in that same game is incredibly rare. I've never come across that myself.

and what about if i had in rtss one program profile set to 80 and another program set to 81 would the two overlap then ? or not as its per program ? only thing that would be at danger of overlapping would be global and program right ?

Again, RTSS can't overlap itself. If you have the in-game limiter set to 80, the RTSS limiter set to 81, and the NVCP MFR limiter set to 79 at the same time for the same game, you'll probably run into frametime performance issues.

Ideally, you want to use a single limiting method per game; for normal scenarios, there's no reason to stack them.

[Anonymous893125]

ok so within RTSS global will not overlap with per program right ?

[Anonymous893125]

"Limiters can overlap and potentially cause conflicting behavior if set too closely to each other, say within 5 frames, especially between two external limiters (say stacking NVCP MFR with RTSS).

I.E. one set to 80, and another set to 100 should be fine, whereas one set to 80, and another set to 82 is not as recommended, generally. The limiter with the lowest value will be the one that activates whenever the framerate reaches it."

when you say this if ive got two profiles in rtss one for 1 game 1 for another 1 being 80 fps and another being 82 fps also a global fps limit will be active (within rtss) would any of this overlap im confused because you said within 5 frames but also said rtss cant overlap so im confused

[Anonymous893125]

using that as the scenario