jstrecker's picture

Jaymie (@jstrecker)


  • Vuo Founder
  • Team Vuo
jstrecker's picture
@jstrecker commented on @Bodysoulspirit's Feature Request, “`Change Items in List` node

Oh, I was thinking the hypothetical Change Item Ranges in List would have a Ranges port that is a list of ranges, like Get Item Ranges from List. Having a singular Range port would not be as complex. Still, you'd have to do a little math to make sure you're feeding in the desired number of replacement items. (The range 2-5 would take 4 items, not 5.)

You can generate a list of positions in a range currently using Make Points along Line. It would be cool if we also had a node to more straightforwardly generate integer sequences.

jstrecker's picture
@jstrecker commented on @marioepsley's Bug Report, “texture mapping a .ply

Thanks for sharing the non-working .ply. This console message gave a clue as to why textures aren't applying correctly:

4/18/17 10:43:54.676 AM VuoComposition-HQrO63[33534]: VuoSceneObjectGet.c:240 convertAINodesToVuoSceneObjectsRecursively()  Warning: Mesh '' is missing tangents, bitangents, texture coordinates.  These channels will be automatically generated, but lighting and 3D object filters may not work correctly.

Actually the .ply file does have texture coordinates (as seen in MeshLab), but for some reason the library that Vuo uses to import meshes (Open Asset Import) seems to be ignoring them — so I've converted your question to a bug report.

When texture coordinates are missing, Vuo tries to generate some, so that shaders will at least partially work. But because this scene's texture map is complicated/piecemeal, the generated texture coordinates aren't close to what the mesh author intended.

jstrecker's picture
@jstrecker commented on @Kewl's Feature Request, “Merge WXYZ Lists

@Kewl, would Lists within lists do what you need? If not, please create a feature request, ideally with some info about how you plan to use it.

jstrecker's picture
@jstrecker commented on @bLackburst's Bug Report, “Auto type-convertor bug

@Bodysoulspirit's explanation is correct. Still, as @bLackburst pointed out, the fact that the Transform -> Rotation type converter is automatically chosen there can easily to mistakes when building a composition, so it could be considered a usability bug. Scheduled for work.

jstrecker's picture

We're planning to provide both a Get 3D Mesh Object Info that outputs the shader (among other things) and a Get Mesh Info node that outputs the full mesh data (vertices, etc.). Get Mesh Info would take more time to execute, since it would have to download the vertices and stuff from the GPU and process them. But you wouldn't need to do that if you were just grabbing the shader. You would use Get 3D Mesh Object Info.