Fri, May 19
Brought behavior back to how it was before. But i find this all weak, and some cleaner design (which follows artists' expectations instead of dictating them how to use something) is really needed in compositor.
@Aaron Carlisle (Blendify), so "squished" part i think we can investigate (as in "resolution" if you wish).
Thu, May 18
@Sergey Sharybin (sergey) but why did it work in 2.77?
Scaling down can not work within the current compositor design. Fixing this issue would mean changing the design completely, which is out of the scope of the bug tracker.
Wed, May 17
Tue, May 16
This is a known limitation. Output node doesn't know of the nature of the data and assumes this is image pixels.
Anti-aliasing happens from the outside side of the spline, which is actually happened to be an inner side of your "buggy" spline. Just switch direction of the spline and anti-alias will work fine.
Mon, May 15
This was a poorly implemented feature which was not thread-safe and was causing lots of crashes. It was disabled in the code, but interface part remained. Thus happened 3 years ago, so think it's safe to let this feature to disappear from the interface.
Unfortunately, this is a limitation of the current compositor design, which has half-finished canvas awareness. The following internal issues are happening:
Sun, May 14
Sun, Apr 30
I see what you want to achieve now. Afraid you'll need to follow some workaround like @ronan ducluzeau (zeauro) suggests with the current BI design.
Sat, Apr 29
Fri, Apr 28
You can add a boolean modifier to your UpperCube.
If you would not specify mask at all you'll have the result you're looking for here.
I tried this, but it gives me wrong result. Upper cube's outline doesn't follow lower cube contour.
Thanks for the report, but the code is working as it was designed to (and here i don't mean it is not confusing for artists). The Edge enhance pass is using Z-pass calculated for objects from current render layer objects and objects which are set by Z-pass mask layers. So adding Z-pass mask does not mean you exclude that unselected layers from edge enhancement.
Final render and preview are having decoupled render border settings. This way you can keep tweaking some specific area in the compo and hit F12 to have a better idea of what's happening on the frame. There is currently no way to automatically inform compositor that some render result was cropped and that it should not calculate anything outside of that region.
Thu, Apr 27
Mon, Apr 24
Apr 18 2017
so maybe : diff
(same issue in Directional Blur)
Apr 16 2017
@Dwight Martin (dwightmartin) thank you for your concerns, we have been a little short-handed as far a people to work on the bug tracker but after your comment, I went back and looked and the different Blender versions and also have a few questions. @Jeroen Bakker (jbakker) I can you, as the compositing expert, explain your reasoning a bit more? I went back and checked Blender versions 2.73a to master and found the issue only started appearing after 2.77. I also checked the release logs (both user and bug fixes and did not see anything that obvious as an intended change) I am also CC'ing @Sergey Sharybin (sergey) as most of the changes done in this time period were your own.
Apr 15 2017
Closing because this is intended behavior as pointed out by @Jeroen Bakker (jbakker)
Apr 13 2017
IIRC - the bug is that the value is zero in the first place.
Apr 8 2017
Can someone confirm this bug?
Apr 5 2017
Apr 3 2017
Change of behaviour is probably relative to a fix in compositor.
Apr 2 2017
Any chance to get this into the 2.79 release?
Can this be used to refine every alpha channel edge, i.e. image with an alpha channel, or just objects with a material id?
Mar 28 2017
If that's the case, okay. But, this was possible in version 2.73a. I don't know when this changed. But here's a tutorial where it was still working: https://www.youtube.com/watch?v=Ra-E0JVkXEI