@khenkel Same behavior in OS 10.11. Vuo 1.2.6 alpha. MPro. Get Mesh Values node is the culprit. Looks like all of the other nodes are working properly.
@khenkel odd. still can’t run the composition when placing the Get Mesh Values node in a composition. @bodysoulspirit Have you attempted to run these updated nodes?
@Bodysoulspirit Have you attempted to run these updated nodes ?
Just tested the Get Mesh Values node and I still get the “There was a problem running this composition” error even with a blank new composition with only that node.
But from the history of the updates on Github it seems several nodes have been updated 2 days ago but not this one (latest update 2 months ago).
I hope the update will also fix the bug when the node is used to retrieve the vertices from Meshes that are being deformed by Add Noise to 3D Object which bugs since 1.2.4 (ran fine in 1.2.3, since the update of the Add Noise To 3D Objects in 1.2.4 to support noise deformation for points perhaps).
Karl, downloaded the latest from Github, replaced the old ones in the user nodes folder, still getting this, anything I would need to delete somewhere ?
Vuo 1.2.6 and a fresh composition with only your get mesh node …
On the errors, it looks like I used the wrong magical incantation to pull mesh data back from the void. It’s fixed, and I’ve updated the node library on Github.
I get the “There was a problem running the composition” error using “Get Mesh Values” in Vuo 1.2.7. @khenkel, does the plugin need to be recompiled for 1.2.7?
@cremaschi, are you sure that Get Mesh Values is the problem? And you have the latest version of co.parabox.nodes.vuonode? I was able to run a small composition containing Get Mesh Values in Vuo 1.2.7.
I notice now that my “get Mesh Values” doesn’t have the “Element assembly method” input, so it should be a previous version.
I investigate deeper how this could happen - an I right downloading the last version from https://github.com/karl-/vuo-nodes/releases/tag/v05-17-2017 as reported in this thread?