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?

[wraith321]

Well... I have a whole different problem now.
Firmware update failed for me at 30-40% and now the updater says "Get Model Name Fail".
I really hope I didn't brick my display... It's still working fine though and is correctly detected in Windows.

@Silent_Scone 

[BiscuitJar]

For me HDR calibration app still clips at 400 for "Console HDR" mode. Gaming and Cinema HDR reach 1000 nits now.

However, there have been no changes to the "too dim HDR" ABL behavior from what I can tell. (Not that it was expected to be fixed this quickly anyway). It seems to behave exactly the same way as before, so personally I'm still stuck at using True Black 400 mode.

But at least KVM auto switching works. Not sure about RTX HDR maximum brightness setting because I don't want to disconnect my second monitor just to try it now.

[DonDOOM]

As I've posted all over reddit, trying to post it here as well to get as much attention to this glaring issue that should never have been allowed to pass internal testing / QC checks... :

Sadly there are significant HDR issues currently.

Console' mode (which should be called HDR 1000 mode) is way too dim in for fullscreen brightness. Weirdly enough peak brightness is working as it should for 1-3% and 10% window sizes.

Test this out yourself easily by using an HDR capable browser, looking up 'winter fox hdr' on youtube and switching between the True Black 400 and Console mode. - True Black 400 mode is capped at ~455 nits, so whilst better in overall brightness, also not a good solution.

Even comparing it to normal SDR should show you the difference.

HDR is effectively not worth using until a firmware update fixes it.

This needs to be fixed ASAP ASUS!

[Silent_Scone]

Please stay on topic and post any additional information that you deem might be useful. The thread has been moved to ROG Care so service can deal with it accordingly, it's in the proper channels. Posting the same thing repeatably and expecting a next to immediate resolution doesn't really help anyone. You're not being ignored 👍

Thanks

[BiscuitJar]

The problem can be easily verified by using this HDR test video:

1. Open the video in fullscreen on browser that supports HDR (For example Chrome / Edge)
2. At various test patterns toggle between different HDR modes from the OSD
3. First test pattern 1% window size:
   1. The first brightness level (100 nits) looks identical on all modes -> ✔️Works correctly
   2. The second brigthness level and 3rd (400 nits, 1000 nits) both look brighter on "Console HDR" than on "DisplayHDR 400" mode -> ✔️ Works correctly
4. Now go to the higher window sizes, for example the 49% that starts at 2:04 mark. This is where things go wrong:
   
   1. First brightness level (100 nits) looks slightly brighter in "DisplayHDR 400" mode?? -> ❌ Incorrect. Why wouldnt "Console HDR" be able to display 100 nits??
   2. Second brigthness level (400 nits) looks massively brighter in "DisplayHDR 400" mode??? -> ❌ Incorrect. "Console HDR" is almost half dimmer here, which makes no sense
   3. Third brigthness level (1000 nits). This also looks almost double as bright in "DisplayHDR 400" mode -> ❌ Incorrect. Sure, with large window size the ABL should kick in and drop the brigthness to around 270-330 nits that the monitor allows sustained 50% window, but "Console HDR" and "DisplayHDR 400" should both be equally bright here

[MrEWhite]

Quick question for you, I notice in a few other posts here people say they can put "Maximum Luminance" in the Windows HDR Calibration tool to 450 nits in Console HDR, but yours seems to be like mine, where it can only be put up to 400 nits in Maximum Luminance and 1000 nits Max FFL, is that correct? Just trying to confirm that it's not a me thing.

[Richu6]

The thing is... some games, that allows to set max peak brightness to 1000, are looking fine to me.

For example "ratchet and clank" or "Horizon zero dawn" HDR seems fine to me, no clipping.

But all apps that are not allowing a manual peak brightness are looking to dim in console mode.

[PiPoLiNiO]

Unfortunately not. Forza Motorsport, for example. You normally set peak to 1000, and even when you change from console mode to true black, it is much brighter in the second mode.

[DonDOOM]

As @PiPoLiNiO stated, even in games where you can set the peak brightness, or games that use Windows' HDR / advanced ICC profile, full screen bright scenes are still too dim compared to what they should be, and can be easily tested by switching between HDR True Black 400 and the other HDR modes.

[Richu6]

Yep its true, that "true black 400" is moore bright.

But i think if you set the Monitors peak brightness to 1000 in a game, than "true black 400" mode is "too bright" overall!! 

Because you have to compare "peak brightness 400" mode when you set the max peak brightness in game to 400.

And compare that with "console" mode when you set peak brightness in game to 1000...

And then it looks kinda the same for me! Except the highlits, which are moore vibrant in "Console" mode!

If you just switch the "modes" on the monitor without changing the ingame peak brightness it is clear, that "true blsck 400" is brighter... because if the slider in game is set too 1000... everything in true black 400 us too bright!. And the highlits are cut off!