Jump to content
  • Advertisement
Sign in to follow this  
haxpor_2

Suggestion on reducing jaggies edge for particular angle.

This topic is 2143 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I used DLAA over my deferred shading scene.
Even I applied the AA on the scene, there's still some jaggies on the far sight over the run way (white line in parallel). You can see it in the bottom image. Please click on the image for the full size.

GNObg.jpg

The run way itself is as below.

rFDww.jpg

It's clearly that there's no problem at all for some angles the camera's looking, but the angle that users will be mostly looked at is the same as the first image.

Any suggestion on ways to reduce those unpleasant glitches is very welcome! Edited by haxpor_2

Share this post


Link to post
Share on other sites
Advertisement
FXAA, MLAA or similar algorithms won't solve this kind of temporal aliasing of small details.

You can:
1. Use temporal AA (subpixel jitter camera every frame + blend current frame with previous). There is more info about it in crysis 2 presentations. This method has it's artifacts, especially when you target 30fps.
2. Use MSAA, FSAA or similar, which are quite GPU heavy.
3. Let the texture filtering handle it - draw big chunks of terrain with final mip-mapped texture (which contains already composed grass, asphalt, run way etc.). It will look nice, but also you will loose some runtime terrain composition flexibility.

Share this post


Link to post
Share on other sites
I'm now trying to finish implementing FXAA following http://stackoverflow.com/questions/7680073/examples-for-using-nvidia-fxaa-shader-antialiasing-in-xna-4-0-winforms/7735547#7735547, but I have some problems possibly about blending result from buffers that i'm trying to solve.

The current result is here.

lXrhU.jpg

I believe I will try solutions from KriScg after this finishes. The result so far seems not to be better than DLAA (I understand there might be some different in environment of implementation). Although modern titles use FXAA method quite more often, I believe they combine with another methods for different distance to camera or some other settings.

If I try out KriScg's solution, or make any progress I will let you know.

Thanks again for your help!

Share this post


Link to post
Share on other sites
FXAA will not help with bad filtering. Are you using anisotropic filtering? ... if not then you definitely should as there is quite considerable anisotropy on the horizon.

Share this post


Link to post
Share on other sites
Guy, some heads up!

I've tested with FXAA 3.11 on Timothy Blog, and it's kind of similar result to DLAA (originally I have) but with less blur.
Now, I'm currently trying to make SMAA in order to resolve temporal aliasing. In fact, I'm trying for several days now.
Please see more info here http://forums.create.msdn.com/forums/t/106646.aspx.

Thanks!

Share this post


Link to post
Share on other sites
[color=#526569][font=Verdana, Arial, Helvetica, sans-serif]

[background=rgb(244, 247, 245)]Heads up guys, I'm able to make the result from the first pass working. The problem seems to come from Matching between vertex and pixel shader ([/background]

[/font]http://www.gamedev.net/topic/434661-fx-hlsl--semantics-problem/[color=#526569][font=Verdana, Arial, Helvetica, sans-serif]

[background=rgb(244, 247, 245)]), you can see the result for the first pass at my blog here ([/background]

[/font]http://haxpor.org/post/26757501785/after-several-days-sitting-duck-in-front-of[color=#526569][font=Verdana, Arial, Helvetica, sans-serif]

[background=rgb(244, 247, 245)]).[/background]

[/font]

[color=#526569][font=Verdana, Arial, Helvetica, sans-serif]

So currently I'm trying to make the second pass works. But after testings, it seems like second pass didn't do anything. I got not-similar result to the reference demo in https://github.com/iryoku/smaa, and always got the result just seen in the first pass. The second pass involves using stencil buffer as well and I'm trying to figure out what's the root cause.

[/font]

[color=#526569][font=Verdana, Arial, Helvetica, sans-serif]

Sorry for my quick heads up, I have to get it done quickly as possible. I believe it's because the hlsl syntax and its feature as of xna 3.1 is not so compatible with the source code seen in the link as there, it targets more on directx 10.

[/font]

[color=#526569][font=Verdana, Arial, Helvetica, sans-serif]

Any suggestions would be appreciated.

[/font]

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!