NVIDIA Pixel Clock Patcher

[ToastyX]

(06-05-2015 04:54 PM)jdubzisfaded Wrote:  What I meant by 320MHz when using nVidia custom resolution, is that I used CRT Timings which brought me to 312MHz and then added extra pixels to the total pixels amount in the manual timings section which may have made it look better or worse I am not a TV guru but I know my way around a PC.

You shouldn't do that unless the TV can't handle standard timing parameters correctly. You're just wasting bandwidth with a higher pixel clock. Use the "LCD standard" timing option.

(06-05-2015 04:54 PM)jdubzisfaded Wrote:  and yes 1440p does not show up in Windows but it shows up in nVidia custom resolutions.

I don't understand what you mean because the problem doesn't make sense. If you mean the resolution is selectable in the NVIDIA control panel but not in the Windows screen resolution settings, then I don't see how that could happen unless there's a driver bug. If you mean the resolution is listed in the NVIDIA control panel as a "Custom" resolution instead of a "PC" or "HD" resolution, then that could only happen if you added a custom resolution using the NVIDIA control panel, but then it should also be listed in the Windows screen resolution settings. CRU resolutions wouldn't be listed as "Custom" resolutions, and you don't need to add the same resolutions with both.

(06-05-2015 04:54 PM)jdubzisfaded Wrote:  One Time it even showed as native so I thought it was sure to work. Yet as I said I just got an incompatible signal causing my display to display a "no signal" blue screen.

The first detailed resolution in the main window is considered the native resolution. Your screen shot covers up the main window, so I can't see what you have defined for the native resolution. You need to define the resolution you want to be native as the first detailed resolution.

(06-05-2015 04:54 PM)jdubzisfaded Wrote:  Also, will the CRU work on all the driver versions.

CRU is not driver-specific. CRU will work with any driver that supports Windows EDID overrides.

(06-05-2015 04:54 PM)jdubzisfaded Wrote:  And why do I have no need for pixel patcher. From what I have read on it I will be limited to 165MHz on HDMI.

That is the case with single-link DVI and HDMI on older cards. Newer cards can handle higher pixel clocks with HDMI, but HDMI support must be defined in the extension block or it will behave like single-link DVI.

(06-05-2015 04:54 PM)jdubzisfaded Wrote:  I read that I needed an HDMI.dat file but I am at my programming job and can't remote in to my pc too much.

The hdmi.dat file just contains an HDMI support data block with the default settings, so you don't need it if you already added it manually.

(06-05-2015 04:54 PM)jdubzisfaded Wrote:  If all of my BS is not 20$ I understand I am being a pain. Name your price in a PM and I will think if it is reasonable

Any donation is welcome.

(06-05-2015 04:54 PM)jdubzisfaded Wrote:  edit 3: lol I think my monitor may be off... and thats the only reason it seems to work. I am an idiot. DAMNIT

Some monitors won't send an EDID when they're off or switched to a different input, which can cause problems with monitor detection. Did you get everything sorted out?