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?

95,167 Views
678 REPLIES 678

These two modes, with "Dynamic Brightness Increase" ON or OFF ?

Doesn't matter. All modes except True Black 400 should be calibrated with about 1000 nits peak brightness. True Black 400 should be with 480 nits.

Full frame brightness is same for all modes, so about 260 nits as that is about what the panel ABL limit is for full window size APL.

So I understand that it is not possible to improve the current situation even with future firmware upgrades ?, but that it is just the panel that beyond that cannot go ?

Sure they could add all kinds of tweaks. If intention is to reduce clipping they could dynamically adjust the curve rolloff only for situations where clipping happens, or reduce brightness in such cases. Although I'm not sure if 240hz 4k monitors have powerful enough image processors to have that much dynamic control.

All in all I think with latest firmware this is no doubt one of if not the best PC monitor HDR experiences you can get these days with lots of options to use it for every preference. Not sure how much more improvement is needed when it already is this good? (Other than waiting for 2025 or 2026 OLEDs that will have even better panels that is.)

Thanks for this. Just to be clear, the values to input for the windows HDR app; 0 - 1000 - 260… correct?

Why 260? I did 0,1060,1060.

No, First 0, After 1000, After 260.

But why 260? Can you explain please? The instructions say to move the slider with the same principles as previous step

Intel i7-13700K / Kingston DDR5 32GB 6000Mhz / ASUS TUF Z790 / PALIT RTX 4090

I am not an expert, according to @BiscuitJar, in the Full Frame screen, whether you enter 260 or 1060 does not change, this is because the panel, beyond 260 does not go.

This causes the HDR colors to be "wrong" when you do the Calibration in the Full Frame at 1060nits.

I understood it that way, but again, I don't know so much about it, I rely on those who seem to know more.

Surely @BiscuitJar can answer you better.

To be honest I'm not sure where the Windows Calibration app full frame brightness value is actually used, it might not affect anything directly at all. Maybe some games use it as reference for "paper white" value?

Yet, what is clear is that the "correct" value for that part is 260 nits. You can look up any PG32UCDM reviews to find that full frame (100% APL window) brightness for this monitor/panel is only 260 nits. Therefore if you want to set the value correctly (just to be safe in case it is actually used somewhere) you should set it to about 260.