using Smokris reinterpret you can fill it
Got it! I forgot about that one. I do have a question about Smokris'
Reinterpret 3D Object and depth stacking order in combination with
Combine 3D Objects. In this comp I have the fill (reinterpreted) z translation set to be below the stroke, but
Combine 3D Objects stacking order appears to override it? Any clarification?
And that's a nice example you put up in the Composition Gallery!
Alastair (@usefuldesign) I'm quite sure you understand the concept here, see attached comp.
Make Parametric Points is simply feeding the same point data to
Make Line Strip Mesh and
Make Point Mesh to show both on screen. This is like Kineme GL Tools in QC, feeding the same point data to a gl line strip and gl point to see lines and points on the screen at the same time.
In this case I'm just finessing the point size to try and get it to match line width exactly, essentially making a round cap on a stroke, in Illustrator parlance. It's remarkably a pita, thus the formula in
Adjust Point Size (Calculate), providing a different adjustment for each number of polygon sides (got lazy after 8 sides, and it might behave differently for different screen sizes, too):
@jersmi don't know if you mean you wanted to fill the composition you shared, but using Smokris reinterpret you can fill it, but straight edges, without the round point edges (except for the 2 points on start).
For the oval shaded points size, I don't know ! But what I don't understand is that using the same color, the lines and ovals don't have the same color (you'll see it better in this modified composition toggling between 2 and 30 points, on 2 points, the left oval point clearly has not the same color, although the line is unlit shaded and the oval shader ignores lightning).
Thanks @jersmi, had a quick look and I'm not sure what you are doing here, I'll need more time to figure it out. Could you give a quick run through the maths and logic of what it's doing to make it easier for me please?
I went looking for a quad patch, because I want to do a limited application where I have to lines/curves on a graph and I want to fill the region between them. I have regular X positions/intervals and variable Y values. So I could do it pretty easily iterating through two lists concurrently and making a set of quads, one per pair of points. But I could only find a Quad layer, I'm not sure if that's that way to go, might have some penalty in making a bunch of layers when I don't need them. Using @Bodysoulspirit's method I can substituent Y values into a 3D square of columns using similar thing to what he did in the example above.
Quad Family patch and a few lines of JS and I'd have it nailed in QC, but the QC smooth curve plug-in by Kineme isn't functional enough for me, it comes with features (kinks/wonks that shouldn't be there and aren't in Vuo curves) I can't accept. I'd like to do in Vuo anyhow, it's the future.
Yeah, I'd really like to fill the polygons in this comp. Btw, @Bodysoulspirit, that comp is awesome! Your approaches to using list tools are inspiring.
I'll throw this in as an obvious workaround in some cases for a rounded cap -- feed a
Make Point Mesh with
Make Oval Shader the same points as
Make Line Strip Mesh. I'd love for someone to tell me how to line them up precisely, because the entire point mesh appears a bit distorted, scale of X/Y axes appear slightly different for me. If you look at
Calculate Point Size, you'll see a formula that reflects how much I am fiddling with the numbers to compensate, still not very good, imo. This was testing for larger line widths at full screen. With smaller line widths, or if you want the points to be conspicuous, then it might be a-ok.
Another relevant FR is Shortcuts for switching between Vuo Editor and VuoCompositionLoader.
There might be another FR which is to have the Run button changed to Run/View button (IIRC something by @cwright) and you can press it even when the comp is running. This would negate need for this FR. Options as I see it:
- Leave it as Run button but make it clickable during running state to bring view app to front and in focus;
- Have it as Run button and change it to Restart button (so still active but different purpose) when the composition is running. This doesn't solve the bring comp to front and focus issue;
- Same as above but with a separate View Button that is greyed out when in 'not running' state to bring composition windows to the front and in focus;
- Have it as a Run/Stop button so clicking it when composition is running stops the composition. Also could add an Option mode where mouse click plus "option" key Views the composition. Right-mouse clicking could give you a context menu to Restart the composition (if the toolbar becomes customisable that will block any right clicking of toolbar buttons same for command + click which moves buttons on toolbar);
- QC style: Have a Run/View composition button. The Run button changes to View when running. Possibly Command clicking it stops the composition.
Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.