Originally Posted by sniggleface
Thanks for that, very interesting!
CRU created resolutions are different from nVidia custom resolutions; they're native to the system. You should fully avoid the nVidia custom resolution section when using CRU. I'm not sure why you're losing 32-bit at 60hz as this does not happen to me with the 320.49 drivers. Regardless, if you're planning on running a higher refresh rate and that one works with 32-bit it shouldn't really matter.
Thanks for the reply. That clears up one mystery -- the CRU custom resolutions show up under PC "native" resolution. Cool.
The remaining mystery is that I have no idea why after running CRU I lose 60Hz 32-bit color as a "native" option.
I guess I'll reinstall the 320.xx drivers, repatch, and retry with CRU.
The reason I want to see both resolutions as "native" is because when I'm not gaming I switch back to 96Hz. I have 2 monitors connected and if I run the Qnix at 96 Hz all the time neither video card downclocks. If I run Qnix at 60Hz then one of my video cards downclocks like normal.
With respect to CRU, it took me a while to figure out what to do in terms of editing, copying, adding, pasting in manual etc. The OP instructions are kind of vague. I learned how to use CRU from reading the thread rather than the OP.
I figured out why I was losing native 60Hz 32-bit color in Nvidia control panel. I was using Precision X to set the pixel clock to "default" and after applying that the Nvidia control panel gets all messed up and keeps thinking that 60Hz 32-bit color is a custom profile rather than a native profile.Edited by coelacanth - 8/14/13 at 9:18pm