Quote:
Originally Posted by iSeries
There doesn't seem to be a reliable way to switch bit depth inside the control panel either lol, always reverts back to 8 bit after a reboot or waking up from sleep, or at least it does for me...bloody Nvidia!
I did manage to create a custom res with CRU by putting in the info from MadVR (custom res listed under 'PC' in the Nvidia control panel), and I can switch between 8 bit and 12 bit no problem (apart from the 12 bit setting not surviving a reboot), but for some reason I can't get MadVR to use it, so if anyone knows a workaround for that, please let me know :-)
|
If set to 12bits at 30p or less before selecting the custom res, the driver displays 8bits when the custom res is applied, but it actually outputs 12bits (at 30p or less). I checked this with a Vertex.
Quote:
Originally Posted by ryrynz
The way that works for me with 385.28 is to set it to 12 while watching a video when madVR has changed the refresh rate, it sticks then.. I'm not using any custom madVR created custom res modes.
I might give the new drivers a shot, but the problems with all versions after 385.28 have always left me wondering why I even bothered.
|
The main motivation for me to leave 385.28 behind was the better 3D. 13mn between frame drops vs 3mn between frame drops is significant.
If you're not a gamer and don't need 3D, 385.28 is the best version to use IMHO, especially if you need Asio4All with Win 10 build 1803.