Blur Busters Forums

New firmware released.

It seems to have at least fixed the black crush at 240hz @ 2.2 gamma. I can now see square 5 with wcg + clamp.

I'll look for more undocumented fixes.

Things look a little less orange/yellow in HDR? Still have to do the six color toggle fix though.

Hey Guys, this thread has been super helpful but i have one question regarding novideo_srgb clamping: i have the icc Profile from the product page active in Windows and use the clamp in edid Mode, is this the right way to do it? Or does it Not Work with an icc Profile active?

I've had a love hate relationship with this monitor. Most of the issues are standard WOLED stuff but the very changeable grey uniformity is killing it for me.

One day it looks acceptable. Another it looks hideous with lines everywhere. Running those youtube randomised colour videos can clean it up. Running the pixel refresh does literally nothing. If anything it makes the problem worse.

My Sony TV is a WOLED and the uniformity doesn't change but I'm guessing this behaviour is normal for this monitor. Anyone got any opinions or ideas before I jump ship to another monitor?

WDeranged wrote: ↑

11 Jan 2026, 11:15

I've had a love hate relationship with this monitor. Most of the issues are standard WOLED stuff but the very changeable grey uniformity is killing it for me.

One day it looks acceptable. Another it looks hideous with lines everywhere. Running those youtube randomised colour videos can clean it up. Running the pixel refresh does literally nothing. If anything it makes the problem worse.

My Sony TV is a WOLED and the uniformity doesn't change but I'm guessing this behaviour is normal for this monitor. Anyone got any opinions or ideas before I jump ship to another monitor?

Hello. Same problem here. Frankly, I'm disappointed with this monitor. There are too many flaws: the blacks are crushed at 240Hz without using novideo_srgb+clamp, uniformity and color accuracy are bad, the color banding/posterization effects is absolutely atrocious. And it's unbelievable that we are now in 2026, and they still haven't managed to fix the VRR flicker at 240Hz. OLED Anti-flicker reduction helps a little but not totally, and it also causes a little stuttering and blacks are crushed even more. And besides, over time, vertical white lines appeared on a grey background, covering my entire screen; I don't know if it's because of pixel cleaning doing this with time… I'm thinking to change it for tandem oled monitor if it's better at the future.

Wroggus wrote: ↑

06 Jan 2026, 11:35

Hey Guys, this thread has been super helpful but i have one question regarding novideo_srgb clamping: i have the icc Profile from the product page active in Windows and use the clamp in edid Mode, is this the right way to do it? Or does it Not Work with an icc Profile active?

If you use the ICC profile, then applications that support ICC will get double-clamped (once by the ICC, once by novideo_srgb.)

There is no reason to use the ICC profile if you use nv_srgb.

What is the recommended brightness for HDR? 90 or 100? and is it better Console HDR or Gaming HDR?

Vultix wrote: ↑

15 Jan 2026, 06:51

What is the recommended brightness for HDR? 90 or 100? and is it better Console HDR or Gaming HDR?

In my experience, there's no need to enable "adjustable HDR" to begin with. If you enable that and set brightness to 100, you lose some color shades for some reason. In my tests, I could see a color gradient completely disappearing when setting it to 100. A piece of white fur around a characters shoulder for example was slightly yellowish at its edges, giving it a worn-out look. When setting brightness to 100, this detail goes away the fur was just white. The yellow shade at the edges disappeared.

As for the HDR mode, "Console" seems to map the brightness games output directly to the display. So I'd say this the best setting for games that have configurable HDR peak brightness. I suspect this is basically HGIG mode, which is recommended, but don't quote me on that.

The "Gaming" mode is better for games where you can't adjust peak brightness and they are hardcoded to something like 1500 or 2000 nits peak. For those, it's best to allow the monitor to map the output to 800 nits peak so that the ouput won't clip and preserve a bit more detail in bright areas. It doesn't help much though. It will still clip overall. Games without an HDR calibration setting usually assume a 1500 or 2000 nits TV display. The only way to fix those is modding them (if there's a RenoDX HDR mod for them,) or try and limit their peak brightness using SpecialK or ReShade.

If you want to measure what the game tries to actually output, you can use reshade's HDR analysis shader. If you see a game that tries to output over 1000 nits, then "Gaming" is better. If the game sticks to what you configured it to (should be somewhere around 750 to 830 nits,) "Console" is better.

I don't know how the Windows 11 HDR calibration app plays into this, since I'm on W10. I suspect that if the HDR app actually applies to everything (including games), then "Console" is also best for that.

As for the "Cinema" setting, no clue what that's good for. Probably good for watching HDR movies where the video player sends HDR metadata to the display. Not really sure. I wish Asus would document this stuff.

A small PSA of sorts.

Tl;dr version:
Rollback from MCM106 to MCM104 clears all oled care usage info (total hours and pixel cleans). So if you care for that, you may want to think twice before going back. Unless you really have issues like I do.

106 firmware introduced a standby bug, now the monitor doesn't properly turn off with the power button. I presume it's because of the first change in the update.
https://rog-forum.asus.com/t5/rog-serie ... -p/1133331
https://rog-forum.asus.com/t5/gaming-mo ... -p/1134631
For me it also caused bios/windows recovery screen signal loss. Before that because of msi mobo bug in their bios (something secure boot related) I was unable to see anything other than windows on reboots, only cold boot. Now the monitor just stays black until windows boots up. It even fails to wake up if I turn it on before booting the pc and it goes to standby. Only power cycling fixes that.
So I reverted to 104 and found out that I lost all usage info. I guess because of the new pixel clean feature, whatever they changed there seems to affect backwards data compatibility.

Speaking about srgb_novideo on 591 drivers, it's a shame nvidia broke their api, so I'm going to stay on 581 until it's sorted that way or another. I play all my games in hdr anyway, but have clamp enabled for desktop usage.

Shifroval wrote: ↑

16 Jan 2026, 09:08

Speaking about srgb_novideo on 591 drivers, it's a shame nvidia broke their api, so I'm going to stay on 581 until it's sorted that way or another. I play all my games in hdr anyway, but have clamp enabled for desktop usage.

Desktop usage in HDR mode? Don't use that tool for that. Windows (both 10 and 11) will clamp to sRGB color when in HDR mode.

Other than that, SDR games can be made to look correct in HDR mode by using either Reshade or SpecialK to fix the wrong gamma. This is the workaround I'm using right now (SpecialK) since SDR mode is borked without novideo_srgb. For games where SpecialK doesn't work, you need to use Reshade instead, which is more complicated to figure out.

I posted this on Guru3D, but I'll copy it here as well:

A workaround right now is to run SDR games in HDR, and fix the gamma using SpecialK using these settings:


Click the "Reset" button first to reset all processing, and select "SDR->HDR or Native" in "Tonemap Mode". This should result in plain SDR looking as intended. The "Peak White Luminance" slider in this setup acts as a general brightness slider. The most important setting here is to use "2.2" in the "Content EOTF" setting. This uses 2.2 gamma which is what the vast majority of SDR games use.

RealNC wrote: ↑

16 Jan 2026, 11:02

Desktop usage in HDR mode? Don't use that tool for that. Windows (both 10 and 11) will clamp to sRGB color when in HDR mode.

No, I use clamp only in sdr, I know that Windows correctly clamps to srgb (although piecewise), so every time I switch to hdr, I untick clamp. I'm not a member of never-turn-hdr-off camp.
Speaking about windows, do we still need to do this?
https://github.com/dylanraga/win11hdr-s ... mma2.2-icm
Now that you suggest displaying sdr inside hdr container I remembered it.

RealNC wrote: ↑

16 Jan 2026, 11:02

I posted this on Guru3D, but I'll copy it here as well

I saw your post, but thank you anyway for reiterating things, it's better that this knowledge is posted in more places than one.