As one of Vuo's developers, I work on Vuo's engine (the thing that makes compositions run), work on nodes, and write documentation. You'll see me on the forums answering people's questions about Vuo.
I enjoy using Vuo to make live music visuals. My hope for Vuo is that it will grow into a community of people of diverse backgrounds and identities making lots of different artistic, useful, unique, goofy, beautiful, crafty, wonderful compositions.
Estoy practicando para ser competente en español. Si publicas en el foro en español, trataré de responder en la misma manera.
Rather than a full recreation of the Get Mesh Values node, could your problem be solved with a hypothetical Transform Point(s) node? The idea would be to feed the points that are currently going into Make Point Mesh, and the transforms that are currently going into Make 3D Object, into the Transform Point(s) node. Does that make sense?
To solve the problem with existing nodes, maybe you could implement the point transformation with Calculate? Not sure if the math would get too complex, better suited to a C node. (With a C node, there might be functions in the Vuo node API that you could take advantage of.)
As of Vuo 2.0.0-beta3, Make Point Mesh has been deprecated and replaced with Make Points Object. Similar for other nodes that deal directly with meshes.
With the changes to the Hold Value node in Vuo 2.0, this exact case of failure to report an error is no longer relevant, so we won't attempt to debug. If there are other cases that come up with non-deprecated nodes in the future, those can go on separate bug reports.