Hi guys, you don't have a 4k Monitor like me?
wanna test how your Nvidia card really perform at real highest resolution?
Go to Nvidia Control Panel and
Create a Custom Resolution:
Horizontal pixels: 3840, Vertical lines: 2160, Refresh Rate: 60,
Timing: Manual, Active Pixels: 1920/1080, Front porch: 20/3, Sync width: 20/4,
Total pixels: 2004/1092, Polarity: Negative/Positive.
until the test worked, you need to go to Customize and make sure, that the 3840x2160 resolution is checked
Super Smash Bros Brawl - Dx11 with highest AAx8 samples (Quality 32x) @4k Resolution with a GTX 780 Windforce overclocked (Gpu clock : 72+mhz, Mem clock: +400mhz)
on very highest demanding level on brawl still 92FPS http://www.pic-upload.de/view-20382387/4k-res.jpg.html
Why on earth are you using manual timings? And why are you raising the horizontal back porch interval?
You're following that guide from neogaf aren't you. After somebody emailed me asking my advice about this method I've spent the past few days trying to figure out why they're doing that step. It shouldn't have any effect on image quality in theory and I haven't seen anyone claim that is does in any of the dozen+ copycat guides. The original English article that the rest of the sites copied off of says they got this information from a German website but fails to mention which one. I was thinking it might be this article: http://www.pcgameshardware.de/Grafikkart...51-817462/
But after getting neobrain to translate pieces of it that I thought google translate might have gotten wrong (thanks for that by the way) I have found no explanation anywhere as to why they are doing it here either.
Edit: Figured it out:
Hardforum Wrote:For smaller resolutions like 3360x2100@1680x1050 you might be able to just change the rendering resolution and don't have to touch anything else. But when you get the message "test failed", you probably will need to increase the value for the total horizontal pixels. This will in turn increase the pixel clock which as mentioned above should not go beyond 165MHz on most configurations. You will have to play a bit with the refresh rate and the total pixel values to get your desired result.
For example, on my display, the LG Flatron IPS235P (1920x1080) I had to increase the horizontal total pixels from originally 2200 to 2800 and lower the vertical total pixels from 1125 to 1090 for 3840x2160@54Hz to work and to stay below 165MHz.
It's for stability. Nvidia's downscaler apparently isn't very stable when the difference in input/output horizontal pixels is too high. Why the fuck inserting blank pixels into the output signal fixes this I have no idea.
Still it's clear that these guys have no idea what they're doing based on their misuse of terminology and have figured out this stuff accidentally.
For the record what you're doing is rendering a 3840 x 2160 image in game then letting the drivers downscale that to 1920 x 1080 before outputting it to the display. For some reason a lot of people who read these downscaling guides get the idea that they are actually pushing 3840 x 2160 through DVI to the monitor.
I don't recommend adjusting the DVI timings unless you have to.
You should also link to whatever downscaling guide you used. Of course they're all the same since they copy/paste off of each other so I suppose it doesn't really matter which one you link to.
Why on earth are you using manual timings? And why are you raising the horizontal back porch interval?
You're following that guide from neogaf aren't you. After somebody emailed me asking my advice about this method I've spent the past few days trying to figure out why they're doing that step. It shouldn't have any effect on image quality in theory and I haven't seen anyone claim that is does in any of the dozen+ copycat guides. The original English article that the rest of the sites copied off of says they got this information from a German website but fails to mention which one. I was thinking it might be this article: http://www.pcgameshardware.de/Grafikkart...51-817462/
But after getting neobrain to translate pieces of it that I thought google translate might have gotten wrong (thanks for that by the way) I have found no explanation anywhere as to why they are doing it here either.
Edit: Figured it out:
Hardforum Wrote:For smaller resolutions like 3360x2100@1680x1050 you might be able to just change the rendering resolution and don't have to touch anything else. But when you get the message "test failed", you probably will need to increase the value for the total horizontal pixels. This will in turn increase the pixel clock which as mentioned above should not go beyond 165MHz on most configurations. You will have to play a bit with the refresh rate and the total pixel values to get your desired result.
For example, on my display, the LG Flatron IPS235P (1920x1080) I had to increase the horizontal total pixels from originally 2200 to 2800 and lower the vertical total pixels from 1125 to 1090 for 3840x2160@54Hz to work and to stay below 165MHz.
It's for stability. Nvidia's downscaler apparently isn't very stable when the difference in input/output horizontal pixels is too high. Why the fuck inserting blank pixels into the output signal fixes this I have no idea.
Still it's clear that these guys have no idea what they're doing based on their misuse of terminology and have figured out this stuff accidentally.
For the record what you're doing is rendering a 3840 x 2160 image in game then letting the drivers downscale that to 1920 x 1080 before outputting it to the display. For some reason a lot of people who read these downscaling guides get the idea that they are actually pushing 3840 x 2160 through DVI to the monitor.
I don't recommend adjusting the DVI timings unless you have to.
You should also link to whatever downscaling guide you used. Of course they're all the same since they copy/paste off of each other so I suppose it doesn't really matter which one you link to.
I got those settings from my mate club4ghz which works great, btw didn't read any 4k downsampling tutorials
Yeah, there's plenty of tuts on the net, so it's pointless to write another.
Just a heads-up though, the AMD DownsamplingGui application won't work with the new drivers.
The last confirmed driver it works with is 12.11. Set up your resolution on that driver, and update your drivers and it'll still work.
