Quote:visually, it appears 1xir, 4xssaa = 2xir, no ssaa. Is that true programatically as well?
Yes and no.
Both will produce 4x the native resolution, however they use different scaling filters. I don't know what output resolution townet was using. If the output resolution is higher than the internal resolution (upscaling) they should produce the same image quality. You might notice a difference with a higher internal resolution.
(01-24-2012, 05:05 AM)NaturalViolence Wrote: [ -> ]Quote:visually, it appears 1xir, 4xssaa = 2xir, no ssaa. Is that true programatically as well?
Yes and no.
Both will produce 4x the native resolution, however they use different scaling filters. I don't know what output resolution townet was using. If the output resolution is higher than the internal resolution (upscaling) they should produce the same image quality. You might notice a difference with a higher internal resolution.
Full screen resolution 1920 x 1080
could you take a screenshot of auto(window size)?
Auto adjusts the internal resolution based on your windowed/fullscreen resolution.
If your height resolution is 480 or lower it will use 1x.
If your height resolution is higher than 480 but lower than 1050 it will use 2x.
If your height resolution is 1050 or higher, but lower than 1920 it will use 3x.
If your height resolution is higher than 1920 it will use 4x.
His image quality will depend on what he sets his windowed/fullscreen resolution to.
(01-24-2012, 01:27 PM)NaturalViolence Wrote: [ -> ]Auto adjusts the internal resolution based on your windowed/fullscreen resolution.
If your height resolution is 480 or lower it will use 1x.
If your height resolution is higher than 480 but lower than 1050 it will use 2x.
If your height resolution is 1050 or higher, but lower than 1920 it will use 3x.
If your height resolution is higher than 1920 it will use 4x.
His image quality will depend on what he sets his windowed/fullscreen resolution to.
That only applies to Auto (Multiple of 640x528) though.
(01-24-2012, 01:03 PM)boogerlad Wrote: [ -> ]could you take a screenshot of auto(window size)?
I think is better you try it your self, set it what you want.
... Just press F9 to take screen shots, the file are store at user/screen shots folder.
(01-24-2012, 01:27 PM)NaturalViolence Wrote: [ -> ]Auto adjusts the internal resolution based on your windowed/fullscreen resolution.
If your height resolution is 480 or lower it will use 1x.
If your height resolution is higher than 480 but lower than 1050 it will use 2x.
If your height resolution is 1050 or higher, but lower than 1920 it will use 3x.
If your height resolution is higher than 1920 it will use 4x.
His image quality will depend on what he sets his windowed/fullscreen resolution to.
Right.
Quote:That only applies to Auto (Multiple of 640x528) though.
That's right. I forgot we renamed fractional to Auto (window size).
In that case Auto (Multiple of 640x528) performs the behavior I listed above and auto (window size) adjusts the internal resolution to match your windowed/fullscreen resolution.
Quote:It appears 4xssaa is broken, and 1ir9ssaa < 3ir0ssaa
Quote:SSAA for DX9 is fine for 9x, but borked for 4x.
(01-24-2012, 05:05 AM)NaturalViolence Wrote: [ -> ]Quote:visually, it appears 1xir, 4xssaa = 2xir, no ssaa. Is that true programatically as well?
Yes and no.
Both will produce 4x the native resolution, however they use different scaling filters. I don't know what output resolution townet was using. If the output resolution is higher than the internal resolution (upscaling) they should produce the same image quality. You might notice a difference with a higher internal resolution.
I don't see why is that true. With 1xir it has less pixels to show the frame, even tough it was rendered with a higher resolution because of AA, shouldn't it be a bit blurrier, or show less detail than 2xir with no aa, where both the shown and the rendered frame have double the native resolution?