Trollpaxton wrote:
grin wrote:
What I meant was obtaining in the created obj a group layout that combines body groups.
Unfortunately that isn't as easy as it sounds. Right now the obj importer/exporter assumes all the vertices are going to be in the same order as they are in the file, but in order to make a group that is made of multiple geosets that are scattered throughout the file I'd have to reorder the vertices.
grin wrote:
In other words, obtain directly in the output .obj what you get when you uncheck body geosets while importing into max (which as far as I know renders the max processed .obj not reinjectable as it doesn't contain the same grouping info as the original).
Yeah, that messes everything up, you definitely don't want to do that.
Why all these limitations? Here is the problem: vertices in M2 files have a lot of data associated with them (things like bone weights) that can't be stored in an OBJ file. In neither file format do vertices have a unique identifier. So, the only way to find out which vertex is which so that the extra data can be reassigned to the right vertex when importing an OBJ is if the vertices are all listed in the exact same order in both files.
grin wrote:
Then you can modify multiple element meshes at the same time...
Can't that be done already? What I do is use the Layers window to hide everything but the body, and that's pretty much it.

Isn"t that what you are trying to do? Or am I missing something?
pls can you give me this programm from the screenie
sry for my english