Dialyn, V3 does not need this to make her work. She does need morphs and the packaging in modules only facilitated d/l for those who still have dial-up and also gave you the ability to choose which packages you wanted. The primary use that I can see for this is to create a distributable file. It is quite easy to use. The other is if you create characters or have sets of particular morphs from V3 that you like to use, you can create a pose file to load them rather than creating a CR2 which contains copies of all the memory intensive morphs over and over. Think of it this way: You have 10 characters in your character library. Each has the same number of morphs, but they are tweaked slightly different to create your different characters. That means you have 10 copies of each of those morphs. With the readscript pose file, there is one set of those same morphs and the readscript goes and gets each morph but only when you apply the pose file. You still have all 10 characters, but in a much smaller file that doesn't have the morphs until you use it. Ten characters...ONE set of stored morphs. And because a person must have the OBJ and morphs in order for the pose file to work, the file can now be distributed. For personal use, even if I don't want to distribute, I use the utility so I won't have copies of the morphs in multiples either. My runtime is huge enough already. I hope this makes enough sense to you. It's just that it's new. And though it seems more complicated, it is more efficient...at least to me it is. Can't speak for anyone else. Cris