Sequential Filter Render

That's one of the distinct benefits of the competitor's product ... being able to group nodes and save them. Then just hook up groups to do what you'd like to do.

Betis, I think this is feasible with the batch renderer.

One of my wishes reminds of this, and that was to have a "Result component" with an output.

I use my "wet stones"-filter as an example, you first render the stones, with height mapping and all, then you use that complete output, and apply a water surface with a new height map, over that first render. I can see multitudes of uses for this, being able to create "meta filters" that is either a chain of filters or filters that internally have output steps passed to the next chain.

OK, nothing you run on the average single core machine, but on the other hand, this might prove faster as you can avoid some techniques used today to create something similar but is very cycles-consuming.

Would this be something to include in version 4?

Two filters that take 20 and 30 seconds, when combined into one filter take 150. In this case the batch processing is/would be helpful.

Also to have an evaluation block to freeze cache at certain components, and have a reevaluate button, would be time saving.

To be able to switch from Surface to Simple filter type for a faster 'preview', and to use Surface->Simple, as Betis mentions for post processing, would be great.

Maybe these issues are already addressed in the 'loop component' and 'script component' threads?