I think I should make something clearer. The app does NOT (yet) replace custom (embedded) geometry with .obj references. (However - that may come soon, given the interest.) What my app does is take a prop file and replace the custom geom in it with the vert-data from that of an already existing .obj file. The new vert data is included in the new prop as replacement custom geometry. For example: Load a figure. Load some dynamic clothing. Use the cloth-room to fit/stretch the clothing to that figure. Save the resulting clothing (from the frame that looks best) as a .obj file. All standard so far. (Side note... The reason for taking this approach (rather than using external geometry) is that, if you have a bit of clothing fitted to a specific figure, it is unlikely that that identical set of verts would be used for any other figure. However, I can see that in different situations, the reverse might be true.) Now my app: Takes the ORIGINAL clothing prop and the FITTED .obj file, and replaces the verts in the original file with those from the .obj file and saves the result to a new file. I am working on some enhancements: Currently ALL it does is replace the vertices in a prop file with new vertices. I have already discovered some problems with this approach, which I want to change (for my own benefit). The main problem I've found so far is that, by copying the original prop, the new prop retains any parenting, which can lead to having to re-parent the new prop to "universe", then zero the x/y/z params (if, as I usually do, you re-parent the clothing to universe whilst going through the fitting process). Not a big deal, but an annoyance none the less. The other problem is that some props come with multiple custom geometries embedded (PhilC's "Hareem" costume being a case in point) which my app doesn't cater for at all. There are also some "presentation" problems, which, if this app is going to be more used than I expected (as seems to be the case), I ought to get sorted. I have a (very basic) version up and running. I'm going to be working on it during the next week or so because are some other issues I need to look into if this app is going to be taken seriously, rather than the hack tool it is at present: There's no help. There's no check that the verts in the .obj match those in the the pp2 file. Had I known the interest generated I wouldn't have started from here:-)) Finally: @kuroyume0161: Thanks for that info. It might come in handy:-)) @hauksdottir: errm, yes, I think. The idea behind the app is to be able to create pre-configured clothing for specific characters, to avoid going through all the cloth-room stuff each time (and sometime several times just for 1 character). @EnglishBob: My app works the other way around, and is specifically designed to INCLUDE embedded geom into a poser file (see above). But if there's a lot of interest in doing the reverse (and there seems to be) I could do that too, but later.. I have enough on my plate right now. PS - one of the things I have beeen thinking about is creating .obj files for external use by Poser, stripping any normals info on the way.. Anyway, bedtime now... Cheers, Diolma