Article View: comp.sys.ibm.pc.games.rpg
Article #720643Re: OT-Monitor question
From: DMP
Date: Mon, 22 Sep 2014 21:45
Date: Mon, 22 Sep 2014 21:45
33 lines
3447 bytes
3447 bytes
On 9/22/2014 4:33 PM, Ross Ridge wrote: > In article <lvptu6$v10$1...@dont-email.me>, DMP <nom...@nodomain.com> wrote: >> A friend of mine is getting rid of his gaming stuff and I have a shot at >> getting a Samsung UHD monitor for cheap. My graphics card a GeForce >> GTX770, so as I look at specs, I don't see the card as an issue. Present >> monitor a Sammy 244T that I've been happy with for many years. > If by UHD you mean 3840x2160, the so called "4K" resolution, then I'd > pass on it. I'm not sure any video card is up to displaying modern > games at that resolution without having to turn down the effects. > Also unless the monitor is huge, you're going to need UI scaling keep > things readable in a lot of games. You'd need the new monitor to be > about 46" to keep things the same size of the 24" you have now. > > If it's only 2560x1440 then your graphics card can probably hold up, > but I still would probably give it as pass. You also probably won't > need UI scaling, it only needs to be 30" to keep things the same size. > I'd be concerned with how well games support that resolution. It should > be fine with anything recent, but I play a lot of older games, and going > from 1920x1600 to 2560x1440 would only increase the number of games > that I can't play at the native resolution of my montitor. If you're > mainly playing the latest FPS shooters that shouldn't be a problem, > but then you're graphics card is more likely to be an issue in that case. > > Ross Ridge > FWIW, here's something I found while doing research....I did not know there was such a thing as a display port as opposed to HDMI. Nvidia says their 600 & 700 will do 4K. As for the other issues you raised, I don't see that in the article but I will do some more reading. https://developer.nvidia.com/4k-ultra-high-resolution-development
Technical Details
Message-ID:
<lvq57q$j9g$1@dont-email.me>Path:
mbox-mo1.pugleaf.net!kf7ni76176lbc.0!nntp.google.com!feeder1.cambriumusenet.nl!82.197.223.108.MISMATCH!feeder2.cambriumusenet.nl!feed.tweaknews.nl!193.141.40.65.MISMATCH!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!border2.nntp.ams2.giganews.com!backlog4.nntp.ams3.giganews.com!backlog4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!news.teledata-fn.de!news.albasani.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mailReferences:
<lvptu6$v10$1@dont-email.me> <lvq133$ph7$1@rumours.uwaterloo.ca>Show Full Headers
Complete Article Headers
X-Received: by 10.194.7.199 with SMTP id l7mr4473954wja.2.1411871469459; Sat, 27 Sep 2014 19:31:09 -0700 (PDT) Path: mbox-mo1.pugleaf.net!kf7ni76176lbc.0!nntp.google.com!feeder1.cambriumusenet.nl!82.197.223.108.MISMATCH!feeder2.cambriumusenet.nl!feed.tweaknews.nl!193.141.40.65.MISMATCH!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!border2.nntp.ams2.giganews.com!backlog4.nntp.ams3.giganews.com!backlog4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!news.teledata-fn.de!news.albasani.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: DMP <nom...@nodomain.com> Newsgroups: comp.sys.ibm.pc.games.rpg Subject: Re: OT-Monitor question Date: Mon, 22 Sep 2014 17:45:16 -0400 Organization: A noiseless patient Spider Lines: 33 Message-ID: <lvq57q$j9g$1@dont-email.me> References: <lvptu6$v10$1@dont-email.me> <lvq133$ph7$1@rumours.uwaterloo.ca> Mime-Version: 1.0 Injection-Date: Mon, 22 Sep 2014 21:44:26 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="feee13a3009245c59fe10e3fe29cdb22"; logging-data="19760"; mail-complaints-to="ab...@eternal-september.org"; posting-account="U2FsdGVkX19dwTF53qsYKd42aSTOEprfYOSNDRkRBf0=" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 In-Reply-To: <lvq133$ph7$1@rumours.uwaterloo.ca> Cancel-Lock: sha1:A/CPXbem8Ze33ZZSI7NNvBEczmM= Bytes: 3175 X-Original-Bytes: 3038 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit