RachelB Wrote:That's really not how it works.
The code is a bit different but it has the exact same end result. You can test it yourself if you do not believe me. Also remember this post that I made awhile back:
NaturalViolence Wrote:Both IR and SSAA raise the actual IR. They are both equally demanding if the same IR is reached.
The IR setting represents the scale applied to each axis. You can calculate the effect on total resolution by squaring it. So for example a 2x IR settings gives you 4x IR (2^2 = 4). Setting IR to 3x gives you 9x the IR (3^2 = 9). SSAA also increases the IR but the SSAA settings represent the total increase in resolution. So 4x SSAA actually increases your IR by 4x. To get your total IR you simple multiply the square of your IR setting by the number of SSAA samples (use 1 if SSAA is disabled).
So:
4x IR ((4^2) x 1) = 16x
3x IR + 4xSSAA ((3^2) x 4) = 36x
As you can see 3x IR + 4xSSAA is a lot more demanding. Not because SSAA is inherently more demanding but because the total IR is higher with this particular combination.
See how confusing this is? The IR setting was originally called "efb scale" which was a much better description of what it does but people were confused by that term so they changed it to "internal resolution". However settings the "internal resolution" to 2x doesn't double the IR, it quadruples it. Which is why I still think that it should either be renamed back to efb scale or the option strings should be renamed to reflect the increase in IR rather than the scale applied to each axis.
2xSSAA will not be added because 2 is not a perfect square. Therefore it would require either only scaling one axis or using a fractional scale. While this is possible it would not be very effective with a standard box or bilinear filter.
If SSAA was done properly in dolphin RachelB's statement would be correct. This is because SSAA like all forms of AA is supposed to use a filter that is specifically designed to eliminate aliasing. However in our case it doesn't. Ever since neobrain broke it using no SSAA or 4x SSAA results in the exact same filter being used, the only difference is the IR. Since I know RachelB will want confirmation of this here is the relevant code:
https://code.google.com/p/dolphin-emu/source/browse/Source/Plugins/Plugin_VideoDX9/Src/PixelShaderCache.cpp#185
In other words 4xSSAA has exactly the same effect as doubling your IR setting. The 9xSSAA setting however does have its own filter and it is quite effective at eliminating aliasing. Unfortunately the IR increase it produces will obliterate your performance even on the strongest graphics cards when using a high IR setting. However if you don't use a high IR settings with 9xSSAA the filter will produce an extremely blurry image. So as a result I don't recommend using it.
You can force proper SSAA through nvidia inspector (requires an nvidia card) if you know what you're doing but it comes with a nasty performance hit usually hovering around 15-20% even with a strong graphics card. I have no idea if CCCs built in SSAA works with dolphin but I really doubt it since you have to change the compatibility bits in nvidia inspector to get SSAA working there.
Raising dolphins IR whether you do it through the SSAA setting or the IR settings reduces aliasing and sharpens textures. The level of improvement you see from increasing it drops significantly once the actual IR passes your screen resolution but there is still improvement. It's not a perfect solution so like RachelB said without driver forced AA you will still see some aliasing at crazy high IR scales.
I've been pestering neobrain about this for years now to no avail. So I doubt it will be fixed anytime soon. Plus the devs keep talking about eliminating or at least deprecating the d3d9 backend quite seriously.
I think I adequately explained my reasoning.
rpglord Wrote:Why do you say that ? SSAA or full-scene anti-aliasing ( FSAA ) is rendering whole image at higher resolutions, then scaling it down.
If SSAA wasn't broken in dolphin he would be right. SSAA uses specific downscaling filters and resolutions targeted at removing aliasing (usually a box filter with an equal integer scale applied to the base resolution along each axis).
yodenny Wrote:wouldn't all that be unnecessary since you cant see the difference on your monitor i mean doesn't raising the res make it look sharper and less blocky and blurry too a certain point where you cant see a difference i feel like there is no point unless you had a huge tv and wanted to make it fit the screen or correct me if im wrong
isamu Wrote:cough*downsampling*cough
Please read the long post that I quoted above. Both of you.
neobrain Wrote:gz, you just named a feature Dolphin doesn't support
Wut? The only other way to display a higher resolution than your screen resolution is by cropping. Even if you let d3d take care of it for you at the hardware/driver level you're still technically downscaling. Plus you fixed a scaling issue literally a month or two ago!
"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
-Ron Swanson
"I shall be a good politician, even if it kills me. Or if it kills anyone else for that matter. "
-Mark Antony
![[Image: yGa1Z.png]](http://i.imgur.com/yGa1Z.png)
