Straight from the horse's mouth... Victoria 3 introduced a new system whereby you INJect the morphs you want to use, as you want to use them. After INJecting those morphs, you can spin the dials to your heart's content. Problem is, when you save those settings to your library (via pose or face files), only the values for the dials [channels] are recorded (by choosing yes when prompted to include morph information). When you load V3 later and apply the pose you saved, it appears as though nothing happened. Well, in actuality, the values recorded have been applied... but because the morphs are not loaded and the channels are not visible, you don't see the change. Before this utility, you would need to either inject all the morphs (needlessly taxing system resources) or manually create (by hand) all of the readScript references to load all the morphs used to create your 'character'. The other alternative was to save a cr2/pz3, which records much more information than is needed and consumes valuable drive space. Being that Poser doesn't save information for 'BODY' channels in a pose file, and given that the best way to apply Full Body Morphs (which all of Victoria's body morphs are) is from the 'BODY', the cr2/pz3 route offered the least heartache. The problem there, aside from consuming space on your hard drive that is better spent somewhere else, is that when an update is released (be it for adding features or correcting a problem) your saved cr2/pz3 doesn't benefit from the changes. So, enter IPB... IPB automates the tedious grunt work of creating poses that include readScript references, previously done exclusively by hand. It does this, based on the values of the channels it reads in the cr2/pz2/fc2 you feed it. Using the options in the 'Options' dialogs, the user can decide exactly how the file is built and what information it contains. Simply? IPB negates the need to manually track down all the [DAZ created] morphs that went into creating that 'perfect' character for Victoria 3, by doing it for you. And it does it in the best possible way to save your system resources, hard drive space, and create files that are completely legit to give away and/or sell. Granted, I'm sure this sounds a bit biased coming from me... but truth be told, I wouldn't of created it if I didn't see a need for it. And if you care for a bit more, it just so happens that this tool was something I created for our [DAZ's] production department, as an in-house tool to speed up the production pipeline. Seeing the relevance for such a tool, I (with help) convinced the PTB that releasing this particular tool would be good for the overall community. -Rob (the guy who wrote it)