Well Marie, if you wish to send a figure that has a custom obj file then using Mover will make it legal. If you are using ProPack, ProPack makes a whole new obj file with the custom geometry in the cr2 IF you save the figure in PPP. Again, using mover you could pass this new obj around by using the base figure as a key. For example, if you made new groups on the p4 nude woman model, you would get a new obj file from Pro Pack with your changes inside but you can still use the p4nudewoman.obj file in your poser directory as the key file for Mover and distribute the new obj encode with the p4nudewoman as the key. If you got a cr2 from someone that has custom geometry in it and it refers to a base figure in your poser geometry folder, you can still open it in pro pack. What will happen is pro pack will load it just like p4 did. If you save it as a new cr2, however, and it has custom geometry, pro pack will then create a new obj for that figure. If you wish to then distribute that new changed figure you'd have to use mover to encode the obj file created by pro pack. PZ3 files do NOT contain the obj file. They are merely cr2 files with the scene's lights, cameras etc stored in them. You can actually just load a pz3 as a figure by renaming it to a cr2 and load it in a character library. As for my earlier comment about grouping the whole figure and forcing the obj data into the cr2, that was a confusing and extremely rare example. Please ignore it.