Monitor Ghosting, Pixel Response Time & Overdrive Lab
Detect trailing motion blur, tune overdrive levels, and eliminate inverse overshoot halos across IPS, OLED, and VA displays.
Ghosting (Trailing Blur): Occurs when pixel transitions (GtG) are too slow to keep up with the monitor refresh rate.
Inverse Ghosting (Coronas / Halos): Occurs when monitor Overdrive / TraceFree is set too aggressively ("Extreme" or "Fastest"), causing pixel voltage to overshoot the target color.
Ghosting & Response Time Moving Grid Lab
Track the moving high-contrast grid with your eyes. Identify whether your panel exhibits normal trailing ghosting (slow response), inverse ghosting coronas (excessive overdrive overshoot), or flawless motion clarity.
What Do You See on Your Physical Screen?
Select what your eyes observe as the grid scrolls to receive instant OSD overdrive adjustments.
Caused by voltage overdrive overshoot. The liquid crystals were over-volted past their target luminance, producing an inverted bright outline.
Caused by slow pixel response (GtG > refresh frame window). Common on VA panels or IPS monitors with Overdrive turned completely off.
Ideal balance. Overdrive voltage accelerates pixel state change perfectly into the refresh interval without overshoot or smearing.
Common Performance FAQs
Hard-won engineering truths regarding frametime pacing, input latency, sub-timing latency, and competitive OS tuning.
Standard in-game FPS counters only sample the mathematical average across thousands of frames over a full second. They do not tell you when individual frames take significantly longer to render.
If your monitor refreshes every 4.16ms (at 240Hz), but a cache-miss, background Windows service, or shader compilation causes a single frame to stall for 18ms, your eye perceives a distinct micro-stutter. The FPS counter might still show "235 FPS", but your 1% and 0.1% lows plummeted to 55 FPS.
To fix this: optimize memory sub-timings to eliminate memory-bus stalls, cap framerates to keep GPU utilization under 97%, and eliminate background DPC latency spikes using LatencyMon.
Focus on 1% Lows and frametime consistency rather than peak average FPS for butter-smooth tracking.