PG32UCDM Console Mode HDR issue

[FallenDeity]

My and other's PG32UCDM monitors have a clipping issue on PC when using the console HDR mode in Windows 11. Currently, the monitor clips at 450 nits in the Maximum Luminance window but it clips correctly in the Max Full Frame Luminance window. Is there a firmware update in the works for this or is this an RMA issue?

[Arhat1984]

Sorry if I'm being a imbecile but if ConsoleHDR is as bright as TrueBlack 400 on beta FW but suffers the same caveat (clipping), what exactly is the advantage of using it over TrueBlack 400? 

[BiscuitJar]

TrueBlack 400 mode is limited to 480 nits regarless of what is on screen. So even if you have a nighttime scene where ABL doesn't force brightness down it still won't go above 480 nits.

That is kind of a problem because the panel can go higher than that for smaller than 10% APL window sizes.

The new Console HDR mode is as bright as TrueBlack 400 mode overall, but when the panel is able to, it can go up to 1000 nits. So basically when ABL isn't forcing the brightness down because of too high APL for the panel to handle it can reach 1000 nits, but it doesn't artificially bring down brightness in other scenes like old firmware did.

[Arhat1984]

Got it, thank you for the explanation. I heard that LG Oled Tvs have a service menu that can disable ABL and other restrictive measures at the cost of voiding the warranty.

Is there any similar feature on this monitor? Because I'm willing to void my warranty for better HDR picture.   

[Kundica]

You cannot disable ABL on LG OLEDs, you can disable ASBL. ABL is a core part of how OLEDs function. You can read more about the difference in this post from TFTC. 

That said, you cannot disable ASBL on the PG32. I've accessed the service menu and there is very little you can do there. I was hoping it would allow me to change the white balance preset values since my panel measures around 6200k with the 6500k preset and in HDR. While I can see them, it doesn't allow me to change them.

[Paul13]

The MCM104 can’t boost over 450nits in high APL picture, the brightness will similar as TB400 mode. But this version boost the brightness to meet the panel limitation in normal APL. So the brightness will be increased. The brightness of MCM104 with small APL picture will brighter than TB400, because the TB400 limited the brightness can’t over 450nits even low APL.

[silverbolt81]

@Rogex47 If you open the HDR settings in Cyberpunk2077 does the image with the sky seems overblown to you when you set the brightness above 400 nits?

[Rogex47]

Are you talking about Peak Brightness or Paperwhite Brightness?
If I set "paperwhite" to 250 ConsoleHDR looks slightly overblown imo, worse than GamingHDR.
At paperwhite = 100 ConsoleHDR looks good to me.
Other settings are:
Peak Brightness: 1.000
Tone Mapping: 2
Colorsaturation: 0.7

[silverbolt81]

The peak brightness yes,even on the current 103 firmware if i switch to Gaming HDR and set the peak brightness over 420 nits the sky is blown out.

Does it happen with the beta firmware under Console HDR?

The paper white setting is just for ui elements,are you sure it is not placebo what you think you are seeing?

[Rogex47]

I don't see a problem setting preak brightness higher to 1.000nits may be even higher.
This is what it looks like in Gaming HDR for me:

I also tried to zoom in on the sky, but the photo is looking horrible. Irl at these settings I can see all the clouds and even colourbanding, but it is definitely not blown out. When changing my settings I mostly look at the rabbit graffiti on the left whether it loses details or not.

And this shots were taken while in Console HDR with FW104.
For the 2nd and 3rd pic I was holding the phone very close to the monitor, but again irl I dont find sky being overblown and I do see details like clouds.

[ProKable]

I just tested the update, and it's really terrible on my side. It is indeed brighter, but the highlights are completely blown out, including in HDR gaming, even though there hasn't been any modification to this mode yet, if I'm not mistaken?