Re: [Bf-committers] Proposal: Add scale operation to the Pixelate Node

That is exactly what I find should be correct. On Mon, Jun 6, 2016 at 3:26 PM, gandalf3 wrote: > I'm not sure this would be a "hard coded coupling" in the usual sense > (which I agree is something best avoided). > As I understand it, this node basically tells subsequent scale

Re: [Bf-committers] Proposal: Add scale operation to the Pixelate Node

I'm not sure this would be a "hard coded coupling" in the usual sense (which I agree is something best avoided). As I understand it, this node basically tells subsequent scale nodes to use nearest interpolation. It does nothing itself to modify the data. Afaik no other node changes the behavior

Re: [Bf-committers] Proposal: Add scale operation to the Pixelate Node

The real problem is not having good education about the tool. When a new tool like this is added, it could be said in the cool new features release that it must be combined with the other node. That should give enough people a heads up that the rest will catch on. Of course it must also be in the

Re: [Bf-committers] Proposal: Add scale operation to the Pixelate Node

The coupling of nodes hard coded is perhaps one of the most destructive paths for Blender. Instead, perhaps effort should be put into providing a means to import and export node trees and groups as singular nodes? The greenscreen coupled up node from hell is an example of a worst case, and it

[Bf-committers] Proposal: Add scale operation to the Pixelate Node

Currently, the Pixelate Node [1] is difficult for new users to know how to use because they do not know that they need to add a scale node before it inorder to get desired results. To easily fix this I purpose that a scale operator is added to the node making it easier to use. - Aaron Carlisle