Sure thing! I had plans on turning the engine into a lib that can be accessed by other programs so that people can make use of the 3D routines. (xLIB3D anyone? lolol just kidding )

This will have to happen after i have at least fixed the back-face culling and implemented polygon clipping (which will unfortunately be a little speed hit :S).

This is a demo with 9 cubes (12 polygons each, so 108 triangles for the 'world') all translated into 16-bit space, running at around 17fps with free movement. I have a basic 'level-of-detail' system running where the number of polygons processed for any particular 'model' is dependent on its distance from the camera. This gives a bit of a speed boost and should allow for more complex scenes:

Yeah it should range between 12-16 fps with around 40 triangles, depending on how many vertices there are also (if there are lots of shared vertices then the speed should be better).

Here is an xwing test model that is 34 triangles and runs at ~18.5fps:

Your OBJ file needed to be scaled and the materials needed to be reoganised. I have converted it by hand since i dont have blender but you lost all of your materials in this test.

You can get the .8xp from here: http://www.tr1p1ea.net/files/downloads/

That being said at 254 polygons, its going to be slow! (maybe ... MAYBE 3fps). You should be able to recreate this model with a small fraction of the polygons.

What syntax are you using? Does your model have less than 256 vertices AND less than 256 faces?

Are you able to send me a copy of the model to test?

Well this was more of a hax (actually its only 3 lines of code lol) which piggy backs off the back-face culling code. Pretty much finds the angle between the face and the 'camera' and uses that as an index for the pattern list (where the patterns are black dithered to white).

Not as yet, i have my sights on finishing the polygon clipping code before attempting that. Technically i have a demo with 9 cubes in 3D space where you can fly around and such (at around 17-20fps) which almost fits the part. They are a reasonable distance apart however so the speed comes from LOD techniques. Ill see what i can do in the short-term.

Actually this is a really neat idea for a project. I can see this being extremely valuable for students and enthusiasts alike.

We spell it metre and centre etc, as well as labour and stuff as well. Right now firefox is telling me off for bad spelling .