@RCLandroid87 wrote:
I just ran the HDR calibration app in Windows and Test 2 and Test 3 portions are behaving as originally intended by MS. The peak saturation points now conclude around 1,000 nitts to 1,100 so whatever tone mapping was occurring prior has been tweaked correctly. I just need to test "peak" brightness from 4% to 10% and then 10% to 100%.
I'm not sure any of this was meant to be made public yet, but since you posted here and on reddit, I'm going to reply.
IDK what mode you're in while calibrating with the Windows HDR cal app, but ConsoleHDR clips at 450nits in the Max Lum test for me on the new firmware as it did before, and never capped less than that for me(I have no idea where you got 260nits from as you posted on reddit). The Max Full Frame Lum test currently clips at ~1000nits, also the same as before. If yours is clipping at 1100 you're either in a different mode, or have some sort of additional tonemapping. Both CinemaHDR and GamingHDR always clipped around 1100nits for me on the old and new firmware due to tonemapping in both test 2 and test 3. I've mentioned this in multiple posts now.
Despite the firmware notes, I don't think ConsoleHDR in its current design is supposed to clip above 450nits in the Windows Cal app given it functions as the HGIG mode tracking PQ very accurately and hardclipping at peak in a 10% Window, which is what test 2 in the Cal app is using. To be fair, it wasn't even communicated to me that it would register in the app 1000nits, just that you can set it 1000nits, where as before it was limited to 450. And that's exactly how it now functions, you can force it to 1000nits and Windows will properly reflect that. If you choose not to use the tool at all Windows will register the current EDID of 1015nits on the new firmware where as before it would be 450nits. Also, EDID now properly communicates 1015nits to apps that look to it like RTX HDR.
I already ran a series of tests, and PQ tracking for all modes remains the same at all APL on this firmware.
