Originally Posted by txcLOL
got my first QNIX yesterday and most of the setup works quite good. OC is possible to ~100 hz, 110-120 gave me some issues. I've not read all of the posts here on these 568 pages, so maybe an more experienced dude can help me with my question.
The Topic is the refresh rate in games. At the Desktop there are no problem, there are 100 Hz. If i play, for expample, Battlefield 3, there are also no problem (maybe because BF supports all refresh rates?!). But, if i play a game like Payday 2 oder CS:GO, i can see, that the refresh rate is 60. Is this, because the lack of native support of these games?
I tried overclock only with this in built-in Pixel Clock utility in Precision. I'm on the newest patched beta driver@ my GTX 780.
Try searching for "forcing refresh rate" not only in this thread but many games have sites that relate to forcing the highest available refresh. Also if you do get to 120hz and put it as a native resolution the nvidia control panel has a "preferred refresh rate" option that appears after a driver update. This will force games that do not have a refresh rate option to use the 120hz refresh. You can find my detailed post regarding this by again searching for "force refresh rate"
Another option that has help many people is installing the catleap monitor driver or another related 120hz driver(you can easily make them with a EDID creator). You can find this by searching "catleap driver" in this thread.
Yet another option or possibility rather is checking you in game versus driver level vsync since these can not only conflict but can have issues with an OC refresh. You can find info on this by searching "vsync" in this thread.
Hopefully this gets you in the right direction and you don't mind doing some searching because all of your questions have been gone over several times and the information already posted is very detailed and helpful. Also by searching through this thread looking at my posts along with some otehr members that have been around since the beginning will be beneficial to your endeavor.
Originally Posted by apav
Massaging does nothing and it's in the same spot even when windows is rotated upside down. It's definitely the monitor, the question is, does this mean bad news? Or is this just a harmless defect?
I noticed something else too, but this seems like it could be a common issue. When I overclock my monitor to 120hz, I see the background's brightness flickering on certain sites. The best examples I have are http://www.tomshardware.com/
. Again it isn't all that noticeable, but when I look close enough I see these shadowy lines flickering on the background of these sites. If I reduce the overclock to 110hz, the flicker goes away. I understand the screen getting darker is common, but what about this? Haven't spotted it anywhere else besides in browser on certain websites. It's not scan lines, it's more like the screen is flickering in brightness at certain spots, causing these dark lines to appear and disappear. I don't think this is PWM.
I have replied to your other thread you started but i am also moving it here because this is the main Qnix thread and is where this inquiry should be. I recommend looking back a few pages at the timings posts that have been going on. they will help you with the flickering. Again the weird pixel is likely not a big deal i have seen plenty of mus-behaving pixels before that never were an overall indication of failure. I think you are being a bit paranoid(no offense) due to the couple panels you went through to get a good one.
The flickering is a form of instability due to the excessively high pixel clock over the DVI cable. This can be fixed in two ways:
1. have a better cable
2. try manually getting the best timings and not just changing the refresh rate(which is like like just overclocking a CPU with the multiplier it works but it is definitely not even close to the best way to do it)
The "weird" pixel is not something i would worry too much about. If it was only doing it when overclocked or if it was spreading(meaning you found more over a short time) sure you might be worried. I have seen single pixels on a screen do a lot of things, more often then not it stays just on that pixel but i have never seen what you are describing though i would never likely done so much testing over a single pixel. Overall i think you are reading to much into this. Getting to 135hz without any real trial and error is a fantastic panel. We have been making some good progress in information relating to custom timings and stability over in the Qnix club that would very likely help you out on this and i recommend doing a little reading about the flickering or "scanning" you are seeing and you will likely find a way to adjust to not have to deal with it any longer like i did.