Use discard_fragment to fix antialiasing #19
Conversation
In order to indicate to Metal that we don’t want to provide a color for a fragment, we cannot simply set the returned alpha value to 0. If we did, the fragment depth would still be written into the depth buffer, causing any geometry behind the “transparent” point to be obscured. Instead, we need to call a special function that avoids specifying a color value for the fragment entirely: discard_fragment. Calling this function prevents Metal from writing the computed depth and color values of the fragment into the renderbuffer, which allows the scene behind the fragment to show through. Link: http://metalbyexample.com/translucency-and-transparency/
|
Do you have a real example demonstrating the difference? |
|
Here's an example running the nanovg demo: Using You can see how thin lines in the demo (top left) become almost invisible and lines in general look very jagged. You are right that discard_fragment is slower however but it's still cheaper than using multisampling as an alternative to achieve smooth lines. |
|
I just tested both methods on my iMac 5K (Late 2014). I think the difference is negligible. Can you tell which one uses
|
olliwang
force-pushed
the
master
branch
3 times, most recently
from
d3f84a6 to
d0b9aab
Compare
|
@olliwang The trial effect is obviously better than the original:
|
In order to indicate to Metal that we don’t want to provide a color for a fragment, we cannot simply set the returned alpha value to 0. If we did, the fragment depth would still be written into the depth buffer, causing any geometry behind the “transparent” point to be obscured.
Instead, we need to call a special function that avoids specifying a color value for the fragment entirely: discard_fragment. Calling this function prevents Metal from writing the computed depth and color values of the fragment into the renderbuffer, which allows the scene behind the fragment to show through.
Link: http://metalbyexample.com/translucency-and-transparency/