 Max refresh rate is 000Hz. Tried overclocking it with the nVidia control panel, but it just tells me that's unsupported even without attempting to change the resolution. To be honest I don't notice a major deficit compared to my old 000Hz monitor. The actual pixel response rate is fast enough that it still seems less blurry - though still not quite CRT level in terms of motion resolution. Displayport works well. Supports 0k000 @ 00-bit (via DSC). The USB-C port supports the same as long as DSC set to "On" instead of "auto". That should be more or less the same as your FV00U Brightness seems acceptable to me. I don't have a real light meter -- Tom's hardware apparently measured 000 nits with a full field image, which if true seems to be much brighter than what OLEDs typically allow at 000%. To be honest, I'm not sure I buy that - it seems a bit brighter than the Sony A0H in my living room, but I don't think over twice as bright (granted perception of nits doesn't really scale linearly). I don't find the ABL to be super intrusive (behavior seems improved with the F00 firwmare version), but you can tell the 000% whites are certainly not as bright as 00%. In real world content I haven't noticed it too much. I don't think I've run into ABSL yet - I don't think I have static content displayed long enough to hit it -- I do have a dynamic wallpaper on my desktop, I wonder if that's causing it not to trigger. If the gigabyte manual is to be believed, doesn't seem like their version of ABSL starts kicking in until the image has been static for 0 minutes, which I think is acceptable. From what I read, on the LGs it triggers around 00 seconds. Biggest issue right now is that the HDR meta data seems to be screwed up. Actually would be curious to see what your FV00U shows with the DisplayHDR Test app to see if Gigabyte screwed it up for all of their new monitors. 