I'm seeing some behaviour that I don't understand particularly well, and that I have not found an answer to in the documentation either. For reference purposes, this is a Windows 11 machine with an RTX 4090 graphics card, software/firmware all updated, and the behaviour reproduces on different monitors. VCGT files are saved directly via SpaceMatch.
So, when I open SpaceMatch on a display that shouldn't have a bespoke VCGT applied to it, I see a fully linear one as VCGT_from_display_0 with no path, i.e., everything is okay.
VP2776 - program start is the example of that, with the following start and end sequences:
0 0, 0, 0 | 0.000, 0.000, 0.000
255 65535, 65535, 65535 | 1.000, 1.000, 1.000
If I get the active VCGT data via pressing "Read", I get the exact same thing, as expected. Attached for posterity as
VP2776 - read.
Where the oddness happens is when I now press the "Reset Display Tables" button. In my understanding, I should be seeing no change, i.e., a reset from a null VCGT to a null VCGT. Instead, I see that the full range of the VCGT changes, shrinking by one "step". Attached as
VP2776 - reset.
Before reset:
250 64250, 64250, 64250 | 0.980, 0.980, 0.980
251 64507, 64507, 64507 | 0.984, 0.984, 0.984
252 64764, 64764, 64764 | 0.988, 0.988, 0.988
253 65021, 65021, 65021 | 0.992, 0.992, 0.992
254 65278, 65278, 65278 | 0.996, 0.996, 0.996
255 65535, 65535, 65535 | 1.000, 1.000, 1.000
After reset:
250 64000, 64000, 64000 | 0.977, 0.977, 0.977
251 64256, 64256, 64256 | 0.980, 0.980, 0.980
252 64512, 64512, 64512 | 0.984, 0.984, 0.984
253 64768, 64768, 64768 | 0.988, 0.988, 0.988
254 65024, 65024, 65024 | 0.992, 0.992, 0.992
255 65280, 65280, 65280 | 0.996, 0.996, 0.996
I would like to understand if this is the expected behaviour and I have misunderstood something along the way, or if there's something to be done about the behaviour.
