HOME | DD

Description
I don't think I'll live long enough to list all the troubles I had while converting that bike, so here's the exact number of problems: 1,061,201. Yes, I had one million sixty-one thousand two hundred and one problems, 374,002 of which were vertices, and 687,199 were faces.

The model was made in Sketchup, which is known to be incredibly good at compressing the model and textures, but at the same time incredibly crappy when imported to Max. Some faces were flipped, some where seemingly non-existent, and on one part, there were faces between all possible permutations of the vertices. There were also hundreds of rubber thingies on the tires, each consisting of 32 polygons. Overall there were about six thousand objects.
All in all, I had to do a lot of merging and reductions - but it was still not enough! I had to export the model in 8 parts (to keep below 65536 vertices and faces) and merge it in PMX, which is, apparently, terrible at handling memory. Storing all undo moves in the memory, accompanied by memory leakages, is more than enough to cause a memory overload for a 32-bit application. It also lagged terribly.

The result could be better, but I'm never going to touch that thing again.

Description
I don't think I'll live long enough to list all the troubles I had while converting that bike, so here's the exact number of problems: 1,061,201. Yes, I had one million sixty-one thousand two hundred and one problems, 374,002 of which were vertices, and 687,199 were faces.

The model was made in Sketchup, which is known to be incredibly good at compressing the model and textures, but at the same time incredibly crappy when imported to Max. Some faces were flipped, some where seemingly non-existent, and on one part, there were faces between all possible permutations of the vertices. There were also hundreds of rubber thingies on the tires, each consisting of 32 polygons. Overall there were about six thousand objects.
All in all, I had to do a lot of merging and reductions - but it was still not enough! I had to export the model in 8 parts (to keep below 65536 vertices and faces) and merge it in PMX, which is, apparently, terrible at handling memory. Storing all undo moves in the memory, accompanied by memory leakages, is more than enough to cause a memory overload for a 32-bit application. It also lagged terribly.

The result could be better, but I'm never going to touch that thing again.