Downsampling: How to - Page 4

applejack · *Last edited by applejack; 04-29-2012 at 22:06.*

Quote:

Originally Posted by Nisei

With a Full HD 120Hz monitor you're running dual link DVI. At 1920x1080@120Hz my pixel clock is above 285. You've got twice the pixelclock as with a 60Hz monitor. So lower your refresh rate to 60Hz and you should be able to get 3840x2160.

I've tried to setup 3840x2160@60hz but couldn't get there, auto and manual timings, desktop is zoomed in or something with a bigass cursor, or screen is distorted, or both.
I also tried 2560x1440@75hz with auto timings as Nisei suggested - but the screen got distorted. while this exact res work fine with manual timings.
So, while on it, using same res that works manually, I tried to raise horizontal total pixels one notch further, just for the pixel clock to pass 165mhz "limit", and found out screen got distorted again.
so it seems to me that pixel clock is still limited to 165mhz on dual link DVI when downsampling, maybe a software (driver/win7) limit, go figure...
maybe I need to setup different "front porch"/"sync width" ? as I only set these as shown in pictures (don't know much about it). I do know the drill with total pixels though (at least I'd like to think I do).

sab3r · 04-30-2012, 00:44 | posts: 2 | Location: Iceland

Quote:

Originally Posted by Nisei

[edit] I was thinking, when you take a look at the screenshot above; the upper part of the settings is what the drivers report to Windows, the lower part (Timings and actual pixel width and height) is what the card is sending to your monitor and you better leave those alone. So what you're doing in the upper part of the panel has absolutely got nothing to do with your monitor. Leave the timings on Auto and just change the upper custom resolution. Then, when you run into a certain resolution which fails the test, it's your graphics card not being able to handle those timings, not your monitor. Beware though, never try to use this custom resolution in the main monitor resolution settings pane because then the card will actually send those timings and resolution to your monitor. That's why you're getting the warning when using the Custom Resolution panel for the first time. [/edit]

GPU scaling doesn't work for me. I've got a 22" monitor that has a native resolution of 1680x1050 and a Geforce GTX 460. All graphics cards should support 1080p, yet I get a "Timing not supported" from the monitor when I create a custom resolution with 1920x1080.

applejack · 04-30-2012, 11:04 | posts: 324 | Location: Israel

I did some more testings and found out that since upgrading from GTX570 to GTX680 (inc. drivers), I can no longer create custom resolutions higher than this 2560x1440. the desktop "zoom in" never happened before.
I actually have several pictures I took listing all my successfully set high resolutions, but same settings just wont work now.

I'm using same monitor. this inconsistency must relate to drivers and/or v.card.
so all my testings seem worthless now. especially for an unsupported "feature".

however I do have my GTX570 sitting around, maybe I'll push it in before selling, just to make sure driver is the problem here, not my precious GTX680.

Nisei · 04-30-2012, 11:11 | posts: 62 | Location: the Dutch Mountains

That's a known driver bug. Above 2560 it no longer downsamples to desktop res. Let's hope this is solved in the next WHQL.

GrandMax · 05-01-2012, 01:37 | posts: 191

Quote:

Originally Posted by Nisei

That's a known driver bug. Above 2560 it no longer downsamples to desktop res. Let's hope this is solved in the next WHQL.

Interesting comments. I also find it funny to play with all these clock settings if the image sent to the monitor is still 1080p.

My GTX680 can send the 2560x1440 to my Samsung LN46D630.

Do I understand it is not worth trying higher res than 1440p with the current drivers?

To OP, great guide man. It took me a while to figure out why you kept 1123 vertical pixel if you could go down to 1104. But then I read one of the last paragraph where you explained it.

GrandMax · 05-01-2012, 04:43 | posts: 191

Quote:

Originally Posted by applejack

I did some more testings and found out that since upgrading from GTX570 to GTX680 (inc. drivers), I can no longer create custom resolutions higher than this 2560x1440. the desktop "zoom in" never happened before.
I actually have several pictures I took listing all my successfully set high resolutions, but same settings just wont work now.

I'm using same monitor. this inconsistency must relate to drivers and/or v.card.
so all my testings seem worthless now. especially for an unsupported "feature".

however I do have my GTX570 sitting around, maybe I'll push it in before selling, just to make sure driver is the problem here, not my precious GTX680.

I confirm this issue too. GTX680 here. 301.24

I was glad to see 3840x2160 working though. But the scaling is screwed up.

As anyone tried other gpu scaling functions like fullscreen instead of aspect ratio?

MfA · **Memory**: 4GB DDR2 1000MHz 5-5-5-15

It's driver related.. Check driver thread

applejack · *Last edited by applejack; 05-03-2012 at 22:50.*

thanks for clarifying.

just installed 301.34 :

2560x1440 @ 60hz (auto timings)
2560x1440 @ 75hz (manual timings)
2880x1620 @ 60hz (auto timings)

3200x1800 @ 60hz - fails - red screen. (worked with older drivers / GTX570)
3840x2160 @ 54hz - fails - red screen. (worked with older drivers / GTX570)

this red screen... I've seen it before with my gtx680 (experimenting OC).
I'm now yet tempted to test gtx570 on new drivers, although 2880x1620 is quite enough. probably isn't worth the hassle...

GrandMax · 05-04-2012, 23:24 | posts: 191

Quote:

Originally Posted by applejack

thanks for clarifying.

just installed 301.34 :

2560x1440 @ 60hz (auto timings)
2560x1440 @ 75hz (manual timings)
2880x1620 @ 60hz (auto timings)

3200x1800 @ 60hz - fails - red screen. (worked with older drivers / GTX570)
3840x2160 @ 54hz - fails - red screen. (worked with older drivers / GTX570)

this red screen... I've seen it before with my gtx680 (experimenting OC).
I'm now yet tempted to test gtx570 on new drivers, although 2880x1620 is quite enough. probably isn't worth the hassle...

Nice. Auto setting work at least up to 1620p on auto timings on my GTX 680.

1620p to 1080p is 2x OGSSAA. Do you know if FXAA is applied on the 1080p or the 1620p.

I get the same red screen at 2160p on auto settings.

GrandMax · 05-22-2012, 23:56 | posts: 191

Is downsampling fixed for 301.42?

I am referring to the red screen above 1620p.

applejack · 05-23-2012, 00:59 | posts: 324 | Location: Israel

guess not, as I still cannot do 1800p.

Bradders684 · 05-26-2012, 11:47 | posts: 204

3840x2160 is working for me, i am not using a custom monitor.inf.

Grahf · 05-26-2012, 17:07 | posts: 1,817 | Location: New England, USA

I love you.

Faks · 06-02-2012, 12:33 | posts: 88 | Location: Europe

very much of useful information.

Xanvast · *Last edited by Xanvast; 06-09-2012 at 00:10.*

WoW so cool I managed to get 3840x2400@49Hz

Xanvast · 06-15-2012, 00:26 | posts: 123 | Location: France

I finally found the right settings to get 3840x2400 with sharp look.
This is just awesome (and really really heavy)
http://img4.hostingpics.net/pics/561...1501110054.jpg
http://img4.hostingpics.net/pics/119...1501111630.jpg

MrBonk · 06-15-2012, 08:52 | posts: 444

hard to tell true quality. All kinds of compression artifacts it looks like. Unless the game looks like that?

Can you take lossless shots (whether with PNG or BMP) and post the downsampled shot and Og size?

Xanvast · 06-15-2012, 11:19 | posts: 123 | Location: France

I think it would not be interesting to make the same with lossless screenshots (moreover for now I have some internet difficulties)
The game actually looks that blurry in 1920x1200...

Xanvast · 06-29-2012, 20:59 | posts: 123 | Location: France

Hey everyone,
I just wanted to warn you about those cheap 27" 2560x1440 korrean monitors you can buy on ebay.
I had no success at all with my Yamakasi monitor and downsampling. That is a big disappointment...

UNREAL_2004 · 07-03-2012, 04:28 | posts: 849 | Location: Bilbao, Spain

I created 3 custom resolutions (2560x1440,2880x1620,3840x2160) and all of them runs perfectly on desktop but i can only use 2560x1440 for games, the other two res are hidden...

whats up?

Xanvast · 07-03-2012, 14:32 | posts: 123 | Location: France

If your resolution is below 60Hz this is normal, they are hidden and you have to modify the driver of your monitor for them to show up.
Here is a link with a tutorial explaining how to do it :
http://www.overclock.net/t/1237470/h...le-in-the-game

UNREAL_2004 · 07-04-2012, 09:01 | posts: 849 | Location: Bilbao, Spain

Quote:

Originally Posted by Xanvast

If your resolution is below 60Hz this is normal, they are hidden and you have to modify the driver of your monitor for them to show up.
Here is a link with a tutorial explaining how to do it :
http://www.overclock.net/t/1237470/h...le-in-the-game

Thanks

ffbecker · 07-06-2012, 00:18 | posts: 1

UNREAL, could you please post some screens resized for your native resolution? Some Skyrim screens would be nice. Thx.

applejack · *Last edited by applejack; 07-09-2012 at 01:55.*

so, no kepler owner successfully configured anything higher than 1620p yet ?

can we conclude it's some kind of hardware limit after all ? hate that red screen.

Xanvast · 07-09-2012, 11:56 | posts: 123 | Location: France

Wow I didn't know Kepler wasn't allowing Downsampling I'm glad I didn't buy a couple of these...