G-SYNC and RTSS

[Anonymous893125]

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

and if im using the global limit to limit a game not in the list per program , that would be a "single limiting method " is that right

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.

are you refering to global and per program within rtss ?, do you mean if i set global to 80 then a program to 82 the two may overlap ? (in RTSS)

[jorimt]

and if im using the global limit to limit a game not in the list per program , that would be a "single limiting method " is that right

are you refering to global and per program within rtss ?, do you mean if i set global to 80 then a program to 82 the two may overlap ? (in RTSS)

As far as our particular discussion goes thus far...

"Single" limiting method counts as having only one of the below enabled globally or per game:

1. In-game limiter - "internal" method
2. RTSS limiter (either globally or per profile) - "external" method
3. NVCP MFR limiter (either globally or per profile) - "external" method

"Stacked" limiting methods counts as:

#1, #2, or #3 (listed as single limiting methods above) + any of the others numbered active at the same time, either globally or for the same game at the same time + a limit on each that are above, say 10 frames of each other = safe, but typically overcomplicated versus either using a single limiter per game, or a single global limit for all games using one external method.

"Overlapping" limiting methods counts as:

#1, #2, or #3 (listed as single limiting methods above) + any of the others numbered active at the same time, either globally or for the same game at the same time + a limit on each that are within 5 or so frames of each other = not always safe.

Again, the lower limiter will prevent the higher limiter from activating, so if you have an in-game limit of 60, and an RTSS limit of 120 (either globally or just for the current game), then the lower limit is the only one that will take effect.

Reverse that, with the RTSS limit at 60, and the in-game limit at 120, and again, the lower limit will be the only one that will take effect.

It doesn't matter how many limiters you stack or overlap, whatever limiter is set lowest will be the only limiter that takes effect, unless, again, you set them too close (within 5 or so frames of each other), at which point frametime variances output by imperfect system performance can make the framerate overshoot the lowest limiter periodically and activate the limiter that is set slightly higher, potentially creating more frametime performance issues as they both try to regulate the maximum average framerate using different processes at the same time.

[Anonymous893125]

ok i think i understand so just so im clear, so when using only the global and per program within RTSS, i dont need to worry about overlapping because it just cant overlap right ?

as for mixing RTSS with an in game one if rtss GLOBAL set to 80 and ive got one in game set to 90 = safe ?

RTSS GLOBAL set to 80 and in game set to 85 = not always safe ?

also the lower fps limiter will be the only one that takes effect right

[Anonymous893125]

do you guys just alter the global for every game ?, just wondered because it seems easier haha

[jorimt]

ok i think i understand so just so im clear, so with just RTSS then i dont need to worry about overlapping because it just cant overlap right ?

Correct. No framerate limiting method, including RTSS, can overlap with itself.

I.E. if you have a global RTSS limit set, and an application profile RTSS limit set, the application profile limit will replace the global limit for that game. They literally can't be active at the same time in that case, since they're the same parameter. RTSS simply internally switches that global value (if set) to your application profile value whenever the game launches.

Same behavior as the above goes for if you're only using Nvidia MFR.

as for mixing RTSS with an in game one if rtss GLOBAL set to 80 and ive got one in game set to 90 = safe ?
RTSS GLOBAL set to 80 and in game set to 85 = not always safe ?

Typically, yes.

also the lower fps limiter will be the only one that takes effect right

Yes, again, so long as any of the higher limits aren't too close to (within a few frames of) the lowest limit.

[jorimt]

do you guys just alter the global for every game ?, just wondered because it seems easier haha

I personally do not use a global limit, and instead choose whatever limiting method I find best for my use-case per game (be it in-game, RTSS, or Nvidia MFR) and switch them around as needed on the fly all the time.

YMMV, of course.

[Anonymous893125]

Yes, again, so long as any of the higher limits aren't too close to (within a few frames of) the lowest limit.

i understand all of it except what you said there, i thought the lower limit takes priority regardless ?
update i understand , thanks man for being so patient

[jorimt]

update i understand , thanks man for being so patient

You're welcome.

[Anonymous893125]

just been wondering now you know when you can press f 11 to go full screen ? if i got a game in borderless would pressing f 11 make it exclusive fullscreen or would this not make a difference ?

[Anonymous893125]

update i understand , thanks man for being so patient

You're welcome.

have you had chance to check this out yet man ?