ajm's picture

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • Mac OS 10.10

Steps causing the bug to occur: 

  1. create a 'Fetch Scene' node with the attached model
  2. run the composition and trigger the node

How did the result differ from what you expected?: 

In vuo 1.1.1, the model loads successfully. In 1.2.0 build 6149 (alpha 3), the VuoCompositionLoader crashes. There's a pretty long error message, but here's the important bit:

Application Specific Information:
Assertion failed: (!"Invalid number of components"), function getVector, file /Users/smokris/src/assimp-3.1.1/code/ObjFileParser.cpp, line 261.

Have you found a workaround?: 

nope!

Compositions: 

AttachmentSize
Package icon model.obj_.zip199.4 KB

Comments

Confirmed the crash / failed

smokris's picture
Submitted by
Status:
Waiting for review by Vuo Support Team
»
Accepted

Confirmed the crash / failed assertion. The problem seems to be that typical OBJ files have texture coordinates that look like this:

vt 0.584961 0.493652 0.000000

Whereas your OBJ file has:

vt  0.584961 0.493652 0.000000

Since your mesh has two spaces after the vt, Open Asset Import's parser is thinking you're trying to specify 4-dimensional texture coordinates (where the first coordinate is empty), but it only supports 2D and 3D texture coordinates, so it panics. I'll see if I can make it parse that correctly / not panic.

In the meantime, maybe try exporting your Noesis mesh into a format other than OBJ.

Puzzling that it does work in

smokris's picture
Submitted by

Puzzling that it does work in 1.1.1

Oh, I forgot to mention — that's because Vuo 1.1 uses Open Asset Import version 3.0, and Vuo 1.2.0 uses Open Asset Import 3.1.1. The new version of OAI fixes some bugs and adds some features, like loading modern Blender meshes and Autodesk FBX meshes. (And apparently it adds some new bugs.)

The Open Asset Import developers fixed it in their repository, but they haven't published a new release yet, so I applied their patch, and Vuo can now load your model. That change will make it into our next 1.2.0 alpha release.