I'm not saying it adds anything on the actual compression level, but it is preventing MPO and I can't even get Independent Flip to work. I'm not sure why you are so upset with me, I'm just presenting it as I understand it. Perhaps these will be of help - one is 500hz with DSC on, other is with DSC off and using max supported 240hz. As you can see, MPO triggles then. I then can play at 240hz and have independent flip mode presented via presentmon monitoring.kyube wrote: ↑27 Feb 2025, 08:45What's up with these random accounts making threads & commenting with no data?
DSC does not add any noteworthy input delay, despite how many people want to try and feel something.
What most here are "feeling" is better refresh rate compliance due to lower refresh rates, hence placeboing themselves that DSC is the culprit (heavily due to the thread of a similar title of a somewhat-known placebo-induced user). This is very noticable on the PG248QP, which is completely compliant at 360hz, but heavily missing the mark at 540hz.
It adds 500ns (0.5µs) of delay, as per this: https://www.tesmart.com/blogs/news/what ... ession-dscStop spreading FUD.How Does DSC Work?
Display Stream Compression (DSC) is a mathematically lossy but visually lossless compression algorithm. This means that although there are some differences in the final image produced after compression, these differences are imperceptible to the human eye. DSC employs various encoding tools to achieve this and can deliver a 3:1 reduction in data size. It accomplishes this with only a 0.5-microsecond increase in overall latency, making it suitable for gaming without affecting the visual experience or gameplay.
Not a single display with DSC has measurably high total input lag, as seen with many reviews.
Look somewhere else in the input lag chain.
DSC causing input lag/heavy mouse feeling?
-
ekajjj
- Posts: 11
- Joined: 16 Jul 2021, 07:19
Re: DSC causing input lag/heavy mouse feeling?
- Attachments
-
- 500hzdscon.png (96.98 KiB) Viewed 700 times
-
- 240hzdscoff.png (144.45 KiB) Viewed 700 times
-
munk33
- Posts: 7
- Joined: 18 Jul 2026, 15:37
Re: DSC causing input lag/heavy mouse feeling?
did you ever find a solution to this on the PG27AQN? just grabbed got one used off amazon, paired with an rtx 5080 and logitech superlight 2 mouse, and i felt a very obvious floaty/delayed mouse sensation running at 360hz over DP 1.4 w/ DSC.DrNem wrote: ↑25 Apr 2025, 02:28I've experienced a similar thing. I don't understand how this could be if it doesn't show up in measurements (as long as they measure input lag in full-screen motion).
I've owned a PG279QM (IPS, 240hz) for years. Recently got a PG27AQN (IPS, 360hz) used.
After a few weeks with me not really understanding what was wrong I tried A/B:ing this yesterday - swapping monitor back and forth between DM rounds in CS2. Again - it's "feel" based now, not measurements - something I understand is a faux pas but I want to share my experiences.
No G-sync, ULMB or similar activated. FPS unlocked. FPS consistently way above the Refresh of either (450+). Playing at 2304x1440 stretched. Scaling on GPU.
The PG279QM feels snappier ("Mouse feel" as OP stated) at 240hz than the PG27AQN at 360hz. Utterly bewildering to me as all reviews, and specs, seem to state that the PG27AQN should be the faster monitor (TFT central measured refresh rate compliance and it looks really good at 360hz).
- kyube
- Posts: 1016
- Joined: 29 Jan 2018, 12:03
Re: DSC causing input lag/heavy mouse feeling?
Your wireless mouse adds AT MINIMUM ≥1 ms (10^-3 seconds) of delay to your total system latency chain. Take a look at Overclock.net for this discussion if you want a source.
DSC adds 0,5–1 µs (10^-6 seconds) of delay to your total system latency.
I'll even put this into perspective:
360Hz = 27778 µs
The DSC line-buffer delay = ~1.07 microseconds
That's 0.038% of a single frame's life span
It's not DSC.
The burden of proof in regards to “buggy firmware implementations” is on the one which claims they're buggy.
There's not a single online resource which was able to proove the claim that any DSC implementation is buggy & thus leads to a severe (millisecond range) total system latency increase.
evaluating xhci controller performance | audio latency discussion thread | "Why is LatencyMon not desirable to objectively measure DPC/ISR driver performance" | AM4 / AM5 system tuning considerations | latency-oriented HW considerations | “xhci hand-off” setting considerations | #1 tip for electricity-related topics | ESPORTS: Latency Perception, Temporal Ventriloquism & Horizon of Simultaneity | good lcd backlight strobing implementation list | display vs gpu scaling
