• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

NVIDIA LIMITING PIXEL CLOCK ON 6 SERIES CARDS

There weren't many catleap 2b's which allowed people to overclock. Anyway reading the site this pixel clock also applies to AMD too however there is a driver hack which fixes it.

--------------
There is a driver mod for AMD video cards that allows an unlocked pixel clock for both Single Card and Crossfire setups (though some have reported certain limitations with Crossfire still). You can follow ToastyX's thread by clicking here.
 
because the spec for DVI is 165mhz per channel, so dual link is 330mhz
they have decided, for whatever reason - possibly errors occuring when running out of spec - to adhere to the spec going forward

there is currently a driver hack to get it working out of spec on AMD - various parties are also working on a hack for NV systems

there's also nothing to say that AMD won't take steps to stop the hack from working on their drivers either (as mentioned above it doesn't always work as it is)

DisplayPort would support up to 2560x1600 @ 120hz

the catleap 2b's aren't even guaranteed to hit 120hz, a lot top out at/below 100hz
 
Last edited:
Pretty much a non-issue tbh since there isn't a market of 2560×1440 @ high refresh rates yet.
A lot of hype on this is a good way to try and steer people to the red side.
 
How small the amount of people wanting it is not the point, the point is it was working before and now is not, why take it away.

The people who do have the cat leap Monitors would rightly be upset about it, which none of you are owners of so of coarse its a non issue to you.

Its not about people wanting manufacture to do something at great experience when its not worth the investment as so few people would buy it, its something that was already there and its at no expense to leave the option in.

It no difference that some people get upset that AMD do not have a force V-sync through the driver in DX, only OpenGL because that was the spec from MS for vista and windows 7 even though most games have V-sync, but NV still has the V-sync on DX through the driver option.

I could say that a non issue because im a Vsync all the way user and im on AMD cards plus there are other options available to force it which i cant remember the last time i had to use one.

Even though the force through driver Vsync is not with the spec it does not mean that NV users should not get up set if NV remove the option.

Me personally would like if AMD put force through driver Vsync but there are other SW options if i need it but for this LIMITING PIXEL CLOCK issue it may need a change of gfxc card which is worlds apart.

Its best to have the option and not need it than need the option and not have it.
 
Last edited:
it makes little sense to limit the pixel clock unless it was causing hardware issues. I haven't kept up on it but i dont think there has been any problems with hardware failing due to the pixel clock? Bit of an odd decision really......


....unless nvidia decide to charge a premium for it.
 
james.miller said:
it makes little sense to limit the pixel clock unless it was causing hardware issues. I haven't kept up on it but i dont think there has been any problems with hardware failing due to the pixel clock? Bit of an odd decision really......


....unless nvidia decide to charge a premium for it.
Click to expand...

If its causing issues with the hardware then that's another matter.
 
You must log in or register to reply here.
Back
Top Bottom