do you guys/gals try and union (join) all parts (meshes otehrwise joined as sibling or child meshes) of a model that share a common texture together, as a single part (one mesh)...
i ask this because of a recent problem with 3Impact, that made me realize the solution was to join all parts sharing the same texture and reduce the parts count...
does this help when rendering a game?
thx
--Mike
Yes- as in blitz this reduces the total surface count, (Usually!)
thx Cyg... sounds right...
--Mike
I could be wrong but you only have more surfaces if you add more surfaces (textures).
So for example if you have a car that included the 4 wheels in the mesh that share a single texture you'll still be on one surface.
You can set the wheels on bones and loadanimmesh in blitz, use find child to get the wheels and you'll have a multi part mesh with independant bits but on one surface...
That's how I read it.
what i had Rob, for example... was a ladder, with each of the rungs and the two side poles as separate meshes... joined as siblings in TrueSpace...
when i loaded em into 3Impact's new code, that now enables multitextured meshes to be loaded (it didn't before, go figure :) ), it seemed to take forever before the loading screen dissapeared...
then it dawned on me that my model might be partly at fault... so i took that ladder (and a few otehr things) and unioned all the rungs and support poles into a single mesh...
the model now loaded in 16 seconds as opposed to 98 previosuly... and the part count the engine had to split it up into was reduced from 168 to 35...
that's why i was wondering if it would make a difference in Blitz... even though the circumstances aren't the same...
--Mike
Yes. If possible, I also try to generate triangle strips.