Will we get options to insert or innately perform other operations beside masking in the upcoming reworked Mixer?
Personally, I’m more used to having 30 Combine nodes, but I’d give the revamped mixer a try. Although when I tried it in G2, I ran into troubles rather quickly. I realised I really wanted to conduct colour erosion on a part of layers I had (say, the first 4 out of 10), but I couldn’t fit it there. I want to stress that I wanted to erode the combination of the 4 first layers before applying the next ones, not to erode each satmap separately before combining them. And there was also no option to split the mixer in two (layers 1-4 and 5-10). It’s not hard to recreate when your masks are external just plugged into the mixer, but if they all are stored inside it, that would be… inconvenient.
Anyway, the question (or feature request, kind of both) is: will we have options to perform operations such as ColourErosion/Weathering/HSL over some amount of layers within the node itself? Or any way to split the latter to insert them?
Hmm, what would happen to the masks of the first set of layers after a color erosion? Seems like it would be better to use two Mixers if you’re doing any heavy color ops on a set of layers.
Splitting a Mixer is a good idea, though I feel like using the built-in masking options for anything but something quick and dirty isn’t ideal.
I don’t think anything would happen to the masks since they’re derived from the height and it stays unchanged (for operations in question like ColErosion or Weathering, at least).
I feel the same, although it’s advertised as a good way to handle colouring since it keeps the graph tidy and occupies much less RAM.
Personally, I agree, as I mentioned the other day, I’d rather pull a Height mask to plug it into a node than use “mask by height” modifier in half of the cases - just for visual clearance. Same with combines and chain sequencing of those. But I keep an eye out for other ways of doing what I do, maybe they prove useful sometimes. =)