I bet you might need to take the composition, delete the old parabox nodes, and then swap in new ones from the node library. Not sure if it will help, but I’ve had something similar happen, and that worked.
BTW, thanks again for this node set, Karl!!! It’s really great.
You (or anyone for that matter) might be interested in some of the things going on in this editor; just saw it a couple of days ago and was impressed at some of the ideas for GUI objects that pop up to make enhance editing.
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 …
@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?