EricBall's Tech Projects

I wrote an OBJ converter back in 2010 to import models into our spacecraft design suite. You can see the results of importing a shuttle model on our homepage. The software originally ran under X11, I was hired on to do the Windows port. Nathan did some freelance work us, he did the button and icon graphics for the port.

 

Might you have used the wrong notation for comments in the OBJ file? I just checked the shuttle OBJ and MTL files I used to test my routines and all the comments start with #. That follows what I see at wikipedia.

Hi Darrell,

 

Here's the sample I used (which fails):

 

# WaveFront .obj file - a single square based pyramid

# Start a new group:

g SquareBasedPyramid

# List of vertices:

v -0.5 0 0.5 # Front left.

v 0.5 0 0.5 # Front right.

v 0.5 0 -0.5 # Back right

v -0.5 0 -0.5 # Back left.

v 0 1 0 # Top point (top of pyramid).

# List of faces:

f 4 3 2 1 # Square base (note: normals are placed anti-clockwise).

f 1 2 5 # Triangle on front.

f 3 4 5 # Triangle on back.

f 4 1 5 # Triangle on left side.

f 2 3 5 # Triangle on right side.

Unity doesn't handle the in-line comments like # Front left. Remove them and it works fine.

I used google sketchup to make simple shapes like mazes and imported to unity a few years ago(maybe it was blender?) However, they sold it to Trimble a while back and I don't know what kind of files the free version will output.

I didn't notice that, though it does match what Wiki has about the OBJ file:

Lines beginning with a hash character (#) are comments.

Just booted up the work machine and all the comments are on lines by themselves.

Wiki does show inline comments in the MTL file, though the files I have are on lines by themselves like in the OBJ files.

Unfortunately, the SketchUp Make license is for non-commercial use only. (Not that I have any plans to make money, but Blender doesn't have that restriction.)