Open Rafaelldestilo opened 1 month ago
The profile name doesn't specify HDR nits, it specifies the "SDR white" nits and its equivalent SDR content brightness value (can be found under HDR settings in Windows 11). So, for the "300 nits / Brightness 55" profile, you have to set your Windows SDR content brightness slider to 55, anything else will be inaccurate.
SDR white does not affect the peak brightness of HDR content, so you can set it to 100 nits if you want and your monitor would still display the full 300 nits in HDR content and Auto HDR.
For your monitor, I'd recommend using the "unspecified" profile, since the other profiles have a hard-coded HDR peak nits value of 800, which is way higher than what your monitor can display and might cause issues with Auto HDR and some other content. The unspecified profile needs an SDR white of 200 nits, though, so set your SDR content brightness to 30 if you use this profile.
I really don't know if I should use HDR on my monitor or not with HDR the image is generally clearer but loses saturation, in SDR I can change the saturation and compensate for the stabilizing black to lighten the black parts a little, the biggest difference even with HDR activated is that I can add the white a little more burst to simulate an HDR light In the Windows HDR adjustment bar, the best value is between 55 and 60, using profile 300 or undefined, undefined was better because the blacks are not so dark and remain at 2.2 but a little brighter, but not undefined If I put it at 30, the white becomes a bit opaque, along with the colors, both the 300 and undefined profiles, 55 to 60 look better In the Windows HDR calibrator, black, white and contrast are good at 290-300, this is the value that looks good in the calibration No, if my HDR is weak, I have to leave the white a bit blown out to see a real difference between SDR and HDR.
Could I be doing something wrong?
I did several tests here, in DX 11 or 12 games where Auto HDR works at its best using profile 300, even at 55 set, the whites are all blown out, as you said, it was set to 800nits In DX9 games it didn't pop, but using the undefined profile it worked correctly for me in DX11 and 12 games, it didn't pop, staying like my profile that I calibrated in the W11's HDR app but with the gamma correction, and DX9 games were good too
but the undefined was good at a value of 50 to 55 on Windows, if I set it to 30, DX9 or 11 games have low overall brightness, and at 55 it was good, even comparing with RTX HDR without a color profile, and the auto HDR with the 2.2 fix were practically identical in quality in DX11 and 12 games, but in DX9 games, RTX HDR still gains a little in brightness quality, but Auto HDR does not work in DX9 games, so using a more superficial HDR in these games
So I'm going to continue using the undefined profile configured in Windows for 55, that's where the best scenario was for me
my monitor is an LG UltraGear 34GP63A-B with only 300Nits with HDR, although it only has 300 nits in HDR mode I feel better color accuracy, but when using auto HDR I always noticed the image with less saturation and grayish blacks, and through your profile the blacks were excellent, many better than the standard HDR, even calibrating the HDR in windows the blacks were bad, and in this profile it was excellent, but my doubt about the profile is that I downloaded "300 nits / Brightness 55" Is it already configured for 300Nits monitors? I have an RTX 3060Ti and I don't use RTX HDR because using Lossless scaling where I use the frame generator, it doesn't work with RTX HDR, but it works perfectly with Auto HDR on Windows 11