Here's another good site to tell you exactly what your doing, and what each variable is and how its all related to each other..
So I got it working....and I checked my screen information and it says that my screen is actually running at 2560x1440 @ 70mhz refresh rate...This is from the monitor not the software I have a picture I will be uploading shortly that shows this. Is it possible that Samsung's 120Hz series are actually down-clocked 1440p monitors, or is it just the monitor interpreting the signal as if it was 1440p? I suppose it would explain all of the connection problems people have with them..It looks like displayport is limited to a 285.5 Pixelclock or the monitor is I'm not sure which. It has to be the monitor right? Because otherwise I would be able to run it at 120hz no problem I would think?
I want to point out that this is entirely different then when I was running catzilla in 1440p. During that test I checked the information of the monitor and it said 1920x1080 @ 100hz, But I know it was being downsampled because all the text was smaller in comparison to the tiger test, I had performance loss and the picture did indeed look much crisper.
Now I'm kind of worried to run this thing like this, even though my method is the same as everyone else's I'm just using a different program to do it. I remember reading that its the refresh rate that will damage the monitor and that if it supports the resolution then it supports it (its one of those either it does or it doesn't). Now I know this thing handles 1080p @ 120hz But when you step up to 1440p what would be the safe refresh rate? Does it stay the same? Do we have any monitor experts here on OCN?Edited by dekciW - 1/24/13 at 10:19pm