LG OLED C1/C2 VRR On or Off? Decide Per Game

Quick Answer

There is no universal VRR on/off answer for LG C1/C2. Keep VRR on when a game varies within the supported range and the result is smoother, tear-free and free of objectionable near-black flicker. Turn it off for a title when frame delivery is already locked to a stable fixed refresh, when dark gameplay flicker outweighs tearing/stutter benefits, or when the title's menus/loading cadence is intolerable. Save the decision per game/source.

Test the same demanding checkpoint four ways: VRR on uncapped, VRR on with one sustainable cap, fixed refresh with V-Sync, and fixed refresh without V-Sync. Record frame time and input feel rather than relying on average FPS. HDMI VRR is designed to reduce lag, judder and tearing, but a stable fixed mode can be preferable when the engine delivers consistent frames.

Symptom Checklist Before Choosing

Camera pans tear horizontally with VRR off and V-Sync off.

A variable-quality mode judders at fixed refresh but looks smooth with VRR.

Dark rooms pulse only while VRR is active and frame time varies.

Loading screens flicker, but normal gameplay remains stable.

A locked 60 fps title looks identical with VRR on and off.

Fixed V-Sync removes tearing but makes controls feel less immediate.

Full blackouts or colored frames occur; those require link/GPU diagnosis, not a preference decision.

Causes and Trade-offs You Are Choosing

Tearing

With synchronization off, a new frame can arrive while the display is scanning another, producing a horizontal tear. It may be obvious in slow camera pans or barely noticed at high frame rates. VRR aligns refresh with frame delivery within its range; fixed V-Sync also prevents tearing but queues/paces frames differently.

Stutter and frame pacing

A fixed 60 Hz display presents frames on fixed intervals. A game that fluctuates between targets can repeat frames unevenly and judder. VRR accommodates changing intervals, but it cannot make a CPU stall smooth. Stable 40, 60 or 120 fps with correct fixed cadence may look better than wildly varying VRR.

Latency

Latency depends on render queue, synchronization, frame cap, game engine, Reflex/Anti-Lag behavior and whether FPS hits the refresh ceiling. NVIDIA notes VRR can provide tear-free play below refresh without conventional V-Sync latency. That is not a promise of identical latency in every configuration. Measure or compare the real title.

OLED near-black flicker

C1/C2 can show brightness variation in dark tones when refresh intervals change. Severity depends on scene darkness and frame-time variation. VRR is not “broken” merely because one loading screen flickers, but disabling it is valid if dark gameplay is uncomfortable.

Performance headroom

A cap below a sustainable performance ceiling can stabilize frame time and avoid repeatedly hitting maximum refresh. A cap too high changes nothing; one too low sacrifices responsiveness/motion. There is no magic 117 FPS rule for every source, title and sync configuration.

Step-by-Step Per-Title Decision

1. Select a representative checkpoint

Use one demanding gameplay section, one dark scene and the title's loading/menu sequence. Record resolution, refresh, HDR, graphics mode, driver/game version and whether frame generation is active. Do not choose only an easy tutorial room.

2. Establish the console/PC target

Determine whether the game targets 30, 40, 60 or 120 fps and whether it genuinely supports VRR. On consoles, a 40 fps mode often expects 120 Hz output for even cadence. On PC, verify G-SYNC/FreeSync is active on the intended display and use Game Optimizer information as supporting evidence.

3. Test VRR on without assumptions

Run the checkpoint and log frame time. Note tearing, judder, dark flicker, responsiveness and any full blackouts. A blackout or colored corruption is not a quality trade-off; diagnose cable/handshake/GPU separately.

4. Add one sustainable cap

Choose a cap the demanding checkpoint can hold, with suitable headroom below maximum refresh according to platform/sync guidance. Use only one limiter. Retest motion, frame-time variance and flicker. If the cap stabilizes gameplay but not loading stalls, judge loading separately.

5. Test fixed refresh with V-Sync

Disable VRR, restart the title where needed, and use a fixed refresh compatible with the target. Enable the platform/game's appropriate V-Sync. This removes tearing but may add latency or stutter when performance misses cadence. Compare the same camera movement and control action.

6. Test fixed refresh without V-Sync

This can minimize synchronization latency but permits tearing. Competitive players may prefer the response at high FPS; cinematic players may find tears unacceptable. Do not claim one preference is objectively correct.

7. Evaluate dark and bright scenes separately

Near-black flicker can decide the result even if bright combat is smooth. Conversely, loading-only flicker may be an acceptable cost for hours of tear-free gameplay. Record where the problem occurs and for how long.

8. Save a title-specific choice

On PC, use a per-application driver profile where supported rather than changing every game. On console, remember that system VRR support and game implementation vary. Recheck after major game/driver/firmware patches because performance and compatibility can change.

Practical Decision Examples

Stable 60 fps single-player game: fixed 60/120 Hz with V-Sync may be smooth enough; VRR can remain on if it adds no flicker.

40–60 fps variable quality mode: VRR often reduces judder/tearing, but evaluate dark scenes and the lower VRR boundary.

Competitive game above 120 fps: at a 120 Hz TV, VRR plus an appropriate cap can prevent tearing; fixed uncapped output may feel responsive but tear. Reflex/Anti-Lag and game settings matter.

30 fps cinematic mode: VRR cannot invent frames. A fixed 60/120 Hz cadence may be appropriate; motion stutter from low frame rate remains.

Loading-only flicker: keep VRR if gameplay benefit is clear, or disable per title if the menus are prolonged or uncomfortable.

Cautions

Do not crush shadows, raise Black Stabilizer or alter service menus to hide flicker. Do not edit EDID/VRR ranges as the first experiment. Do not stack game cap, driver cap and third-party limiter. Rapid flicker can affect photosensitive users; stop testing when uncomfortable. Pixel Cleaning and picture calibration do not fix frame pacing.