Bodysoulspirit's picture

@cymaspace around a circle check my Eclipse EQ in the Composition Gallery. For 3D however around a sphere, either you would have to create a sphere and use Karl Henkel's Get Mesh Node (see the node gallery and his Github but I'm having a bug with it in the last alpha version 1.2.6 a1), or use a parametric node to create a list of points around a sphere.

Then you have to do the math to make them move, I managed that around the circle in the composition I stated above, the math for 3D should be a bit different.

Bodysoulspirit's picture
@Bodysoulspirit commented on @krezrock's Discussion, “Get Mesh Values Node / Scale

@Azy yup same for me, no more Get Mesh Values since Vuo 1.2.6.a1

Bodysoulspirit's picture
@Bodysoulspirit commented on @Bodysoulspirit's Feature Request, “`Change Items in List` node

Well, out of context right now I'm not sure but, for the example of Xavier's composition, if I had a list of shaders, and I would want a specific range of the shader list to be replaced, how would I do it without ranges ?

And he wanted the items to be replaced not always to be the same but to change.

If for example there was a Replaces Ranges In Lists with drawers, I could make a range from 2-5 for example and fill a 5 shaders list that would place itself at positions 2-5.

How would I be able to choose the position of the items to be replaced ?

Perhaps I overview the simpler method !?

Bodysoulspirit's picture

We're planning to do this as part of another feature request, Get Mesh / Object Vertices.

How could merging the 2 affect the performance versus 2 different nodes ?

I mean I usually use Karl's node to retrieve even moving meshes, like noise distorted. Having a shader retrieval port could lower the performance for detailed objects with many vertices would it not ?

Same for large amount of sub-child shaders ...

Bodysoulspirit's picture

Another piece — "select a bunch of pre-connected nodes, right-click them into a macro and all publishing and cable connections are done for you" — doesn't have a public feature request, but we're already working on it and are planning to release it in Vuo 1.3.

Wow that is amazing Jaymie !!