Fri, Mar 17
Wed, Mar 8
Fri, Mar 3
But if the node is broken because it is incomplete? It is actually only usable if it is not animated.
Eeeeh… this sounds much more like a feature request than a bug report to me, @Sergey Sharybin (sergey)?
Feb 23 2017
Grrrr… using same var for two different things… grrrrrrrrr… developers should know better…
Feb 20 2017
Feb 9 2017
Sorry, I've been away and haven't had time to update this. I'm attaching a file demonstrating the problem.
Report has not been reacted on for 7 days, closing due to bug tracker policy.
Feb 2 2017
Thanks for the report, please provide a blend file for testing.
Feb 1 2017
Jan 26 2017
Rebased on the latest master.
Jan 16 2017
@Michael P. (forest-house) You forgot to set parameters of the Dilate/Erode Node. Setting the Distance -1 removes the artifact.
Jan 15 2017
@Shinsuke Irie (irie) these are greate improvements to the node.
Good news! This issue is already fixed! If you want the fix head over to https://builder.blender.org/download/ and grab a nightly, otherwise this will be fix in the next official version!
Jan 13 2017
- Forgot to update extern/smaa_areatex/README.blender
Also update the test build for Windows 64bit.
- Improve render quality
- Fix several render issues
- Remove unimportant options such as Predicated thresholding
- Remove "Blending Weights" output that is useful only for debugging
- Rename "Depth" to "Value"
- Modify UI texts
- Move smaa_areatex.cpp to extern/smaa_areatex/
- Style cleanup
- Update copyright year
Jan 6 2017
I tested this new node for some cases, and I'm really impressed.
Dec 20 2016
I can confirm. I will try to fix this myself.
Dec 18 2016
Dec 16 2016
Style and comment fixes, remove own utility functions
Dec 15 2016
Here is a test build for Windows 64bit.
Looks neat! I'd be happy to test it on some vfx type things.
Dec 14 2016
Dec 13 2016
For such patches it's always a good idea to include render tests demonstrating the results. How does this compares to existing AA operation? If it's considered more superior quality, can existing AA operation be switched to this code?
Dec 12 2016
Dec 9 2016
happy to - and already did. :)
Hrm, yeah that's confusing.
Masks are stored in the normalized space (coordinates 0 to 1) which are then mapped to the "canvas". By default, we map them to scene resolution, so when you do alpha-over or things like that in compo you always have same result regardless of render percentage.
Dec 7 2016
Here, the problem is not the mask.
It is the image.
Nov 26 2016
Just curious why this would be the intended behavior? Isn't the render percentage only supposed to modify the final output? By having it affect the way the compositor works, you have to adjust your mask nodes every time you adjust the final render output. This seems cumbersome and unintuitive.
Hmm, this is intended behavior but for example, the mask node has the Size property to change how this works.
Nov 25 2016
if the animated gif won't load, check out the gif here..