pbourke's picture

Paul (@pbourke)


2 years ago
2 years ago
2 years ago
pbourke's picture
Paul commented on Paul's Bug Report, “OBJ reading

OK, it seems to be an OBJ size thing. The OBJ file I was using before had 256x128x2 (65536) faces. If I keep dropping the number vertices somewhere between 220x110x2 (48400 faces) and 230x115x2 (52900 faces) it stops working. The attached with 48400 faces works. While I dislike (arbitrary) limits there may be good reasons. But should be documented (sorry if I missed it).

pbourke's picture
Paul posted a new Bug Report, “OBJ reading

OBJ reading


Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 10.12

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

  1. I have an OBJ file that appears correct in MeshLab, Blender, and other packages.
  2. When reading using the Fetch Scene node I seem to only get the 1/2 the model.
  3. I supply a minimal composition that illustrates the problem along with offending OBJ file.

Have you found a workaround?: 




Package icon Archive.zip2.56 MB
pbourke's picture
Paul posted a new Discussion, “Shader parameters

Shader parameters

Is there any way to add parameters as input ports to the shader node? Having fun writing shaders for realtime image mappings but having to hardwire constant parameters is "messy". Yes I know about the method concatenating shader code and external text together outside the shader node, not so elegant either. :-)

pbourke's picture
Paul posted a new Discussion, “Frame rate question
pbourke's picture
Paul commented on bLackburst's Discussion, “Is Vuo ok?

The 12%-88% is clearly problematic. For those of us who clearly see a place for Vuo in our own product offerings the onus is on us to promote Vuo and add license to to our quotations.