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?

[Richu6]

Dear aureliannn

Thx for your response.

First off... the "Main Issue" seems to be the wrong peak brightness value of about 455nits in the "EDID" of the Monitor.

Because in every game and so on, where its possible to set the max peak brightness manualy to about 1000nits, the Console mode looks fine to me!

But because of the "wrong" EDID" value some games or features, dont let us set the peak brightness to 1000. 

For example "Nvidia RTX HDR"... does take the EDID Value as maximum.

So we can only set it to max 455nits... and this is too low.

Than looks everything too dim!

But yea i use "Console-Mode" most of the time.

And in windows calibration tool the peak brightness in test 2 (the Window) i get about 450nits peak... but weirdly in test 3 (the 100%full field) it peaks at about 1000nits. 

My Hardware

I9 13900k 

ROG strix 4090

Windows 11 (newest build)

Monitor is on Displayport

[PiPoLiNiO]

Seriously? The first posts about incorrect HDR are 3 weeks old. And now you're asking what's going on? You are making total idiots out of your customers.

You have instructions everywhere on how to check. Just watch any movie in 4k hdr on YT with bright scenes ("WINTER 4K HDR"). You turn it on in Console Mode, take it to full screen and switch to True Black, which will be at least 2 times brighter.

So stop freaking out about some serial numbers as if it applies to several monitors, BECAUSE THE PROBLEM APPLIES TO ALL OF THEM. I see that it is best to return the monitor to the store and buy MSI again, because we won't get this firmware sooner than in a month or five.

My Hardware

I9 14900k 

Gainward 4090

Windows 11 (newest build)

Monitor is test on Displayport and HDMI 

[Silent_Scone]

---

@PiPoLiNiO wrote:

So stop freaking out about some serial numbers as if it applies to several monitors, BECAUSE THE PROBLEM APPLIES TO ALL OF THEM. I see that it is best to return the monitor to the store and buy MSI again, because we won't get this firmware sooner than in a month or five.

---

Hi @PiPoLiNiO 

It's called due diligence. Something you should consider before responding again, considering you've already made claims of posts being deleted that are still online. Please respond respectfully to staff and with the information requested, or let them respond to people wanting a resolution who can.

[PiPoLiNiO]

Sorry, buddy, but I spent 1,600 euros and I can't use the monitor normally. Neither me nor other people. If after 3 weeks the company starts wondering what's wrong, then for me it's a cabaret and that's it. It would be enough for them to take a random piece of this monitor model from the company and do what I wrote and they would know everything. Something that should take them 30 minutes will now take them days, weeks or months. You are a moderator so you will defend Asus, but I think everyone will agree with me that this is a clear mockery of customers.

That's it from my side. On Monday, I will report to the store that I want to return the monitor. I hope everyone else will do exactly the same and not get ripped off by products that don't work.

[Silent_Scone]

It sounds like you'd already made your mind up before posting, so I can only reiterate the above. Let others respond and don't waste their time as well as your own.

[PiPoLiNiO]

No, I've had the monitor for 10 days and I've been writing about it for 10 days. I hoped that Asus would quickly fix such an obvious error and I would be able to leave the monitor. As you can see, I was wrong 🙂

[Richu6]

@PiPoLiNiO 

Calm down and relax!...

I have the same issue like you. (And maybe some moore, because i have also weird scan lines in low frequencys, and dark areas).

But the monitor is far away from unusable.

Asus needs some time to fix the issues.

2 weeks are nothing! 

Just sit back, relax, and enjoy the nice picture Quality of the Pg32 UCDM in 95% of the time!

[FallenDeity]

Hi,

Yes, I am currently using Console HDR mode.

Auto brightness is not enabled. 

Using auto brightness does not fix the issue.

Display HDR 400 has the current highest visible brightness.

On the windows calibration app, maximum brightness reaches 450 in Console HDR and Full Max luminance reaches 1000 nits

Display port cable (tried with hdmi as well)

Firmware is MCM101

Asus Tuff 4090

Windows 11. 

Than you for looking into this!

[BiscuitJar]

• Yes, issue is in Console HDR mode. All modes except HDR 400 are too dim for large window size brightness (as seen in my other post here)
• I have tried with Adjustable Brightness on / off and tried resetting settings from OSD. No difference
• HDR 400 is significantly brighter in any larger window size brigthness HDR content
• Firmware version is MCM101. Using the included displayport cable, 4k 240hz. Graphics card is RTX 4080.

[DonDOOM]

@Aureliannn_ROG

Have you enabled the Brightness Adjustable feature? If adjusting the screen brightness from there resolves the issue?

Doesn't matter, enabling it only makes it possible to dim the screen even further, it's on 100 by default and can't make the screen any brighter. I have it disabled, as it is by default.

In HDR mode, which mode currently has the brightest setting (Gaming HDR/ Cinema HDR/Console HDR/ Display HDR 400)?

True Black 400 mode is the brightest for fullscreen brightness, but is capped at around 400 - 455 nits - so no peak highlights (which is working as intended I believe).

Console HDR mode (Should change it to be named HDR 1000 for clarity) is very dim full screen brightness. Weirdly enough peak brightness is working as it should for 1-3% and 10% size highlights.

All other HDR modes behave the same as Console HDR mode - way too dark for full screen bright scenes. They behave the same as Console HDR mode regarding brightness.

When testing the maximum brightness value, does Console HDR reach 450 nits?

As stated above, Console HDR peak brightness works as it should for 1-3% and 10% size highlights, reaching as high as 1000 nits for peak 1-3% size highlights. The issue is for fullscreen brightness, in which scenario the overall brightness is way too dim.

Besides this, it would be great to have a mode with proper full screen brightness, which also raises 10% window brightness to ~600 - 700 nits and 1-3% window peak highlights to 1100 - 1200 nits. This panel should be easily capable of this without burn-in issues.

Can you provide a screenshot of the brightness test results for our reference?

I'm having difficulty capturing HDR screenshots for some reason. Instead you can easily test this out yourself by using an HDR capable browser, looking up 'winter fox hdr' on youtube and switching between the True Black 400 and Console mode.

Or use @BiscuitJar 's method that he wrote up in a comment above for example.

At the same time, please provide the current signal cable/firmware version/graphics card model/PC model

Cables used: DP 1.4 Cable provided with the PG32UCDM.

Firmware version: MCM101

GPU: 4090

Other PC hardware: 13900K, 32GB DDR5 @7600MT, Z790 ROG Maximus Hero