03-07-2024, 05:01 AM
(03-07-2024 12:09 AM)ToastyX Wrote: [ -> ]Yea, this is the only display I've had where I can't get CRU working, at all, not a single change is listened to.(03-02-2024 12:56 AM)Dreamic Wrote: [ -> ]Any idea what could be causing this?That looks like a signal quality problem, but if it's not the cable, then either it's an internal problem with the monitor, a bug in the monitor's firmware, or a bug in the GPU's driver with regard to DSC. If CRU doesn't have any effect, that's a GPU driver bug.
4 second clip:
https://i.imgur.com/g1gWFBC.mp4
Horizontal white line flicker on OLED, seemingly only at 360Hz, regardless of HDMI or DP cable or port, VRR on or off. I can find various results of different monitors, TV's, QDOLED, WOLED, Dell/Alienware, LG, MSI, 27", 32", etc of this issue.
No real solutions or explanations, besides lowering refresh rate which isn't much of a solution imo. Also CRU seems to do nothing on this specific display.
I've already amassed a list of like 15 people on Reddit who have commented in various places about having this issue with this monitor, and tagged MSI (even though the issue isn't exclusive to them, from what I've seen).
![[Image: twxSkTM.png]](https://i.imgur.com/twxSkTM.png)
I've also been encouraging everyone to make a ticket about it, hopefully they can get to the bottom of it. I was wondering if Blurbusters was getting one of these 3660Hz QDOLEDs, as if he was able to replicate the issue he would probably have an easier time getting MSI to listen.
Regarding DSC, they already confirmed they're working on a toggle for upcoming firmware, so we'll see if that changes anything. However, the issue is already only present at 360Hz, not 240Hz (the next highest option), even though DSC is forced on at all refresh rates and resolutions currently.
And when DSC is able to be disabled in new firmware, you still won't be able to run 360Hz 2560x1440 at 10bit without it, even though the monitor does have a proper 48gbps HDMI 2.1.
Blurbusters also suspects firmware issue currently. It's definitely not cable, it could be Nvidia driver or DSC. Or Samsung really screwed something up.
Anyways, I've done about all I can do, with others also brainstorming and trying various things. All that can be done is to get MSI's attention and hope something comes of it, I pray they're able to reproduce it so it's like locked in to being investigated. They'll have an easier time contacting Nvidia, Microsoft, or Samsung if they need to...
