Should the gtx 295 have a straight dvi or hdmi connection?

This topic is locked from further discussion.

Avatar image for EdgeOfThorns316
EdgeOfThorns316

155

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#1 EdgeOfThorns316
Member since 2006 • 155 Posts

As opposed to a vga connection with a dvi adapter on the end of it?

Im trying to figure out this monitor issue im having still, where on some screens it looks like horizontal, wavey, fluttering or static interference, or electronic interference...as if some connection just isnt right. And im wondering if using those adapters can cause certain minor issues like that.

Im thinking a straight hdmi or dvi connection may fix it, what do some of you think? The things i see are only visible on some screens, but its just annoying...a rolling fluttering kind of puling lines going horizontally.

Avatar image for XaosII
XaosII

16705

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#2 XaosII
Member since 2003 • 16705 Posts

Why would you ever use the VGA port if your monitor uses DVI? Im not even sure why you are asking us about this? Why not just switch the cables around? Surely it would've taken less time and effort to do this change than to write up a whole post asking us about it?

VGA is analog and old technology and prone to missynching. Its likely thats is the the cause of wavy patterns in areas of high detail and contrast. Stick to DVI and HDMI.

Avatar image for codezer0
codezer0

15898

Forum Posts

0

Wiki Points

0

Followers

Reviews: 44

User Lists: 0

#3 codezer0
Member since 2004 • 15898 Posts

Why would you ever use the VGA port if your monitor uses DVI?

XaosII
The Gateway FPD2185W I have has VGA and (supposedly) DVI with HDCP; yet as it is right now, I can't get a signal to show up on it at all with the system it's on via DVI. I have to use VGA in order to see a desktop at all.
Avatar image for slayerpker
slayerpker

217

Forum Posts

0

Wiki Points

0

Followers

Reviews: 1

User Lists: 0

#4 slayerpker
Member since 2008 • 217 Posts

It could be also that you are not running at your native resolution. My Acer Monitor's Native Res is 1680x1050, and It gets wavy and the refresh rate gets very noticeable if I run it at any res that is not 16:10 or4:3. The same thing happens no matter if I use the d-sub or dvi

Avatar image for codezer0
codezer0

15898

Forum Posts

0

Wiki Points

0

Followers

Reviews: 44

User Lists: 0

#5 codezer0
Member since 2004 • 15898 Posts

It could be also that you are not running at your native resolution. My Acer Monitor's Native Res is 1680x1050, and It gets wavy and the refresh rate gets very noticeable if I run it at any res that is not 16:10 or4:3. The same thing happens no matter if I use the d-sub or dvi

slayerpker
Was that referring to me? If so, well, I've tried everything. The first time the problem showed up, it was with Windows Vista and an NVIDIA graphics card. Simply, I couldn't get a display on DVI after I installed the display driver. I've tried contacting both eVGA (since I was using the 8800GTS as my primary at the time), both Vista 32-bit and 64-bit, and also contacted NVIDIA support directly for help, and even tried some of their beta drivers to try and correct the problem. Issue is, the problem still occurred. And while I could get a display on DVI when I unplug the cable and reinsert it, I then am still unable to select the native resolution. But at least it's better than what I am now encountering with this same monitor, on a separate system using Windows XP and an ATi Radeon card. In that system, I can't get a signal after I install the video driver... period. I know the connection works because I can see the POST scren and even see the windows boot screen; but right when the video driver is supposed to be loading, it just goes black, and the thing stops sending a signal on DVI. I've also tried running the LiveEval Ubuntu on the system with the monitor connected via DVI and am able to use Ubuntu with the system like that. The only thing I can think of is that it's either an issue with the display drivers, or the HDCP fiasco.