jstrecker's picture
@useful design commented on @krezrock's Feature Request, “Export 3D Mesh

wow I disappeared down that rabbit hole for 30 minutes VJ SATOSHI (@vjsatoshi)!

useful design's picture

Thanks Jaymie (@jstrecker) Vuo 1.3 is going to be a mammoth release by the looks of it.

Please consider 'macros' or Group Nodes as a high priority for composition tidiness, and I suspect for Editor run time performance too? To my way of coding it's as important for legibility and coder comfort level as the canvas notes (which will be coming in 1.3 I believe, exciting!).

On the Modules folder, would all Vuo compositions in any given folder share access to the Modules folder? In one sense this is a feature (shared non-global scoping of sub-comps) in another way it's a kinda a potential liability: each Vuo comp (including version saves which is how many of us save our work) with sub-comps would require its own parent folder to maintain single Vuo file scope for the sub compositions.

Team Vuo have probably thought it all through better than me, but that did occur to me as a potential issue. I guess it's better than embedding the sub-comp file in the Vuo file though which was how I kinda assumed it would work.

jstrecker's picture

[@jersmi] Wondering if this will include anything like Kineme Spooky Send/Receive…

No. I think that's covered by another feature request, Super cables.

[Alastair (@usefuldesign)] So have you already implemented global, local and group sub-comps/nodes…

We have not yet implemented the feature request Option to edit sub-composition without affecting other instance.

We have implemented the "global" and "local" levels.

  • If a subcomposition is installed in ~/Library/Application Support/Vuo/Modules or /Library/Application Support/Vuo/Modules, then all compositions can use the subcomposition and all compositions see any changes to it. — same behavior as now
  • If a subcomposition is placed in a Modules folder next to a composition, then only that composition can see the subcomposition. Other versions of the subcomposition can be placed in Modules folders elsewhere in the filesystem and are not affected by the changes to the first one. — new behavior
useful design's picture

This composition is a bit more complex, but it uses position (in polar co-ordinates), velocity and acceleration to move an autonomous car around a track. It just uses Hold Values and calculations to do the maths, most of the other nodes (grey) are additional stuff for screen printing data and converting the polar coordinates to cartesian coordinates. Unfortunately we can't hide them away in macros just yet.

Look for the "tangerine" coloured nodes, they do all the work and there's only three holds and three calculate nodes one of each for each variable (position (θ), Velocity and Acceleration).

You'll need to relink to this image for the car. Or just substitute with a Vuo circle node.

Single car on a track.vuo

useful design's picture

You should be able to get by with just a Hold Value or Hold List node, don't need Select Latest, Changed, Spin Off Event nodes in normal circumstances. The Hold node allows you to do the update on a value using its own contents in the calculation. Typically the update event going to the Hold node (allowing it to update itself) comes from a Build List or Fire Periodically node.

Will have a look at your comps when I get a chance. We're in the same boat I think :-)

Pages

Welcome!

Vuo is more than nodes and cables, it's a community! Feel free to browse or add your voice.

Browse Discussions

Start a Discussion


Browse Feature Requests

Suggest a Feature


Browse the Composition Gallery

Share a Composition


How can I get notifications?

Learn more about the community

Learn more about Vuo

Vuo Announcements

Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.