Monitor OSD odd behaviour

[nav1204]

Hello! I have a Lenovo G24-10 monitor with a 48-144hz freesync range. I run it at 120hz though as there is very high idle power on my rx580 when in 144hz, unsure if this is gpu issue or monitor issue. I usually cap my games at 117hz and make sure to have freesync + vsync on. However I have noticed some strange behaviour, for example, when I am playing any game at locked 117hz (with RTSS), and the frametime is a consistent 8.5ms (verified with RTSS graph), the monitor OSD displays refresh rates from 110hz all the way up to 120hz.

1. Is this behaviour expected/normal? Or is there a potential fault with my monitor.
2. When the monitor displays 120hz, and my fps is 117hz, is the monitor actually refreshing at 120hz (so that v-sync is taking control?), or is it actually refreshing at 117hz (with no v-sync)?
3. I can send a video if needed.


Thanks!

[RealNC]

Moved to freesync section.

[jorimt]

1. Is this behaviour expected/normal?

Yes, it's "normal."

Those monitor-side refresh rate meters, especially on G-SYNC Compatible FreeSync displays, can't be relied on for accuracy; as long as said meters are fluctuating (meaning VRR is engaged), you should rely on system-side readouts for monitoring average frame/refresh rates instead.

[nav1204]

1. Is this behaviour expected/normal?

Yes, it's "normal."

Those monitor-side refresh rate meters, especially on G-SYNC Compatible FreeSync displays, can't be relied on for accuracy; as long as said meters are fluctuating (meaning VRR is engaged), you should rely on system-side readouts for monitoring average frame/refresh rates instead.

Thanks, any comment on my second question?

[jorimt]

Thanks, any comment on my second question?

With VRR, the duration of each scanout cycle is determined by the current max refresh rate (8.3ms at 120Hz), while VRR itself controls how many times that scanout process repeats per second based on the current framerate.

I.E. 117 FPS 120Hz VRR = scanout cycle repeats 117 times per second, with each scanout cycle completing in 8.3ms per.

[nav1204]

Thanks, any comment on my second question?

With VRR, the duration of each scanout cycle is determined by the current max refresh rate (8.3ms at 120Hz), while VRR itself controls how many times that scanout process repeats per second based on the current framerate.

I.E. 117 FPS 120Hz VRR = scanout cycle repeats 117 times per second, with each scanout cycle completing in 8.3ms per.

Thank you. So even if my monitor is displaying a current refresh rate of 110-120hz, and my fps is 117hz, I should not trust the monitor, and providing I am not seeing any tearing, the monitor is doing what it should (117 cycles per second)

[jorimt]

Thank you. So even if my monitor is displaying a current refresh rate of 110-120hz, and my fps is 117hz, I should not trust the monitor, and providing I am not seeing any tearing, the monitor is doing what it should (117 cycles per second)

Again, those monitor meters are basically toys.

In order of reliability/accuracy:

1. Monitor-side VRR meter on G-SYNC native display containing module.
2. Monitor-side VRR meter on FreeSync display with AMD GPU in FreeSync mode.
3. Monitor-side VRR meter on FreeSync display with Nvidia GPU in G-SYNC Compatible mode.

If it's fluctuating = VRR currently engaged, if it's static (and the number is fixed at the current max refresh rate) = VRR is not currently engaged.

Unlike system-side average framerate counters, some of these monitor-side meters also include LFC multiples in their number, confusing things further.

I.E. as long as your monitor-side VRR meter is fluctuating, and your system-side average framerate counter is displaying the correct number (that being an average framerate at least 3 frames within the current max refresh rate), then VRR should be working as expected.