(04-24-2021, 04:33 PM)denzjos Wrote: I think I get it now (the workflow I mean). I always want to know the thinking behind a workflow, I don't like the click, click, click,... to become a result. I know, it's always difficult to explain a workflow in little text. @Ofnuts, it would be nice to get the object smaller and then become bigger depending the position on a path. In this case, when the fly disappear behind the tree. Just a thought...
We would have to find a usable way where you can express the size change as a function of the position on the path.
Another solution is to split your path into a few sections and run OBSOP on each after changing the brush size, accumulating the layers in the same image. Of course this could change the spacing a bit between the sections, but in your case giving a smaller spacing for the "far" sections would also be necessary. The only extra option you could need is a way to tell OBSOP to not stroke the last element of a path section (but you can just as well delete the last layer produced each time).
You also implicitly volunteered to test if the Fade ➤ Size dynamics mapping is still usable with OBSOP
(no promises, if it still works it's sheer luck for the time being)