-
Notifications
You must be signed in to change notification settings - Fork 500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aliasing in magpie. #74
Comments
FSR is just CAS + Upscaling, AA is supposed to be enabled by the application. |
Obviously I understand that, but enabling aa in the game is doing the aa pass on the 1080p image, then after if gets upscaled new aliasing artifacts appear. What I want is an aa pass on the full 4k image. |
The choice of anti-aliasing algorithms is limited as Magpie can only post-process the image. The most ideal algorithm I could find is FXAA, and I will port it in the future. |
Could you also please consider smaa, since that is the method people most commonly use on reshade. |
I will port them both in v0.7 :) |
Is TAA post processing? Unsure, but it'd be a nice option to have <3 |
TAA should be implemented at the driver or engine level, not at the post-processing stage. |
I've ported FXAA and SMAA. Use with caution, they are expensive and don't work as well as native anti-aliasing. |
How do we actually use the ported FXAA and SMAA? is it in the scale config? |
Add this to your ScaleModels.json {
"name": "FSR+FXAA",
"effects": [
{
"effect": "FSR_EASU",
"scale": [ -1, -1 ]
},
{
"effect": "FSR_RCAS",
"sharpness": 0.87
},
{
"effect": "FXAA_Medium"
}
]
},
{
"name": "FXAA+FSR",
"effects": [
{
"effect": "FXAA_Medium"
},
{
"effect": "FSR_EASU",
"scale": [ -1, -1 ]
},
{
"effect": "FSR_RCAS",
"sharpness": 0.87
}
]
}
|
How do I please activate the SMAA at FSR, thank you very much. Pet |
这两种写法除了顺序不同,有什么区别吗 |
先抗锯齿然后缩放更快,哪个效果更好见仁见智。 |
这么说,先锯齿画面会更好? |
按顺序添加效果即可 |
I am wondering if magpie will ever include some sort of anti aliasing pass? FSR can really exaggerate aliasing, so it'd be very nice to see.
The text was updated successfully, but these errors were encountered: