The problem here is the order in which the objects are rendered. In Vuo, depth writing and testing are always enabled. In the right window of your screenshot, it looks like the “Top” image is being drawn first. For each pixel in the “Top” image, if the alpha is 1/255 or greater, it writes to the depth buffer. Next, it draws the “Bottom” image. Since the antialiased edges of “Top” already wrote to the depth buffer, it doesn’t draw “Bottom” at all for those pixels, resulting in a hard, unblended edge.
Ultimately (a few 0.5.x releases from now), objects will be rendered back-to-front automatically (“Painter’s Algorithm”), and the solution for 2D compositing will be this:
use the Z coordinate to control the order in which objects render (analogous to “Render Layer” in QC)
configure the scene to render with orthographic projection (so that the Z value doesn’t affect the size of the layers)
@mnstri — For 2D compositing like this, we came up with a simpler solution. In Vuo 0.5.4, we added a new “Layers” node set, which draws 2D image layers in the order you specify (whereas the Scene node set, in a future release, will be drawing objects ordered by distance from the camera).
I modified your composition to use the new Layers node set, and attached it to this bug report (“UglyBordersFixed.vuo”).
