I'm working on a little helper app that should make it a more easy to work on the Poser model and especially if doing it in Wings3D.

Everything went well untill all my apps went nuts on TheGirl, after several hours I did realise that she is not split up in parts as all other models i know of but rather a single part.

What is the god and bad with such a construction?

As an example, how do I make morphs. Normaly I would load the model from the geometry folder and create a morph, save the part(s) and import as a morph(s). But how should I work on a model such as this?

Message edited on: 12/14/2004 17:17

I find the best way is to export the figure from the zero position from Poser as an obj file. Make sure the hips and body are both zeroed on all axis and use the joint window to zero all joints. You will need to turn off IK. When you export tick the box that name the individual parts and do not weld the seams. The mtl file seems to add a number to each material name but you can edit that later. I find I need to scale it up by 10 when importing into Wings. Hope that helps

She is grouped differently. The right breast is the nipple and so the chest is grouped differnt too. Why, I don't know. Maybe the JP's work better that way. I do the same with the export except I scale at 20 for defalt Import and .05 export. Higher if needed. Geep has a tut with the varied scales. I also found I get double groups in wings. I delet the first part name, the second one seems to be the one to use. Don't ask me why this is happening. But I can create a morph and import it into Poser just fine. Maybe I should get the new version of wings? LOL.

OK. I usually work from the .obj file rather than export in order to be sure that I got the model in is original position. After reading your posts I suppose that I have to use the export for this model in order to get it split up in parts. What I was confused about is if applying a morph made for a part was possible to apply to a model that not really is made of parts. The appearance of several parts with the same name is probably because Wings goes nut on the fact that group and material info in the file (at least the original .obj file) is least to say unstructured. After running the model trough my app it's sorted in a nice way with also means that I don't have that problem with the model when imported to Wings. What concerned me when working on it in my app was that Wings added thousands of vertices to the model when loaded and when I tried to weld the model in UV mapper in order to validate the function of my own weld function there was nothing to weld. So when it comes to this model I suppose I either have to handle it another way than the other models or I will have to work on an exported version instead.