NVIDIA Pixel Clock Patcher
|
05-14-2013, 05:25 AM
Post: #71
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
I think the patcher needs to be updated again for 320.14. It's not finding the SL limit on DL-DVI.
|
|||
05-14-2013, 07:50 AM
Post: #72
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
I will update it soon, but that limit is not needed for the Catleap monitors.
|
|||
05-16-2013, 04:22 AM
Post: #73
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher | |||
05-17-2013, 07:22 PM
Post: #74
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
The Tempest is the same as the Catleap. I've updated the patcher.
|
|||
05-24-2013, 07:13 AM
Post: #75
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
Big thanks for your work!
In my Samsung S24A850DW i increase refresh rate to 75 (76 max) without any problems! GeForce8800 GTS Windows7 x64 320.18 Using NVIDIA Control Panel |
|||
05-24-2013, 09:58 AM
Post: #76
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
Hello there. Thanks for the patcher, very nice work. I have one question, if you don't mind:
I have a qnix qx2710 and two 670s in sli, with windows 64 bits. Did the patch with the full exercise, entered test mode and created custom resolutions in CRU, at 96hz and 120hz, and it works, mouse and Window movement gets much soother. However, in games fraps never passes 60 frames per second. Tried metro last light, bioshock infinite and dirt 3. Dirt 3 even allows me to chose 96hz refresh rate but still doesn't pass the 60fps mark. Am I doing something wrong? Thanks for the help. Cheers :-) |
|||
05-25-2013, 07:34 PM
(Last edited: 05-25-2013, 07:43 PM by Pretzil)
Post: #77
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
I just received my QNIX QX2710 and am able to overclock it using Nvidia CP to 135Hz with only a few scan lines. Currently running at 125Hz w/ no scan lines.
I did not originally have the patch installed and I was using 314 drivers. At 135Hz the screen looked like crap and I was only able to get it up to 115Hz w/o having any scan lines. I installed the patch and enabled test mode, restarted and tried the higher refresh rates again, same as without the patch installed. I've since installed 320.18 drivers and have not installed the patch again, I disable test mode as well. I am running SLI with 2xEVGA GTX670 FTW on Win 7 64bit. I am now able to reach 135Hz w/ only a few scan lines, fairly visible, and 125hz w/o any scan lines. I have not attempted to go above 135Hz yet. My Pixel Clocks are: 135Hz: 532.44 - Manual Timings 130Hz: 512.72 - Manual Timings 125Hz: 493.00 - Manual Timings 120Hz: 473.28 - Manual Timings 115Hz: 453.56 - Manual Timings 110Hz: 443.11 - Automatic Timings 105Hz: 422.97 - Automatic Timings 100Hz: 402.85 - Automatic Timings For my manual timings I just changed the horizontal to 1450. This seems odd to me because the patch information says that if you are running SLI you need the patch for Pixel Clocks greater than 400Mhz. |
|||
05-27-2013, 08:53 PM
(Last edited: 05-27-2013, 08:55 PM by TarAldarion)
Post: #78
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher | |||
05-28-2013, 05:22 PM
Post: #79
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
(05-27-2013 08:53 PM)TarAldarion Wrote:Did you use the full patch? Some 500-series cards need the full patch. If test mode wasn't working, the patched driver wouldn't load at all, and you wouldn't be able to load the NVIDIA control panel or set refresh rates.(05-09-2013 11:22 PM)ToastyX Wrote: What video card? It doesn't sound like a problem with test mode. (05-25-2013 07:34 PM)Pretzil Wrote: This seems odd to me because the patch information says that if you are running SLI you need the patch for Pixel Clocks greater than 400Mhz.Are you sure you have SLI enabled? Without the patch, people were getting pauses every few seconds with SLI when the pixel clock was greater than 400 MHz, basically making it unusable. The patch won't get rid of the flickering scanlines. That's a signal quality problem. Either the monitor or cable can't handle it. (05-24-2013 09:58 AM)Badelhas Wrote: I have a qnix qx2710 and two 670s in sli, with windows 64 bits. Did the patch with the full exercise, entered test mode and created custom resolutions in CRU, at 96hz and 120hz, and it works, mouse and Window movement gets much soother. However, in games fraps never passes 60 frames per second. Tried metro last light, bioshock infinite and dirt 3. Dirt 3 even allows me to chose 96hz refresh rate but still doesn't pass the 60fps mark.Some games have frame rate caps, but I know for sure that Dirt 3 doesn't. There's no reason for it to be locked to 60 FPS when the refresh rate is 96 Hz. Are you sure you don't have a frame rate cap set somewhere? Do you happen to have a 60 Hz monitor connected? I've heard some people having issues when having different monitors connected at the same time. |
|||
05-28-2013, 05:33 PM
Post: #80
|
|||
|
|||
RE: NVIDIA Pixel Clock Patcher
(05-28-2013 05:22 PM)ToastyX Wrote:(05-24-2013 09:58 AM)Badelhas Wrote: I have a qnix qx2710 and two 670s in sli, with windows 64 bits. Did the patch with the full exercise, entered test mode and created custom resolutions in CRU, at 96hz and 120hz, and it works, mouse and Window movement gets much soother. However, in games fraps never passes 60 frames per second. Tried metro last light, bioshock infinite and dirt 3. Dirt 3 even allows me to chose 96hz refresh rate but still doesn't pass the 60fps mark.Some games have frame rate caps, but I know for sure that Dirt 3 doesn't. There's no reason for it to be locked to 60 FPS when the refresh rate is 96 Hz. Are you sure you don't have a frame rate cap set somewhere? Thanks, I got it working now, had to use nvidia inspector ;-) |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 10 Guest(s)