Overclock.net › Forums › Components › Monitors and Displays › [Official] The Qnix/X-Star 1440p Monitor Club
New Posts  All Forums:Forum Nav:

[Official] The Qnix/X-Star 1440p Monitor Club - Page 569

post #5681 of 25888
Now I was thinking. If they can just release such a monitor with displayport you will get over the bandwidth limit on a DVI dual link cable. Displayport is 17.28 Gbit/s
Main Gaming RIG
(17 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k ASUS VII Ranger Galax hof gtx 980 ti 16GB 1600mhz adata ram 
Hard DriveHard DriveHard DriveCooling
128GB SSD Samsung 840 evo 1TB WD blue Liteon 256GB SSD Phanteks PH-TC14PE 
OSMonitorKeyboardPower
Windows 8.1 ASUS PG279Q Cooler master Quickfire XT Corsair AX850w 
CaseMouseMouse PadAudio
Corsair Air carbide 540 Steelseries Ikari Laser Steelsereies QCK+ sound Blaster Z 
Audio
Sennheiser HD 598 
  hide details  
Reply
Main Gaming RIG
(17 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k ASUS VII Ranger Galax hof gtx 980 ti 16GB 1600mhz adata ram 
Hard DriveHard DriveHard DriveCooling
128GB SSD Samsung 840 evo 1TB WD blue Liteon 256GB SSD Phanteks PH-TC14PE 
OSMonitorKeyboardPower
Windows 8.1 ASUS PG279Q Cooler master Quickfire XT Corsair AX850w 
CaseMouseMouse PadAudio
Corsair Air carbide 540 Steelseries Ikari Laser Steelsereies QCK+ sound Blaster Z 
Audio
Sennheiser HD 598 
  hide details  
Reply
post #5682 of 25888
Quote:
Originally Posted by DiceAir View Post

Now I was thinking. If they can just release such a monitor with displayport you will get over the bandwidth limit on a DVI dual link cable. Displayport is 17.28 Gbit/s

I say once 4k is out we organise a lot of OCNers t o contact the sellers so they contact the manufacturers asking for monitors with what we want - i.e. no scaler, DP, a PCB natively capable of running at least 120Hz (something about lanes).

I think they did something like that over on 120Hz.net - but we'd need quite a lot of people to commit to buying beforehand.
post #5683 of 25888
Quote:
Originally Posted by Moragg View Post

I say once 4k is out we organise a lot of OCNers t o contact the sellers so they contact the manufacturers asking for monitors with what we want - i.e. no scaler, DP, a PCB natively capable of running at least 120Hz (something about lanes).

I think they did something like that over on 120Hz.net - but we'd need quite a lot of people to commit to buying beforehand.

Imagine that. That would be mindblowing but the bandwidth on DP won't be enough. I would say first we need better DP then we can think of doing this. I think they said next DP cable will go about +-21 gbit/s
Main Gaming RIG
(17 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k ASUS VII Ranger Galax hof gtx 980 ti 16GB 1600mhz adata ram 
Hard DriveHard DriveHard DriveCooling
128GB SSD Samsung 840 evo 1TB WD blue Liteon 256GB SSD Phanteks PH-TC14PE 
OSMonitorKeyboardPower
Windows 8.1 ASUS PG279Q Cooler master Quickfire XT Corsair AX850w 
CaseMouseMouse PadAudio
Corsair Air carbide 540 Steelseries Ikari Laser Steelsereies QCK+ sound Blaster Z 
Audio
Sennheiser HD 598 
  hide details  
Reply
Main Gaming RIG
(17 items)
 
  
CPUMotherboardGraphicsRAM
i7-4790k ASUS VII Ranger Galax hof gtx 980 ti 16GB 1600mhz adata ram 
Hard DriveHard DriveHard DriveCooling
128GB SSD Samsung 840 evo 1TB WD blue Liteon 256GB SSD Phanteks PH-TC14PE 
OSMonitorKeyboardPower
Windows 8.1 ASUS PG279Q Cooler master Quickfire XT Corsair AX850w 
CaseMouseMouse PadAudio
Corsair Air carbide 540 Steelseries Ikari Laser Steelsereies QCK+ sound Blaster Z 
Audio
Sennheiser HD 598 
  hide details  
Reply
post #5684 of 25888
Quote:
Originally Posted by DiceAir View Post

Now I was thinking. If they can just release such a monitor with displayport you will get over the bandwidth limit on a DVI dual link cable. Displayport is 17.28 Gbit/s

There's actually no documented bandwidth limit for dual link DVI. It's limited by the cable quality and DVI signal strength. I'm guessing it's preferable because it's older and less complex than DP (read: cheaper).
Edited by sniggleface - 8/14/13 at 8:56am
post #5685 of 25888
Quote:
Originally Posted by sniggleface View Post

There's actually no documented bandwidth limit for dual link DVI. It's limited by the cable quality and DVI signal strength. I'm guessing it's preferable because it's older and less complex than DP (read: cheaper).

Many DVI-D cables start to have a good deal of problems after 400mhz. Generally speaking a good thick cable can do almost 500mhz before capping out but will have some stability side effects. This makes us using a good cable and keeping it down to about 450mhz very doable. This is no documented limit but there a pretty good and well testing "rue of thumb" per say. Toastyx went over this and i believe overlord forums had a very good post regarding their limits i will have to find them and post a link.

EDIT: Here it is

http://overlordforum.com/topic/44-2560x1440-120hz-possible-over-dvi-d/
Edited by Spartan F8 - 8/14/13 at 10:00am
post #5686 of 25888
I need some help with CRU.

My current setup = MSi GTX 580 Lightning Xtremes in SLI with the 320.xx Nvidia driver.

Here's what I did:

1) Downloaded ToastyX's patcher and ran the full patch (since I'm running SLI)
2) Rebooted
3) Downloaded CRU
4) Opened CRU and clicked on the resolution in the detailed resolution section, hit Edit, hit Copy, backed out to the main screen, hit Add, in Manual I pasted the specs from my stock detailed resolution, then changed Hz to 96
5) I moved my new resolution with 96Hz to the top of the detailed resolution list in CRU
6) Unchecked "Include extension block" and hit OK
7) Rebooted
8) Went to Nvidia control panel to the resolution section. There was a custom resolution there, but it only listed 60Hz 32-bit color. There was nothing in the custom resolution list about 96Hz. So I looked at PC resolutions right below and clicked on 2560 x 1550 (native). My "native" resolution had changed to 2 choices: 60Hz and 16-bit color, or 96Hz with 32-bit color. I no longer have 60Hz with 32-bit color as an option under native resolution.

I ran the reset tool in CRU and rebooted and went back to Nvidia control panel and my "native" resolution under PC was back to 60Hz with 32-bit color. There was also a custom resolution there, 60Hz with 32-bit color.

So my questions are: Why are the custom resolutions from CRU not showing up in the "Custom" section of Nvidia control panel resolution? Are the custom resolutions supposed to show up under "native" resolution under PC resolutions? If so, why am I now missing 60Hz and 32-bit color (since I still have the profile in CRU)?

Thanks.
My System
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7-4770K @ 4.5GHz ASUS Maximus VI Hero Z87 Gigabyte GTX 980 Ti G1 Gaming 16GB (2 x 8GB) G.Skill Trident X DDR3-2400 
Hard DriveHard DriveHard DriveHard Drive
750GB Samsung 840EVO 256GB Crucial M4 150GB Velociraptor 1TB Samsung F1 
Optical DriveCoolingOSMonitor
Asus DRW-24B1ST Phanteks PH-TC14PE Win 10 64-bit 27" Qnix QX2710 96Hz 
KeyboardPowerCaseMouse
Cooler Master QuickFire Ultimate Cooler Master V1000 1000W 80+ Gold Fractal Design Arc Midi R2 Logitech G500s 
Mouse PadAudioOtherOther
Func Surface 1030 Asus Xonar Essence STX M-Audia AV 40 Polk PSW10 Sub 
  hide details  
Reply
My System
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7-4770K @ 4.5GHz ASUS Maximus VI Hero Z87 Gigabyte GTX 980 Ti G1 Gaming 16GB (2 x 8GB) G.Skill Trident X DDR3-2400 
Hard DriveHard DriveHard DriveHard Drive
750GB Samsung 840EVO 256GB Crucial M4 150GB Velociraptor 1TB Samsung F1 
Optical DriveCoolingOSMonitor
Asus DRW-24B1ST Phanteks PH-TC14PE Win 10 64-bit 27" Qnix QX2710 96Hz 
KeyboardPowerCaseMouse
Cooler Master QuickFire Ultimate Cooler Master V1000 1000W 80+ Gold Fractal Design Arc Midi R2 Logitech G500s 
Mouse PadAudioOtherOther
Func Surface 1030 Asus Xonar Essence STX M-Audia AV 40 Polk PSW10 Sub 
  hide details  
Reply
post #5687 of 25888
Quote:
Originally Posted by Spartan F8 View Post

Many DVI-D cables start to have a good deal of problems after 400mhz. Generally speaking a good thick cable can do almost 500mhz before capping out but will have some stability side effects. This makes us using a good cable and keeping it down to about 450mhz very doable. This is no documented limit but there a pretty good and well testing "rue of thumb" per say. Toastyx went over this and i believe overlord forums had a very good post regarding their limits i will have to find them and post a link.

EDIT: Here it is

http://overlordforum.com/topic/44-2560x1440-120hz-possible-over-dvi-d/

Thanks for that, very interesting!
Quote:
Originally Posted by coelacanth View Post

I need some help with CRU.

My current setup = MSi GTX 580 Lightning Xtremes in SLI with the 320.xx Nvidia driver.

Here's what I did:

1) Downloaded ToastyX's patcher and ran the full patch (since I'm running SLI)
2) Rebooted
3) Downloaded CRU
4) Opened CRU and clicked on the resolution in the detailed resolution section, hit Edit, hit Copy, backed out to the main screen, hit Add, in Manual I pasted the specs from my stock detailed resolution, then changed Hz to 96
5) I moved my new resolution with 96Hz to the top of the detailed resolution list in CRU
6) Unchecked "Include extension block" and hit OK
7) Rebooted
8) Went to Nvidia control panel to the resolution section. There was a custom resolution there, but it only listed 60Hz 32-bit color. There was nothing in the custom resolution list about 96Hz. So I looked at PC resolutions right below and clicked on 2560 x 1550 (native). My "native" resolution had changed to 2 choices: 60Hz and 16-bit color, or 96Hz with 32-bit color. I no longer have 60Hz with 32-bit color as an option under native resolution.

I ran the reset tool in CRU and rebooted and went back to Nvidia control panel and my "native" resolution under PC was back to 60Hz with 32-bit color. There was also a custom resolution there, 60Hz with 32-bit color.

So my questions are: Why are the custom resolutions from CRU not showing up in the "Custom" section of Nvidia control panel resolution? Are the custom resolutions supposed to show up under "native" resolution under PC resolutions? If so, why am I now missing 60Hz and 32-bit color (since I still have the profile in CRU)?

Thanks.

CRU created resolutions are different from nVidia custom resolutions; they're native to the system. You should fully avoid the nVidia custom resolution section when using CRU. I'm not sure why you're losing 32-bit at 60hz as this does not happen to me with the 320.49 drivers. Regardless, if you're planning on running a higher refresh rate and that one works with 32-bit it shouldn't really matter.
post #5688 of 25888
Quote:
Originally Posted by sniggleface View Post

Thanks for that, very interesting!
CRU created resolutions are different from nVidia custom resolutions; they're native to the system. You should fully avoid the nVidia custom resolution section when using CRU. I'm not sure why you're losing 32-bit at 60hz as this does not happen to me with the 320.49 drivers. Regardless, if you're planning on running a higher refresh rate and that one works with 32-bit it shouldn't really matter.

Thanks for the reply. That clears up one mystery -- the CRU custom resolutions show up under PC "native" resolution. Cool. thumb.gif

The remaining mystery is that I have no idea why after running CRU I lose 60Hz 32-bit color as a "native" option.

I guess I'll reinstall the 320.xx drivers, repatch, and retry with CRU.

The reason I want to see both resolutions as "native" is because when I'm not gaming I switch back to 96Hz. I have 2 monitors connected and if I run the Qnix at 96 Hz all the time neither video card downclocks. If I run Qnix at 60Hz then one of my video cards downclocks like normal.

With respect to CRU, it took me a while to figure out what to do in terms of editing, copying, adding, pasting in manual etc. The OP instructions are kind of vague. I learned how to use CRU from reading the thread rather than the OP.

EDIT:

I figured out why I was losing native 60Hz 32-bit color in Nvidia control panel. I was using Precision X to set the pixel clock to "default" and after applying that the Nvidia control panel gets all messed up and keeps thinking that 60Hz 32-bit color is a custom profile rather than a native profile.
Edited by coelacanth - 8/14/13 at 9:18pm
My System
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7-4770K @ 4.5GHz ASUS Maximus VI Hero Z87 Gigabyte GTX 980 Ti G1 Gaming 16GB (2 x 8GB) G.Skill Trident X DDR3-2400 
Hard DriveHard DriveHard DriveHard Drive
750GB Samsung 840EVO 256GB Crucial M4 150GB Velociraptor 1TB Samsung F1 
Optical DriveCoolingOSMonitor
Asus DRW-24B1ST Phanteks PH-TC14PE Win 10 64-bit 27" Qnix QX2710 96Hz 
KeyboardPowerCaseMouse
Cooler Master QuickFire Ultimate Cooler Master V1000 1000W 80+ Gold Fractal Design Arc Midi R2 Logitech G500s 
Mouse PadAudioOtherOther
Func Surface 1030 Asus Xonar Essence STX M-Audia AV 40 Polk PSW10 Sub 
  hide details  
Reply
My System
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7-4770K @ 4.5GHz ASUS Maximus VI Hero Z87 Gigabyte GTX 980 Ti G1 Gaming 16GB (2 x 8GB) G.Skill Trident X DDR3-2400 
Hard DriveHard DriveHard DriveHard Drive
750GB Samsung 840EVO 256GB Crucial M4 150GB Velociraptor 1TB Samsung F1 
Optical DriveCoolingOSMonitor
Asus DRW-24B1ST Phanteks PH-TC14PE Win 10 64-bit 27" Qnix QX2710 96Hz 
KeyboardPowerCaseMouse
Cooler Master QuickFire Ultimate Cooler Master V1000 1000W 80+ Gold Fractal Design Arc Midi R2 Logitech G500s 
Mouse PadAudioOtherOther
Func Surface 1030 Asus Xonar Essence STX M-Audia AV 40 Polk PSW10 Sub 
  hide details  
Reply
post #5689 of 25888
Quote:
Originally Posted by Spartan F8 View Post

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.
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.
""""""""""

Thanks, I appreciate it. Also, is the 59.950hz the same profile as the stock 60hz one? I was looking at the guide, but I don't see a stock 60hz profile in the CRU. If I change my resolution in Windows, both 59hz and 60hz are there though.
post #5690 of 25888
Quote:
Originally Posted by coelacanth View Post

Thanks for the reply. That clears up one mystery -- the CRU custom resolutions show up under PC "native" resolution. Cool. thumb.gif

The remaining mystery is that I have no idea why after running CRU I lose 60Hz 32-bit color as a "native" option.

I guess I'll reinstall the 320.xx drivers, repatch, and retry with CRU.

The reason I want to see both resolutions as "native" is because when I'm not gaming I switch back to 96Hz. I have 2 monitors connected and if I run the Qnix at 96 Hz all the time neither video card downclocks. If I run Qnix at 60Hz then one of my video cards downclocks like normal.

With respect to CRU, it took me a while to figure out what to do in terms of editing, copying, adding, pasting in manual etc. The OP instructions are kind of vague. I learned how to use CRU from reading the thread rather than the OP.

I totally agree. I found way more direct info from the thread as well and recommend it over the manual.
Quote:
Originally Posted by apav View Post

Thanks, I appreciate it. Also, is the 59.950hz the same profile as the stock 60hz one? I was looking at the guide, but I don't see a stock 60hz profile in the CRU. If I change my resolution in Windows, both 59hz and 60hz are there though.

This is no big deal it is merely seeing a refresh in between two common modes and displaying both as a result. You can fix this by removing the 59.95hz one and adding just a 60hz one. Sometimes it does take a video driver re-install for it to figure it out(in my experience).
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Monitors and Displays
Overclock.net › Forums › Components › Monitors and Displays › [Official] The Qnix/X-Star 1440p Monitor Club