Using my telekinetic remote debugging abilities .....

I don't know. Having a composition + file makes this a zillion times easier.

I'm going to guess that the object's too big and gets clipped (try enabling the Normalize input), or it's too small to see (try enabling Normalize). Or it could just be oddly translated so as to be invisible -- in that case, just enabling Center will do. (Normalize implies Center, by the way).

If you mouse over the object output port, does it tell you vertex/face/normal counts? If those are non-zero, the object is loaded and ready for display.

Also, Stop Using OBJ. Holy crap. The format is junk, and it takes forever to load.

Im sorry chris... Here comes the files.

Ok so you say that the obj format is crap, im new to the format and didnt know. which format do you recommend feeding the object loader?

thanks for taking your time. niklas

It's ok -- it's just hard to track down when things don't work without something to test with :)

OBJ's ok usually, but in Kineme3D the loader is very very slow, and it doesn't always do the right thing. FBX is a much better-supported format.

Checking out the files you posted -- Looks like the obj is incomplete, or FBX can't parse it properly -- it simply contains a a few vertices, and then "l" data (not sure what that is -- lines perhaps?). typically you need "f" data (faces) for anything useful in Kineme3D.

I'm getting the same results here... seems like the file is "malformed". Can you get it to open with anything else?

it is malformed. If you open it in TextEdit, you can see the vertices (v blah blah blah) data is ok, but there's no face data (would look like "f blah blah blah" or "f blah/blah/blah blah/blah/blah" etc). Instead, there are lines like this: "l blah blah blah blah blah blah blah", which definitely isn't 3d face data. Opening it with FBX SDK's demo "load everything" sample, it just draws a circular line segment, no faces.

Just downloaded your files & converted your .obj in autodesk to .fbx & also tried looking at it in Photoshop.

It is a blank empty space all around.

Nothing to see, nothing to render.

When viewed in a plain text editor it reads:-

joe.obj created by IVREAD.

Original data in diamond.obj

g Object001

v 0.000000E+00 0.000000E+00 78.0000 v 45.0000 45.0000 0.000000E+00 v 45.0000 -45.0000 0.000000E+00 v -45.0000 -45.0000 0.000000E+00 v -45.0000 45.0000 0.000000E+00 v 0.000000E+00 0.000000E+00 -78.0000

l 1 2 6 4 1 l 1 5 6 3 1 l 2 3 4 5 2 so obviously something is there.

Question is to convert it, and by the way, the .fbx didn't cut it neither as binary , nor as ASCII.

Slightly puzzling indeed.

Oh, and trying out other .obj files resulted in some considerable crunch within Quartz Composer - needed to be Force Quit.

Almost any other model type worked AOK though.

Clearly something to do with the means by which the .obj is formatted and if not formatted and marked up right, it probably won't convert via FBX convertor correctly.

Interseting problem.

Use another diamond 3D in a different file format different would be my initial workaround, but it would be cool to know how to turn otherwise good .obj files into loadable items without conversions taking place, although sorting that out so they don't churn and burn would be cool too.

I'm just not there right now :-)

Sorry.

It doesn't work as FBX either Because There Isn't Any Face Data. Kineme3D Only deals with Faces (triangular faces, at that). Not lines. Not points. Not teapots. Not Nurbs (though it tries to convert these to faces if necessary). This model only contains line segments, so there's not face data for kineme3D to extract, regardless of format (fbx, dae, dxf, 3ds, it's still line segments, and nothing will change that).

If it was to load properly, it would only render a wireframe -- if that's all you want, kineme3D is overkill. If you wanted a faceted diamond, this model will not provide that.