jstrecker's picture

Jaymie (@jstrecker)


  • Vuo Founder
  • Team Vuo
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)!

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
jstrecker's picture

Alastair (@usefuldesign), you might have gotten your problem solved on another thread, but for anyone else with a similar question…

In this demo composition Getting the next item in a list in a process list cycle v 1.1.vuo I'm not getting the Process List node to cycle the list as I think it should.

To cycle the way you described, I would actually recommend using Take from List and Add List:

But as a mental exercise, here is how you could do it with Build List:

All values except for X (r), which is a constant for all cars, are to be recalculated every frame.

You may want to take a look at Magneson (@MartinusMagneson)'s PetriDish.vuo on this thread.

jstrecker's picture

Magneson (@MartinusMagneson), thanks for your helpful answer.

Alastair (@usefuldesign), I want to bring this discussion back in a constructive direction. I understand you're frustrated and I agree that Build List and Process List can be tricky to get working for non-trivial situations. A lot of people have had the similar questions. If you look for past discussions on Build List and Process List, you'll see several times where someone shared their composition and asked how to get it working, and with the community's help they were able to. These nodes are admittedly not the easiest to use, but they do get the job done if you're willing to have the patience, and they're hopefully better than nothing. Please bear with us until we're able to implement a more robust method of iteration.

While I and the rest of Team Vuo welcome suggestions on how to improve Vuo, or even measured comments on what you found difficult to learn, your recent comment comes across to me more as venting. I really am sorry that Vuo is falling short here. But that kind of comment is just not constructive or helpful toward solving the problem.

I think you're on the right track to be using Display Console Window in your debugging attempts. Without seeing the composition, I'm not sure why it's not working as you expect. Maybe if you post your composition someone can help.