It's typical for a manufacturer to state that a refresh rate is "overclocked" if the user needs to use an "overclock" setting in the OSD to be able to use a refresh rate. I'm assuming that is the case here, it is on other models that I've tested with this G-SYNC module (such as the AOC AG352UCG6). If the overclock was just done completely passively and was always enabled, that's different.
I don't understand how that makes any sense.
It's not the options in the OSD that determine what constitutes an "overclock".
A though experiment:
Take a normal monitor with a native 120Hz panel (no overclock) and restrict it to run only at 100 Hz. Then allow this restriction to be removed via the OSD menu, again allowing the panel to reach its native 120 Hz refresh rate. Does that mean the panel is overclocked? Of course not, but that's essentially the argument you made (as I understand it).
The AOC AG352UCG6, and every other overclocked monitor I can think of, are a completely different story. These monitors are justified in requiring an explicit overclock setting. As a user, when you set that, you're saying "I know the panel in my monitor isn't designed to run at this higher refresh rate, and might show artifacts, discoloration, overshoot, flickering, or other issues when refreshing at this higher speed. However, I'm willing to make those sacrifices in exchange for the faster refresh rate".
This is how OEMs limit their liability when the display isn't perfect at that higher refresh rate. I think this is fine.
If LG is only overclocking the g-sync module however (not the panel), then you won't have any of these issues. For what then, would you have to explicitly allow overclocking in the OSD? It seems pointless. The only potential downside is a slightly higher power draw.
On the other hand, see my previous post on how this seems to be a deliberate attempt to misinform.
I'm somewhat baffled that you don't seem to see an issue here, so I wonder why we see this differently.
Last edited: