> > I don't know Vipr...

> > Joystick support?
> > 3D acceleration?
> > Game engine?

> > Seems to me you're loosing focus !:rolleyes:
> > You were programming a converter tool, no?

> > Why not just make a SIMPLE tool that converts a 3ds model into a vxl and runs native under Windows?
> > Nothing more, nothing less...

> hehe yeh i agree just a prog 2 convert 3ds 2 vxl in a fast time.. we dont need special features just summit 2 do it and fast and not have many errors not that i have come across many.. just 1. the viewer for it would be cool if it worked..

the viewer is essential to ensure my program properly loaded the models. looking at the voxel is not clear enough. One of the most common errors is that some models have the meshes all in the wrong place. it's absolutely killing me that i cannot figure out why this is happening. also some models have whole meshes with all inverted faces or just some triangles inverted. also you need to make sure the model is facing the right way and because Will's and Olaf's programs display the vehicles flipped, you really need my program to help you see which way they are actually orientated.

btw what do you think of the speed of my converter? is it unbearable? is it much slower than Flyby's new voxelizer. there's probably something i can do to speed up my program if you don't use textures. i noticed you hardly use textures WeeRaby2k. anyway my program currently assumes people use textures all over the models so it does the color conversion to 8bit for every voxel block. whereas if you were just using material's overall colors then i could program it to do the conversion once and just reuse that color index for all faces using that material.