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?

710 Views
678 REPLIES 678

Please let us know!

So, forewarning, I don't have measurements but I did test Horizon and Destiny. No clipping with either with the settings mentioned in my last comment so I'm happy. ABL didn't seem distracting or extremely noticeable (but each person is different when it comes to that). All in all, I'm good with this update. HDR is extremely comparable to my OLED G8 ultrawide which I tested side by side and that monitor has a service menu tweak that I did to get HGIG 1000 nits. I haven't commented much after starting the thread since more knowledgeable people started chiming in but I think I can end my watch over the topic now lol. Still curious to see how the dynamic brightness handles since I did see someone mention that clipping is still occurring with that mode on. It may just be a compromise for the panel tech at the moment. 

Can you send screenshots/pics of your setting ups

Had to head out for work but I can when I get back later. Also, I can confirm that dynamic brightness does cause clipping. There's a warning now that turning the mode on will cause the PQ curve to change.

Can you please answer my question before you disappear for 10 hours lol.

Did you do your side by side comparison with the boost disabled or enabled?

I'm confused, are you insinuating that they lowered the aggressiveness of abl even with the brightness boost turned off?

Honestly i dont see it the aggressivnes is imo the same as fw103 if turned off and if turned on we go to fw104. Just by eye I can see,brightness is way lower when turned off

This is because ConsoleHDR(without Dynamic Mode enabled) no longer functions as HGIG as it previously did, and now tonemaps to max peak brightness. The upside is that it now tracks well in both 10% and 2% window sizes instead of the odd tracking it exhibited before with APL smaller than 10%, the downside is that it's not longer HGIG.

With Dynamic Mode enabled, ConsoleHDR behaves much like before with odd overtracking in smaller window sizes, but hard clipping in a 10% window, which is why it clips at 450ish nits and completely expected behavior. The caveat to the tracking is that it has the odd boost in middle grey, which is how they're making the the mode brighter in higher APL content.

FW105 - ConsoleHDR - 10%
FW105 - ConsoleHDR - 10%FW105 - ConsoleHDR - 10%

FW105 - ConsoleHDR - 2%
FW105 - ConsoleHDR - 2%FW105 - ConsoleHDR - 2%

FW105 - ConsoleHDR (Dynamic) - 10%
FW105 - ConsoleHDR  (Dynamic) - 10%FW105 - ConsoleHDR (Dynamic) - 10%

FW105 - ConsoleHDR (Dynamic) - 2%
FW105 - ConsoleHDR (Dynamic) - 2%FW105 - ConsoleHDR (Dynamic) - 2%

 

So are you saying they added brightness boost but it being turned off is still better and an improvement from the last firmware because of this change?

It's a bit of a mixed bag. One of the things that made ConsoleHDR unique in previous firmware was its function as HGIG, so hardclipping rather than tonemapping. The downside to the old ConsoleHDR was that it didn't track PQ well at all small APL where it could hit the 1k+ nits(it's not entirely clear to me how that impacted real world use since we're typically not watching static APL images, but on paper it didn't look good). Now it tracks smaller APL and 10% APL well, but there's rolloff(tonemapping). GamingHDR and CinemaHDR already tonemap so now all 3 modes do.

Personally, I don't see this a big issue and welcome better PQ tracking over HGIG. People should be aware that when calibrating a tonemapped picture mode with a console or doing in game calibration it's probably best practice to calibrate to the monitor's stats on paper, not what the calibration window is showing. So ~1030nits of ConsoleHDR without dynamic mode enabled.

It's worth mentioning that Dynamic mode still allows the monitor to reach over 1k nits in 2% APL scenarios, but you'll probably see it clipping around 450 in most calibration situations because they typically use 10% and the dynamic mode tracks with a hard clip at that APL.