Quote:
Originally Posted by madshi
Generally, in this situation it *seems* that the Nvidia custom mode control panel works, but it doesn't, really. Try rebooting your OS and the custom mode you created through the Nvidia control panel should be gone (it is on my PC). The Nvidia control panel doesn't report failure of the Nvidia custom mode APIs, while madVR does. That's why it seems to work in the Nvidia control panel (but doesn't survive a reboot, or a GPU reset), while madVR properly detects the failure and reports it.
|
ok, but the nvidia control panel custom modes do work, at least somewhat...
just did some testing, created a custom mode in nvidia, 2160p24, only changed 24.000 Hz to 23.976Hz, left everything else. (So I basically only changed the pixel clock from 297.00mhz to 296.70mhz if I understand nvidias panel)
So I tested standard modes 23 and 24 and my custom 24 mode by just running a 23.976fps video for about 10 minutes each time
in FSE, every mode stabilized at the same Hz:
23.97894 Hz
1 frame repeat every 4.41 minutes
in windowed or fullscreen windowed, I had different Hz every time:
standard 23:
23.97894 Hz
1 frame repeat every 4.41 minutes
standard 24:
23.99914 Hz
1 frame repeat every 41.71 seconds
Custom 24:
23.97489 Hz
1 frame drop every 1.07 hours
So the new custom mode does "something" different than the standard modes.
Interesting thing to note is that according to the madVR custom modes tab, my custom 24 mode is not active, the 23Hz one is. This might be, because my custom 24 mode seems to have the exact same timing parameters as the standard 23 mode, even though I get different results in playback.
I don't know if this is new information, or if this was obvious to you from the start, but there it is...
Since I'm using windows 10, I should be getting 10bit in windowed fullscreen, correct?
If so, 1 frame drop every 1.07 hours is good enough for me and I'm done for now.
Though if bugs get fixed in the future, I'm happy to do more testing.
On an unrelated note:
the "display bitdepth - toggle" shortcut only goes through 9bit and 10bit the first go round... So if I have a 10bit display and use the shortcut, it'll go from 10 bit to 9, 8, 7, 6, then back to 8, 7, 6, 8, 7, 6 etc. Shouldn't it go back up to 10 bit?