cancel
Showing results for 
Search instead for 
Did you mean: 

PG32UCDM Console Mode HDR issue

FallenDeity
Level 8

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?

93,896 Views
678 REPLIES 678

So, since Console mode is using HGIG, should I leave the 10 percent window in the windows calibration 100 at 450-460 and the max full luminance at 1000? I've owned a bunch of other hdr monitors and some included HGIG and none of them had two different values for the max luminance and max full frame. 

Yeah, pretty sure the Win Calibration tool capping at 420 nits on the max luminance test (2nd test) is bugged.

If you want to use ConsoleHDR mode and the tool then I'd set both to 1000nits. Just know that ConsoleHDR mode doesn't track PQ well past 300ish nits to reach 1000. It'll still do 1000nits, just not tracking PQ. It's probably not a huge issue since we're talking about specular highlights in games, but it's worth mentioning. I'll add this info to my initial reply. 

Personally, I only use HDR in HDR supported games and don't use AutoHDR, so I just ignore the Windows HDR Calibration app since peak brightness can be set in most games I've come across. If you use AutoHDR, games that don't allow for peak brightness adjustment, or the saturation adjustment feature of the Windows tool, then just set it to 1000nits on both screens in ConsoleHDR mode.

This info is only for gaming. If you watch HDR content on the monitor I would use one of the tonemapped modes, probably CinemaHDR since it should be the only mode that properly adapts its tone curve to maximum display luminance metadata 4000nits. I need to measure this to confirm, but it's how it works on some other Asus OLEDs.

That reminds me. During one of my conversations with Asus, they mentioned that Brightness should be default 90, which is the case for their new ultrawide WOLED, but as we all know the default for this monitor is 100. I never bothered to measure at 90, perhaps it will result in a 2% Window in ConsoleHDR mode tracking PQ correctly. I have noticed that HDR movies in ConsoleHDR mode sometimes have posterization on skin, which is also the case with the new ultrawide when set to 100. I'll measure later today and update this thread if it shows any differences worth mentioning.

EDIT: I tested adjusting brightness and it doesn't have any impact on ConsoleHDR PQ tracking, just lowers output brightness. I also tested GamingHDR and CinemaHDR to check out they adapt their tone curves for movie content. CinemaHDR is the only mode that properly adapts its tone curve to maxMDL 4000nits.

MrEWhite
Level 10

Quick question for everyone here, when set to Console HDR, where does your brightness clip in the Maximum Luminance test in the Windows HDR Calibration tool? Mine clips right at 400 nits, so I find it odd it's clipping a bit later for others.

DonDOOM
Level 10

Thanks @ApolloEleven for pointing Monitors Unboxed video out.

I rewatched their PG32UCDM review video, and funnily enough he does point out that the brightness is surprisingly low for one of his tests, but then sadly doesn't go on to investigate further.

https://youtu.be/qywLwR7KT9M?t=1575

@Aureliannn_ROG This is the issue we're talking about.

Support us on Patreon: https://www.patreon.com/hardwareunboxed Join us on Floatplane: https://www.floatplane.com/channel/HardwareUnboxed Buy relevant products from Amazon, Newegg and others below: Asus ROG Swift OLED PG32UCDM - https://geni.us/wN9RQ Asus ROG Swift OLED PG32UCDM (Asus link) - ...

MetalHarl
Level 7

Its really a bug or its designed that way?

In Asus spes page It doesen say anything about 1000cd/m2...

Brightness (Max) : 450cd/㎡
Brightness (100% APL) :250cd/㎡

Read all the other posts, it's not about the specs or max brightness but CLIPPING. 

packene
Level 9

Not sure why people are debating whether this is intentional or a bug. Other displays using this panel are functioning as expected. This seems like it should be a simple software fix, and hopefully Asus is working on just that.

In the meantime it would probably be cool if people stop cluttering the thread with off-topic and incorrect speculation.

 

Honestly it's more weird that reviewers didn't catch this. We need to spread the word to reviewers.

@Aureliannn_ROG Will you finally write us back or will you continue to pretend that there is no problem? 

Today, I will send information with a description of the problem to all YT reviewers.  Maybe they will publicize the issue if they were not paid and then suddenly Asus will do something 

14900KS :: RTX 4090 :: Aorus Master X Z790 :: 64 GB RAM