internal resolution and aa suggestion
|
02-01-2012, 07:08 PM
02-01-2012, 09:48 PM
(01-31-2012, 09:39 PM)andr2535 Wrote: My point is that like all other hardware screens are also getting better and they areAlmost a decade since the first 30" 2560x1600 LCD came out and we're still stuck there unless you can afford a 4K display. Everything else has gone from 16:10 to 16:9 so resolution has gone down so its going to a while before this a problem unless you do eyefinity with widescreen hack (if that works). 02-02-2012, 06:32 AM
(This post was last modified: 02-02-2012, 06:33 AM by NaturalViolence.)
Quote:Does that mean that it is not an easy code to create? No, it means that nobody wants to do it.
"Normally if given a choice between doing something and nothing, I’d choose to do nothing. But I would do something if it helps someone else do nothing. I’d work all night if it meant nothing got done."
-Ron Swanson "I shall be a good politician, even if it kills me. Or if it kills anyone else for that matter. " -Mark Antony 02-02-2012, 10:38 AM
He wants a custom option to implement support for arbitrary internal resolutions.
"Normally if given a choice between doing something and nothing, I’d choose to do nothing. But I would do something if it helps someone else do nothing. I’d work all night if it meant nothing got done."
-Ron Swanson "I shall be a good politician, even if it kills me. Or if it kills anyone else for that matter. " -Mark Antony 10-02-2013, 03:31 AM
Who says you need a 4K-Screen to see the difference between 4xnative and even higher internal resolutions?
I made some screenshots in Mario Galaxy 2 to demonstrate the difference on a 1080p monitor. The first one is made with 4x internal resolution and the fullscreen window size is 1920x1080. So in this case, a 2560x2112 image is downsampled for 1080p. For the second one, i used downsampling to achieve an even higher resolution than 4x native. So i set internal resolution to "auto window size" and created a custom video resolution in the graphic card's driver of 3840x2160. So in the second case, a 3840x2160 image gets downsampled to 1080p. You can see a clear difference between the two if you look at the edges. Even using anti-aliasing, the difference is still visible (not only as downsampling works on the whole image, while MSAA only works on the edges; it also makes more details on textures visible in the distance; and third, it affects the quality of post process-shaders such as SweetFX) ! 4x native resolution (2560x2112) on 1080p: http://www7.pic-upload.de/01.10.13/3fymxjkbaf1.jpg 3840x2160 on 1080p: http://www7.pic-upload.de/01.10.13/r49diupkxu8.jpg Conclusion: More than 4x internal resolution definitely makes sense, so please include a function to insert a custom internal resolution as PCSX2 already has. Thx! 10-02-2013, 03:47 AM
afaik the only reason they haven't is because they don't know how they want to implement the UI XD
10-02-2013, 03:58 AM
10-02-2013, 04:02 AM
PCSX2 also provides 5x and 6x but they are overkills. Custom resolution option is better as it covers any resolutions. I found it quite useful as I could set the IR to 1.4x, 1.5x, etc. Anyway, if what you want is to use more than 4x, then just having 5x and 6x will be suffice.
|
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)